How we replaced rented mail with a mailbox we own
Email is priced per person, forever. We moved it in-house, and the interesting part is the three places we decided not to cut the cord.
Mail is the purest per-seat product there is. Every person you hire adds a line to the bill, every month, for as long as they work for you. Nothing about the tenth mailbox costs the provider more than the first.
It is also the subscription people assume is untouchable. So this one is worth walking through carefully, including the parts where we deliberately kept a safety net.
Three separate problems, not one
Running your own mail sounds like one project. It is actually three, and they fail in different ways:
- Receiving: mail addressed to the domain has to arrive somewhere you control.
- Storing: it has to be kept, threaded, and searchable.
- Sending: it has to leave and actually land in an inbox rather than a spam folder.
Most people who try this solve storage, discover sending is the hard one, and quietly go back.
Receiving
The domain's mail records point at an email infrastructure provider rather than at a mailbox product. Anything sent to any address at the domain arrives there and triggers a webhook into our system.
A detail that cost us time: the notification that an email arrived does not contain the email. It carries metadata only. So when a message lands, we go and fetch the full text ourselves. If you build this, expect that step.
Storing, and the one place we broke our own rule
Our whole operating system runs on Airtable. Mail does not. It is the single exception, and the reasons are specific rather than ideological.
- Long messages get silently truncated past a field size limit, and silent truncation of a client email is unacceptable.
- There is no real way to search inside message bodies, and mail without search is an archive nobody opens.
- Mail volume grows without a ceiling in a way business records do not.
So mail lives in Postgres, which handles full-text search and volume without complaint. The lesson is not "Airtable is bad". It is that the shape of the data should pick the store, and mail is a different shape from everything else we run.
One rule we set early: if that database is unavailable, mail must still be forwarded and still be attached to its lead. Storage degrades instead of throwing. A new feature is never allowed to take down the path that already worked.
Sending, and the reputation trap
This is where self-hosted mail usually goes wrong. Deliverability is a reputation score attached to your domain, and it is easy to destroy by accident.
The specific danger is mixing cold outreach with real business mail. A few strangers marking outreach as spam will damage the reputation that your invoices and client replies depend on. Same domain, same score.
So outreach sends from a completely separate account, on a separate subdomain, with its own signing key. A complaint about a cold email cannot reach the reputation that client mail depends on. If you take one thing from this post and you send any outreach at all, take that.
The security line we drew differently
Most of our internal tooling fails open on purpose. If a check cannot run, it lets you through, because locking the owner out of an operations dashboard during a bad deploy is worse than leaving it ajar.
The mailbox does the opposite. A missing session, a missing secret, an unverifiable token: all of them mean no. There is no override flag, deliberately. A setting that opens everyone's email is not a safety valve, it is a vulnerability with a friendly name.
What we did not cut
Every inbound message is still forwarded to an ordinary external inbox. We own the mailbox, and we kept a copy somewhere that does not depend on our own deploys being healthy.
That is not a failure of nerve. If our system has a bad morning, missing a client email is a real cost and the forward is nearly free. Owning your software does not mean refusing all safety nets. It means choosing them on purpose instead of paying per seat for them.
The honest cons
- You become your own deliverability team. Signing keys, sending domains and bounce handling are now your job.
- There is no desktop or mobile client unless you build or connect one. In practice we work in the browser.
- An outage is yours to fix, with no support line to escalate to.
- Long retention and legal discovery are genuinely easier on a big provider. If you are in a regulated industry, think hard.
Who this is actually for
If you have a handful of mailboxes and no compliance obligations, this is a strong trade. The per-seat line disappears and your mail sits next to the records it is about.
If you are an enterprise with a legal hold policy, keep renting and do not feel bad about it. Knowing which subscriptions to keep is the same skill as knowing which to kill.