A proposal published in late June and flagged by the Hacker News community describes a new top-level domain — .self — built specifically to support self-hosted services. The idea is that individuals and households could claim a stable, human-centered address for their own servers: a home media library, a personal cloud, a family calendar, a local AI assistant. The organization behind it frames this as reclaiming digital identity from platforms that can change their terms, raise their prices, or simply shut down.
Most families will not set up a .self domain this week. That's fine. But the proposal is worth paying attention to as a signal, not as a product.
What's actually changing
For the past fifteen years, the dominant logic of household computing has been: let someone else run the server. Google holds your email. Apple holds your photos. Dropbox holds your documents. Spotify holds your music. This model is convenient, and it works — right up until it doesn't.
Platform risk is real and underappreciated. Services sunset. Pricing structures shift. A company acquired this year may have different data practices next year. Recent BLS data on software sector employment shows repeated contraction waves, which means the engineers maintaining your cloud service are not guaranteed to be there indefinitely.
The .self proposal, as covered by Hacker News, represents a technical community that has been quietly building in the opposite direction: home servers running open-source software, local networks that don't depend on any single company's uptime, personal data that stays personal. Tools like Nextcloud, Jellyfin, and Home Assistant have matured significantly. The technical barrier to running them is lower than it was five years ago.
The AI layer matters here too. Families are increasingly storing sensitive information in AI-assisted tools — health tracking, financial summaries, educational records for children. Most of that data sits on someone else's servers, under terms of service most people have not read. As AI systems become more embedded in daily household life, the question of where your data actually lives becomes more consequential.
None of this means the cloud is about to collapse. It means diversification is the right posture.
What we'd actually do
Audit where your irreplaceable household data actually lives. Sit down for thirty minutes and list the five or six things you would genuinely grieve losing: family photos, financial records, medical documents, your kids' schoolwork, contacts. For each one, identify whether you have a local copy. Most families discover they don't.
Most cloud backup services are automatic enough that people assume they're covered — until they lose access to the account. A one-time export plus an external drive (a 2TB drive costs under $60) is not a glamorous prep, but it closes the most common failure mode: account lockout, service shutdown, or billing lapse during a chaotic period.
Set up a basic local backup routine before you consider any server hardware. A dedicated NAS (network-attached storage) device like a Synology or a used mini-PC running TrueNAS is a reasonable second step for households that want real redundancy. But buy the external drive first. A working backup on a $55 drive beats a complicated server you abandon after a weekend.
Learn what your household's AI tools actually store. If anyone in your household uses an AI assistant for anything sensitive — medical questions, financial planning, legal summaries — spend fifteen minutes reviewing the data retention settings. Most major platforms have a history or activity page. Delete what you don't want kept. This is not about paranoia; it's the same logic as shredding financial mail.
Watch the self-hosting tool ecosystem without rushing to adopt it. Nextcloud, in particular, has a free tier installable on modest hardware and covers calendar, contacts, and file sync. It is not a weekend project for non-technical users, but it is achievable in an afternoon for someone comfortable with a router. If that's not you, knowing it exists is still useful — because the person in your neighborhood who can help you set it up probably already runs it.
The bigger picture
The .self proposal may or may not become an actual registered TLD. ICANN processes are slow and contested. What matters is that a meaningful technical community is building infrastructure designed to outlast any particular platform — and that the tools they're producing are now within reach of households that have never touched a command line.
Preparedness, at its core, is about not having single points of failure. That principle applies to your pantry, your finances, and your data. You do not need to run a home server to take this seriously. You need to know where your important files are, have a copy you control, and check it once a year.
The cloud is a convenience. Treat it like one.
