Email is the successful federated protocol. Since RFC 821 defined SMTP in 1982, anyone has been able to run a mail server and exchange messages with anyone else running one. A Gmail user can send to an Outlook user, who can send to someone on a custom domain, who can send to someone on iCloud. There is no central authority. No single company owns the network. There is not even a single implementation — Postfix, Exim, Dovecot and others all interoperate because they adhere to the same RFCs. This is what decentralised infrastructure looks like when it works. And yet, despite this architectural triumph, almost everyone outsources their email to a handful of companies. Gmail alone has over one and a half billion users. Add Outlook, Yahoo and iCloud, and the vast majority of emails flow through providers you can count on one hand. The protocol is federated. The user base is centralised.

This centralisation was never inevitable. It is the result of a deliberate asymmetry that compounds over time. Running a mail server is genuinely harder than signing up for Gmail — you need a domain, a server, DNS configuration, TLS certificates and working knowledge of SMTP, IMAP, SPF, DKIM and DMARC. It requires managing spam filtering, storage, backups and deliverability. Each task is individually solvable, but together they form a barrier that most people will not cross. And the large providers have spent decades making sure the barrier stays high. Every aggressive spam filter that silently drops mail from unknown senders, every new authentication standard that requires configuration a self-hoster must learn, consolidates their position under the banner of security. The asymmetry is not incidental. It is structural.

The debate about which email provider to use has been framed as a spectrum: Gmail at one end, self-hosting at the other, with Proton and Tuta somewhere in the middle. This framing is not wrong, but it misses the variable that actually determines your sovereignty. The unit of ownership in email is not the server, the software or the provider. It is the domain. A Gmail address — sangtd@gmail.com — cannot be moved. You can migrate your inbox, but you cannot migrate your identity. The moment you switch providers, everyone who knew your old address no longer reaches you. A custom domain — sangtd.net — is portable regardless of which server handles the actual delivery. You can move from Gmail to Proton to a self-hosted server without changing your address, without losing inbound mail during the transition and without anyone on the sending side needing to update their address book. The domain is the anchor. Everything else is replaceable.

This reframes the entire provider landscape. Gmail and Outlook offer the lowest barrier to entry and the highest barrier to exit. Your address is tied to their domain. Your data flows through their infrastructure. Google and Microsoft scan and process your email as raw material for their machine learning models and advertising systems. You are not paying with money, so you are paying with data, and if you ever want to leave, you must change your address and inform everyone you have ever corresponded with. This is not a product. It is a retention mechanism disguised as convenience. Apple’s iCloud Mail represents an improvement on privacy — Apple’s business model is hardware, not advertising, and the company has implemented end-to-end encryption for many services — but the lock-in operates through a different mechanism. Custom domain support exists but is cumbersome, and the experience degrades outside Apple’s ecosystem. A benevolent landlord is still a landlord. Proton Mail and Tuta address the privacy problem directly by implementing zero-access encryption: your emails are encrypted at rest using keys the provider does not possess. Neither company has an advertising model. Both offer custom domain support as a first-class feature. But they are still hosted providers, and a hosted provider always retains power over its users. While encryption protects stored content, metadata — who you email, when you email and from which IP address — remains visible to the server operator. If a Swiss court orders Proton to log metadata for a specific account, they have done so in the past. The encryption is strong, but the relationship is still tenant and landlord.

Self-hosting is the only arrangement where you are not a tenant. You own the server, the software, the keys and the data. It is also genuinely harder. Deliverability is the most difficult challenge: Gmail and Outlook are suspicious of emails from unknown IP addresses, and a new server with no sending reputation will land in spam folders for weeks until enough recipients mark your messages as legitimate. This is not an accident — the large providers have every incentive to make self-hosting difficult because each self-hosted user is someone who left their platform. But the technical barriers have decreased substantially. Projects like Mailcow, Mailu and Docker Mailserver bundle the entire mail stack into a single containerised deployment, handling DKIM key generation, SPF and DMARC policy suggestions and automated TLS renewal through Let’s Encrypt. What was a multi-week project a decade ago can now be done in under an hour, assuming you already have a domain and a VPS. The benefit of crossing this barrier is genuine sovereignty. Your email lives on your disk. No company reads it, mines it or can lose it on your behalf. No terms of service change retrospectively. No acquisition shuts down your account. If your VPS provider raises prices, you migrate. If your domain registrar changes policies, you transfer. Every layer of the stack is replaceable because every layer is built on open standards.

The path from Gmail to sovereignty follows a predictable sequence that most people skip. The first step is owning your domain. Register it, configure the DNS, set up email forwarding from your domain to your current Gmail or Proton inbox, and begin using your custom address for everything that matters — banking, government, password resets, professional correspondence. The second step is adding authentication: publish SPF, DKIM and DMARC records so your domain’s email is verifiable regardless of which server sends it. These two steps alone move you from tenant to landlord, because the domain is what gives you portability. The third step is choosing a provider that treats your domain as yours rather than its own. Proton and Tuta are the current best options. The fourth step, which you may never need to take, is running your own server. Each step involves more work and delivers more control. There is no universally correct point to stop — the trade-off is real and the work is non-trivial. But the direction of travel should be clear. Email sits at the centre of your digital life. It is your identity online, your password reset channel, your archive of personal and professional correspondence. It is too important to rent. Own the domain, and the rest follows.