Email is where a company’s most sensitive conversations live: pricing, contracts, disputes, staff matters. Most companies rent it by the mailbox and have never asked where it is stored or who can access it.
For most, that is a reasonable choice. For some, it is worth owning. One of our manufacturing clients decided it was, and we moved them.
Why they moved
Three concerns:
- Privacy. They could not get a clear answer about how the provider handled email content or who could access it.
- Cost. Per-user licence and storage charges rose with every mailbox.
- Control. Mailbox numbers, storage limits and spam rules were whatever the plan allowed.
None of these is dramatic. Together they describe paying a growing bill for something you do not control.
What we built
A dedicated AWS environment in an account the client owns, running Mailcow, an open-source mail platform that provides SMTP, IMAP, webmail, spam filtering and administration.
- The account is theirs. Not ours, not a reseller’s. If they replace us tomorrow, nothing changes.
- Policies are theirs. Mailbox quotas, user limits and spam rules are settings.
- Authentication is set up properly. SPF, DKIM and DMARC, so their mail is trusted by recipients and their domain is hard to spoof.
- Backups are defined. Mail data and configuration, on a schedule they chose.
Adding a mailbox is now a setting, not a purchase.
The honest trade-offs
Self-hosting email has a reputation for being difficult. The reputation is earned. Go in with open eyes.
Deliverability is your responsibility. A new sending address has no reputation. Authentication records must be correct, the server must not be on blocklists, and volumes should build gradually. Get it wrong and your quotations land in spam.
Someone has to maintain it. Security updates, certificate renewals, disk space, monitoring. This is a recurring task. It needs an owner, whether in-house or under a maintenance agreement.
Availability is on you. A hosted provider has a large operations team. You have a backup strategy and a recovery procedure. They must be tested.
Security is on you. A mail server is an attractive target. The cloud account underneath it needs the same guardrails as any production system: no long-lived access keys, restricted regions, a protected audit trail and spend alerts. We wrote up the baseline we apply.
A test nobody planned
In November 2026, Microsoft’s Exchange Online was unavailable worldwide for about a day. Mail on a separate, self-hosted server carried on. We wrote about what that day looked like and what to take from it.
When it makes sense
- You have enough mailboxes that per-user pricing has become a significant line.
- You have a real requirement to control where data is stored. AWS has had a Malaysia region since 2024, alongside Singapore.
- You need policies a hosted plan does not offer.
- You have, or can contract, someone competent to run it.
When it does not
- You have a handful of mailboxes. The subscription is cheaper than anyone’s time.
- You rely heavily on the bundled suite: shared calendars, documents, video meetings.
- Nobody will own maintenance. An unpatched mail server is worse than any vendor.
The wider point: own the account
The principle underneath is broader than email. Whatever you run in the cloud, the account should belong to your company.
We see the opposite often. A business whose website, systems and data live in an account registered to a freelancer or agency. When the relationship ends, so does access. In the worse cases, the business does not hold the credentials to its own production data.
Every system we build runs in an account the client owns. We work inside it with access they can revoke. It means a client can leave us easily. That is the point.
Questions to ask about your own setup
- In whose name is the account that holds our email, website and systems?
- Who holds the highest-privilege credentials, and are they a person or a company?
- If our IT supplier vanished, could we get in?
- Where, geographically, is our data stored?
- What would it take to move?
If the answers are comfortable, a subscription is fine. If they are not, the fix is rarely expensive. It is mostly a matter of putting the right name on the account.