Hosted email for custom domains compared - Workspace, Microsoft 365, Zoho, Proton, WorkMail

Pick hosted email for your domain without regret.

Page content

Putting email on your own domain sounds like a weekend DNS task. In practice it is a small distributed system with a twenty-year legacy.

MX routes inbound mail. SPF lists who may send for your domain. DKIM signs messages. DMARC ties the story together and tells receivers what to do when something does not line up. Skip or miswire any layer and you get silent failures, spam-folder burial, or both.

Hosted email options compared

This article compares the five hosted options I see engineers actually choose - Google Workspace, Microsoft 365, Zoho Mail, Proton Mail, and AWS WorkMail - with rough USD prices, setup friction, and honest when to pick what advice.

Why providers beat rolling your own

You can run Postfix or Exim on a VPS. You should not unless you sell email infrastructure. IP reputation, PTR, bounce handling, backscatter, and greylisting eat weekends. Managed hosts amortize that pain across millions of mailboxes. For a personal domain or a small team, paying a few dollars per seat is cheaper than your hourly rate debugging why Gmail drops your replies.

Google Workspace

Price - roughly 6-12 USD per user per month depending on tier and region.

What you get - Gmail UI, strong spam filtering, predictable deliverability, shared calendar and drive if you use them, and admin tooling that “just works” for most SMB setups.

Verdict - The default when you want reliability over novelty. Setup is boring in the good way. If your only goal is “you@yourdomain.com works forever,” start here.

Microsoft 365

Price - roughly 8-22 USD per user per month depending on bundle (often bundled with Office apps).

What you get - Outlook, deep enterprise features, Entra ID (formerly Azure AD) integration, and a natural fit if your company already lives in Excel, Teams, and SharePoint.

Verdict - Match made in heaven for Microsoft-heavy shops. Slightly heavier admin surface than Google for tiny teams, but reliability and deliverability are solid once DNS is correct.

Zoho Mail

Price - free tiers exist for tiny teams; paid plans often land around 1-5 USD per user per month.

What you get - Straightforward hosted mail, control panels that get the job done, fewer bells than the giants.

Verdict - Best when budget matters more than polish. Fine for side projects and low-stakes mail. Expect more rough edges in UX and occasionally messier deliverability stories than Workspace or Microsoft.

Proton Mail

Price - roughly 5-10 USD per user per month for paid plans with custom domains.

What you get - Privacy-first design, encryption oriented workflows, Swiss jurisdiction story that matters to some buyers.

Verdict - Choose Proton when privacy is a requirement, not a vibe. You may accept more integration friction (calendar, third-party clients, automation) than with mainstream suites.

AWS WorkMail

Price - list pricing is modest (on the order of 4 USD per user per month) before add-ons and data transfer.

What you get - Mailboxes in AWS, IAM-flavored admin, and hooks into the broader AWS universe.

Verdict - Paper looks cheap. Reality includes SES identities, receipt rules, routing surprises, and debugging sessions that belong in a ticket queue. Pick WorkMail only when AWS-native email is a product requirement. Otherwise you trade dollars for engineering hours you will not get back.

At a glance

Provider Rough $/user/mo Setup Best for
Google Workspace 6-12 Easiest Default choice, minimum drama
Microsoft 365 8-22 Easy-medium Microsoft-centric orgs
Zoho Mail 1-5 or free tier Medium Tight budgets, side projects
Proton Mail 5-10 Medium Privacy requirements
AWS WorkMail ~4 + AWS overhead Hard Deep AWS integration (rare cases)

Prices move with region, currency, and promotions - treat the table as order-of-magnitude, not a quote.

Choosing today

  • Want it to work and move onGoogle Workspace.
  • Already on Office and EntraMicrosoft 365.
  • Money is tight and mail is not mission-criticalZoho (eyes open on deliverability).
  • Threat model or policy demands privacyProton.
  • Need mail inside AWS for architectural reasons you can defend in a design reviewWorkMail; otherwise skip.

Closing

Email rewards boring choices. The clever move is rarely “my own Postfix box at a discount VPS.” It is picking a reputable host, nailing DNS (see the web infrastructure cluster for more on DNS), and spending your creativity on software that is not SMTP.