Hosted email vs self-hosted in 2026

“Should we run our own email server or just pay for it?” We get asked this every few months, usually by a technical founder who has read a thread on r/selfhosted and now thinks the $6-a-mailbox bill from Google is a scam. Sometimes it is the opposite: a company already self-hosting on an old box that keeps landing in spam, and they want out. We run mail for both kinds of clients, so here is the operator answer, not the hobbyist one.

Most comparisons you will find argue the wrong axis. They frame it as control versus convenience, or privacy versus the cloud. For a business it comes down to three duller questions: where does your mail actually land, what does an hour of broken email cost you, and who picks up the phone when delivery breaks on a Saturday. Answer those and the decision usually makes itself.

Self-hosted and hosted are not the only two boxes

Quick definitions, because people muddle them. Hosted email is a mailbox you rent: Google Workspace, Microsoft 365, Fastmail, Zoho. Someone else runs the servers, the spam filtering, the IP reputation, the backups. You manage users and pay per seat.

Self-hosted means you run the mail server yourself. That is Postfix and Dovecot on a Linux box, or a packaged stack like Mailcow or Mail-in-a-Box, sitting on a VPS you rent or hardware you own. You own everything, including the parts you did not know you were signing up for.

There is a third option almost nobody names, and it is the one we set up most often: self-hosted mailboxes with a paid SMTP relay in front for outbound. You keep your storage and your control, but you borrow someone else’s trusted IPs to actually deliver the mail. More on that below, because it dodges the single hardest problem with self-hosting.

The cost math nobody shows you

Self-hosting looks free. A 2 GB VPS that comfortably runs Mailcow for a small team is about $12 to $20 a month. Workspace is $7.20 per user, so ten people is $72 a month. On paper self-hosting saves you roughly $50 a month, $600 a year. That is the pitch, and it is honest as far as it goes.

It stops being honest the moment you price the part that never lands on an invoice. Someone has to patch the server, rotate certs, watch the queue, file a blocklist appeal when your IP gets flagged, and restore from backup the week the disk fills. Budget an hour a week in calm months and a brutal day or two when something breaks. At any sane rate for a person who can actually fix Postfix, that $600 of savings is gone and then some. We charge clients real money to run this for them precisely because it is real work.

So the cost case for self-hosting is not really about money. If you are doing it to save $600 a year on ten mailboxes, stop now and buy the seats. The savings only show up at scale, where per-seat pricing turns against you: 200 mailboxes on Workspace runs about $17,000 a year, and at that headcount a $40 VPS plus a slice of one sysadmin’s week looks very different.

Deliverability is the whole game

The savings math ignores the part that actually sinks most self-hosted setups: getting your mail into the inbox. Google and Microsoft between them filter most of the business email on the planet, and they do not trust a brand-new IP from a hosting provider’s range. You can have flawless SPF, DKIM, and DMARC and still sit in spam for weeks because your IP has no sending history.

Microsoft 365 is the worst offender. There is a pattern that has been complained about for years on Hacker News and every sysadmin forum: a correctly configured self-hosted server gets silently dropped by Outlook and Office 365 tenants, with no bounce, no explanation, and a support process that goes nowhere. We have watched legitimate mail vanish into that void. You cannot fix it from your end, because it is a reputation problem, and reputation takes months to build and one spam complaint to wreck.

Hosted providers solve this by sending from IP pools with years of accumulated trust and full-time teams whose entire job is staying off blocklists. You are renting that reputation. For most businesses that one fact ends the debate, because email that does not arrive is worse than no email at all.

When self-hosting actually earns its keep

We do recommend self-hosting in specific cases, and we build it without flinching when one of these is true:

• You have a legal data-residency rule that no hosted plan satisfies, like mail that must stay on hardware in one country or off US-owned cloud entirely.
• You are past a few hundred seats, where per-mailbox pricing stops making sense and you already employ people who run infrastructure.
• You send bulk or transactional mail you want on dedicated IPs you warm deliberately, rather than sharing a provider’s pool.
• You have a documented audit or privacy obligation that mail content never touch a third party.

Notice what is not on that list: saving money on a ten-person team, or a vague unease about the cloud. Those are the two reasons people usually give us, and neither survives contact with the deliverability problem.

When hosted wins, which is most of the time

If you run a normal business with somewhere between two and a couple hundred staff, hosted email is the right call and it is not close. You get inbox placement that just works, mobile and calendar sync, shared drives, spam filtering that updates itself, and a recovery path when someone fat-fingers a deletion. The per-seat fee buys you out of an entire category of problem.

The only real decision left is which provider, and that mostly comes down to whether your team lives in documents and spreadsheets or in Teams and Excel. We wrote a full breakdown in our Google Workspace versus Microsoft 365 comparison, migration gotchas included, so we will not repeat it here.

The hybrid most people miss

Back to that third option. Say you have a real reason to keep mailboxes on your own server but you cannot afford the deliverability gamble. You run your own Postfix and Dovecot for storage and receiving, and you route all outbound through a paid SMTP relay: Amazon SES, Postmark, or a provider like MXroute. Your server holds the data; their trusted IPs do the delivery.

That is what a smarthost does, and it is how plenty of serious self-hosted setups stay out of the spam folder. You keep most of the control argument and hand off the one part that is nearly impossible to win alone. It costs a few dollars per thousand messages, which for a business is rounding error. When a client insists on self-hosting and we cannot talk them out of it, this is almost always the shape we build.

What we would tell you to do

Default to hosted. Buy the seats, pick the provider that matches how your team works, and spend the hour you saved on something that grows the business. Email is infrastructure. It should be boring, and it should arrive.

Consider self-hosting only if you hit one of the four cases above, and even then put a relay in front of it. If you are already self-hosting and drowning in blocklist appeals, you do not necessarily have to move everything to a hosted plan. Sometimes the fix is just routing your outbound through a smarthost and leaving the rest alone.

If you want a second opinion on your specific setup, that is the kind of thing we do. We run mail servers for clients across Postfix, Mailcow, and the major hosted platforms, we fix deliverability when SPF, DKIM, and DMARC are not enough, and we will tell you plainly when self-hosting is a bad idea for you. Start with our email setup and deliverability services, or read how we handle mail on a Linux server if you are leaning toward running your own.