Self-Hosting Gets Its Own TLD: What .self Means for Builders
The .self TLD proposal wants to make self-hosting a first-class citizen of the web — and that's a bigger deal than it sounds.
The signal: A proposal for a .self top-level domain is gaining serious traction, designed specifically to give self-hosted services a clean, standardized namespace on local networks.
Why it matters: Right now, self-hosters hack around with .local, custom DNS resolvers, or ugly IP addresses — it’s friction that keeps normies away from owning their own stack. A dedicated TLD flips self-hosting from a hobbyist workaround into something browsers and tooling can actually support natively.
The pattern I’m watching: This lands right as the self-hosting wave is cresting — Coolify, Umbrel, and Proxmox are pulling real users away from SaaS. The missing piece has always been UX polish; a recognized TLD is exactly the kind of infrastructure primitive that unlocks the next layer of tooling.
What I’d do with this: If you’re building anything in the homelab or privacy-first infrastructure space, start designing around .self now — early tooling that assumes this namespace will have a head start when (not if) browsers adopt it. At minimum, watch the IETF/ICANN thread closely; this is the kind of spec that moves fast once it gets momentum.