Answers that do not mention SiteGround

Yes. The important distinction is that your website host and your email host do not need to be the same company. You can keep your website exactly where it is and point your domain’s email (MX) records to a dedicated email provider. Microsoft explicitly notes that changing mail hosting does not affect where the website runs. Microsoft Learn

My shortlist

For most small businesses, I'd look first at Google Workspace or Zoho Mail. If you already live in Word/Excel/Outlook, Microsoft 365 is the natural alternative.

The key setup

Suppose your website is:

www.yourcompany.com

and you want:

you@yourcompany.com
info@yourcompany.com

You can leave your website's A/CNAME records pointing at your web host while changing only the MX records to your email provider. You'll also normally configure SPF, DKIM and DMARC for good deliverability and anti-spoofing protection. Zoho's current documentation, for example, specifically recommends configuring these records. Zoho Zoho

Zoho is particularly straightforward if cost matters: it supports custom domains and lets you manage multiple domain-based accounts and aliases. Zoho

zoho.com

If you tell me what you're using for your website hosting (e.g. GoDaddy, Hostinger, Bluehost, Squarespace, Wix, WordPress, Cloudflare, cPanel, etc.), I can tell you exactly which email option fits and what DNS records you'll need to change.

Yes. For a growing ecommerce store, I’d look at Zoho Mail, Fastmail, and Microsoft 365.

• Zoho Mail — particularly attractive if you want lots of mailboxes without paying for a huge productivity suite. It supports custom-domain email, organization-wide spam controls, allow/block lists, quarantine, SPF/DKIM/DMARC checks, and admin rules. Zoho Zoho Zoho
• Fastmail — excellent if email itself is the priority. It supports custom domains, multiple addresses, shared addresses such as support@, and adaptive spam filtering. Fastmail Fastmail Fastmail
• Microsoft 365 — a strong option if your team also needs Outlook, OneDrive, Teams, etc. Microsoft includes built-in anti-spam protection for cloud mailboxes, with configurable policies and phishing protection. Microsoft Learn

What I'd consider for ecommerce

If you're expecting addresses like:

orders@ · support@ · returns@ · sales@ · billing@ · info@

I'd pay particular attention to how the provider charges for users/mailboxes versus aliases/shared addresses. You may not need a separate paid mailbox for every address.

Zoho Mail is probably the first one I'd investigate if keeping costs under control while adding lots of addresses is important. Fastmail is worth considering if you want a simpler, email-focused experience and particularly good spam handling.

One other important distinction: customer/marketing email (Shopify notifications, newsletters, abandoned-cart emails, etc.) should generally not be sent directly from your normal employee mailboxes. For that, you'd typically use a transactional/marketing email service alongside your business email hosting.

If you tell me roughly how many people/mailboxes you have now and how many you expect in 1–2 years, I can compare the likely costs and setup for Zoho vs Fastmail vs Microsoft 365.

Yes. For a growing ecommerce store, I’d look primarily at Google Workspace, Microsoft 365, and Zoho Mail. All support custom-domain mailboxes and are designed to scale as you add staff.

*Pricing varies by plan and billing term.

What I'd consider for ecommerce

Google Workspace is particularly convenient if you'll have addresses such as:

• you@store.com
• orders@store.com
• support@store.com
• returns@store.com
• accounting@store.com

You can manage employee accounts centrally and add/remove users as the company grows. Google says its business Gmail includes phishing protection and tools for managing users as the organization grows. Google Workspace

Microsoft 365 is another strong choice, especially if your team uses Outlook, Excel, Word, or Teams. Exchange Online includes multilayer spam and malware protection, customizable anti-spam policies, and administrative controls. Microsoft Microsoft Learn

Zoho Mail is worth looking at if you're mainly paying for email rather than a complete productivity suite. Current 2026 comparisons put its entry-level business email considerably below Google/Microsoft on a per-mailbox basis. Faivelo Zapier

One important ecommerce distinction: don't use your employee mailbox provider as your bulk marketing-email platform. For newsletters, promotions, abandoned carts, etc., use a dedicated ESP such as Klaviyo/Mailchimp/etc. Microsoft explicitly recommends a third-party ESP for commercial bulk mail. Microsoft Learn

My practical setup

For a store expecting to grow from, say, 3 → 20+ employees, I'd set it up roughly like:

Google Workspace/Microsoft 365
→ employee mailboxes + customer-facing support inboxes

Dedicated ecommerce email platform
→ newsletters, promotions, automated customer emails

SPF + DKIM + DMARC
→ domain authentication and protection against spoofing

If you tell me roughly how many mailboxes you need now (e.g. 5, 10, 20) and whether you prefer Gmail or Outlook, I can compare the actual monthly cost and setup for the most sensible 2–3 options.

For a solo freelancer, I’d shortlist these:

• fastmail.com — best overall fit. It supports custom domains, has dedicated mobile apps, calendars and contacts, and can also sync with third-party clients such as Outlook and Apple Mail. Its Individual plan currently includes 60 GB total storage. Fastmail
• proton.me — best if privacy is a priority. Paid plans support custom domains, and Proton provides mobile apps. Mail Plus supports one custom domain and 15 GB storage. Proton Proton
• zoho.com — budget-oriented option. It supports custom-domain email and is aimed at individuals and small businesses; current third-party comparisons list inexpensive plans with mobile/device synchronization. Namecheap

My pick

Fastmail is probably the simplest choice for a one-person freelance business. It gives you a professional address such as hello@yourdomain.com without forcing you into a large productivity suite, while still giving you good mobile and desktop flexibility. Fastmail

If you tell me your budget per month (e.g. under $2, under $5, or price doesn't matter), I can narrow it down to one or two options.

For a solo freelancer, I’d shortlist these three:

My pick: Fastmail

For a one-person freelance business, Fastmail is probably the easiest overall choice. Its paid plans support your own domain, multiple addresses on one account, calendars and contacts, a dedicated mobile app, and access through clients such as Apple Mail and Outlook. www.fastmail.com

That gives you something like:

• you@yourdomain.com
• hello@yourdomain.com
• invoices@yourdomain.com

without having to manage a complicated mail server.

If price matters: Zoho Mail

Zoho Mail is worth considering if keeping costs down is more important. It supports custom domains, and its paid plans provide IMAP and ActiveSync, allowing synchronization with mobile and desktop clients. www.zoho.com

There is also a free custom-domain tier, but it does not include IMAP/POP/ActiveSync, so I wouldn't choose the free tier if mobile/third-party mail synchronization is a requirement. www.zoho.comwww.fastmail.com

If privacy is the priority: Proton Mail

Proton Mail supports custom domains on paid plans and has dedicated iOS and Android apps. proton.me It's particularly attractive if encrypted/private email is important to you. One caveat is that third-party desktop clients require Proton Mail Bridge, which is available to paid subscribers. proton.me

Bottom line: I'd choose Fastmail for a typical solo freelancer, Zoho Mail for maximum value, or Proton Mail if privacy is your primary consideration. www.fastmail.com

For a local service business with multiple aliases + nontechnical staff, I’d narrow it to Microsoft 365, Google Workspace, or Zoho Mail.

What I'd choose

Microsoft 365 is particularly well suited if you have addresses such as:

• info@yourbusiness.com
• service@yourbusiness.com
• appointments@yourbusiness.com
• billing@yourbusiness.com
• support@yourbusiness.com

You can make these shared mailboxes, give multiple employees access, and let staff send/reply as the shared address. Microsoft also supports automatic replies, forwarding, permissions, and shared calendars. learn.microsoft.com

That structure is generally better than giving everyone a bunch of aliases on their personal mailbox. For example:

Employee: jane@yourbusiness.com
Shared mailbox: appointments@yourbusiness.com
Aliases: bookings@yourbusiness.com, schedule@yourbusiness.com

All three public-facing addresses can feed the appointments mailbox, while Jane and other staff work from the same inbox.

When I'd pick the others

Google Workspace makes more sense if your staff already live in Gmail, Google Calendar, and Google Drive. Google Groups can also function as Collaborative Inboxes where staff can assign and resolve conversations. support.google.com

Zoho Mail is worth considering if keeping costs down is important. Its admin interface supports multiple aliases per user, and Zoho's current documentation says a user can have up to 30 addresses total (1 primary + 29 aliases). It also has dedicated shared-mailbox functionality. www.zoho.com

My practical recommendation: if you tell me (1) how many employees need email, (2) roughly how many shared addresses/aliases you want, and (3) whether you're currently using Gmail or Outlook, I can lay out the simplest setup and approximate monthly cost for your business.

For a local service business, I’d generally choose Google Workspace if your priority is easy setup + nontechnical staff + lots of aliases.

My shortlist

• workspace.google.com — best fit for most small businesses. Gmail is familiar to most staff, and Google supports aliases such as info@, sales@, and support@. Group aliases don't require an additional paid user, and individual users can have up to 30 aliases. Google Workspace Google Workspace Help
• microsoft.com — good if your staff already live in Outlook/Word/Excel. Microsoft supports up to 400 aliases per user without additional licenses. For addresses that several employees need to actively manage, Microsoft recommends shared mailboxes rather than ordinary aliases. Microsoft Learn Microsoft
• zoho.com — worth considering if keeping costs down is important. It has an admin console for aliases and shared mailboxes, with a fairly straightforward management model. Zoho currently documents up to 30 addresses per user (1 primary + 29 aliases). Zoho Zoho Corporation

How I'd structure your business

Rather than creating a separate paid account for every address, I'd do something like:

• john@yourbusiness.com — actual employee mailbox
• sarah@yourbusiness.com — actual employee mailbox
• info@yourbusiness.com — shared/group address
• bookings@yourbusiness.com — shared/group address
• quotes@yourbusiness.com — shared/group address
• billing@yourbusiness.com — shared/group address

That distinction matters: aliases are great when one person owns the address; shared/group mailboxes are better when multiple staff need to see and respond to the same incoming conversations. Google specifically recommends Google Groups when several users need to send and receive from the same address. Google Workspace Help

Bottom line: I'd pick Google Workspace unless your business is already heavily invested in Microsoft 365. It's particularly attractive for a small service company because the Gmail interface is familiar, setup is guided, and you can create common business addresses without paying for a separate mailbox for every alias. Google Workspace

If you tell me roughly how many staff you have and which addresses you want (e.g. 3 people + info@, quotes@, billing@), I can lay out the cheapest/simple setup and explain exactly which should be users, aliases, or shared inboxes.

For a small nonprofit funded by donations, I would start with nonprofit programs before looking at paid email hosts. The biggest cost savings usually come from eligibility-based grants rather than finding the cheapest mailbox. Google Google

Here are the strongest options:

My shortlist for a donation-funded nonprofit

1. Best overall: Google Workspace for Nonprofits

For most small nonprofits, this is the first thing I would check. It gives you:

• Email at your domain (name@yournonprofit.org)
• Shared calendars
• Google Drive and Docs
• Shared ownership of files (important when volunteers/staff change)
• Admin controls and security features

Google lists a nonprofit edition at $0/user/month for eligible organizations, with custom-domain Gmail and collaboration tools included. Google

Good setup pattern:

• executivedirector@domain.org → real person
• info@domain.org → Google Group/shared address
• donations@domain.org → donor inquiries
• board@domain.org → board communication

Avoid creating separate paid accounts for every role address if a group/alias will work.

2. Best if your team lives in Outlook: Microsoft 365 nonprofit

Choose this if your staff already uses:

• Word/Excel heavily
• Teams meetings
• Outlook calendars
• SharePoint/OneDrive workflows

Microsoft’s ecosystem is closer to a traditional Exchange environment. Nonprofit licensing can substantially reduce costs for eligible organizations. Lifehouse Development

3. Cheapest simple email: Zoho Mail

If you have, for example:

• 2–5 staff
• no need for Google Docs/Drive
• mostly email/calendar

Zoho can be much cheaper than paying for a full productivity suite. TechRepublic

I would be cautious about using it as your long-term platform if you expect:

• many volunteers
• lots of shared documents
• complex permissions
• grant/compliance workflows

4. Email-only alternatives: Fastmail or Proton

These are good when email quality matters more than an office suite:

• Fastmail: clean, fast, standards-friendly email
• Proton: privacy/security emphasis

They are usually not my first choice for a small nonprofit because you often still need document sharing, calendars, and collaboration.

A few nonprofit-specific things I would prioritize

1. Organization-owned accounts

• Never let donor records live in a volunteer’s personal Gmail account.
• Make sure the domain registrar, email admin account, and recovery contacts belong to the nonprofit.
• Use aliases/groups instead of extra mailboxes

• contact@
• donations@
• volunteers@
• board@
• Set up email authentication

Configure:

• SPF
• DKIM
• DMARC

This matters a lot for donor communications and newsletters.

4. Plan for turnover

Volunteers and board members leave. Make sure:

• at least two trusted admins exist
• files belong to the organization
• access can be revoked quickly

My recommendation by nonprofit size

• 1–20 people: Google Workspace for Nonprofits first; Zoho if you only need mail.
• 20–100 people: Google Workspace or Microsoft 365 nonprofit depending on your team’s habits.
• Mostly volunteers + shared inboxes: Google Groups/shared mailboxes are often more important than buying many accounts.
• Sensitive donor/legal information: consider stronger security controls and retention features.

If you tell me:

1. number of staff/volunteers needing accounts,
2. whether you use Gmail/Google Docs or Outlook/Office today, and
3. whether you need newsletters (Mailchimp-style) or just normal email,

I can narrow this to the cheapest practical setup.

For a small donation-funded nonprofit, I’d focus first on nonprofit-specific free/discounted tiers, rather than ordinary consumer email hosting.

The main options

Google Workspace

google.com offers a no-cost Google Workspace for Nonprofits edition to eligible organizations. It includes Gmail on your own domain, Calendar, Drive, Docs, Sheets, Meet, etc. Google currently says the nonprofit edition supports up to 2,000 users, with 30 GB of storage per user in the standard nonprofit offering. Google Google Help Google Help

So if you're already thinking "G Suite," this is probably the first thing I'd investigate. You don't necessarily need to pay for ordinary Google Workspace.

Microsoft 365 / Exchange

microsoft.com currently lists Microsoft 365 Business Basic as a grant/free offer for up to 300 users. It provides custom-domain email through Exchange, Outlook, Teams, and 1 TB of OneDrive storage per user. Microsoft

If your staff lives in Word/Excel/Outlook, this can be particularly attractive. Microsoft also offers Business Standard at $3.50/user/month for eligible nonprofits, including desktop Office applications. Microsoft

One thing to watch: Microsoft changed nonprofit pricing in July 2026, so older articles quoting nonprofit prices may now be outdated. Microsoft Microsoft

Zoho

zoho.com is another option worth considering if minimizing recurring costs is paramount. Its nonprofit program provides credits that can be applied toward eligible Zoho products, including adding users and renewals. Zoho

I'd consider Zoho primarily if you don't need the broader Google/Microsoft ecosystem and want a leaner alternative.

What I'd do for a donation-funded nonprofit

First choice to investigate: Google Workspace for Nonprofits at $0.

Alternative: Microsoft 365 Business Basic at $0 if your organization is more Outlook/Word/Excel-oriented.

That gives you professional addresses such as director@yournonprofit.org, info@yournonprofit.org, and donations@yournonprofit.org without paying ordinary per-user commercial email rates.

One important distinction: email hosting and your domain registration are separate. You'd still need to maintain yournonprofit.org with a domain registrar and point its DNS/MX records to Google or Microsoft.

If you tell me roughly how many people need individual mailboxes (e.g. 5, 10, 25) and whether you're more Gmail/Google Docs or Outlook/Word/Excel, I can compare the actual annual cost and setup complexity for the 3–4 most economical choices.

Yes. For a media site with a large newsletter/mailing list, I’d look at email delivery platforms rather than conventional hosted inbox providers like Google Workspace or Microsoft 365.

The key distinction is that you can keep your own domain (news@yourdomain.com) while having the actual sending infrastructure hosted by a specialist.

Good options

• aws.amazon.com — Best if you're comfortable with a more technical setup. It supports your own sending domain, custom MAIL FROM, DKIM/SPF/DMARC, dedicated IPs, IP pools, and automated managed-IP warmup. AWS specifically supports separating marketing and transactional traffic into different IP pools. AWS Documentation AWS Documentation AWS Documentation
• postmarkapp.com — Particularly interesting if deliverability is the priority and your volume is substantial. Postmark now supports bulk/newsletter sending through Broadcast Message Streams, while keeping broadcast and transactional traffic separated. Dedicated IPs become available at 300k messages/month. Postmark Postmark
• mailgun.com — A strong fit for publishers and developer-driven sites. Mailgun supports dedicated IPs and recommends them generally around 100k+ messages/month, with pools for very high-volume sending. Mailgun Help Center
• sendgrid.com — Another major option for large-scale marketing email, particularly if you want a more polished marketing/newsletter interface alongside the sending infrastructure.

One important architecture choice

For a media company, I'd generally set things up something like:

yourdomain.com
       │
       ├── website
       │
       ├── regular mail
       │      └── Google Workspace / Microsoft 365
       │
       └── email sending
              └── mail.yourdomain.com
                    └── SES / Postmark / Mailgun / SendGrid

Then authenticate the sending subdomain with SPF + DKIM + DMARC, rather than simply blasting millions of messages through your normal employee-mail infrastructure.

For example:

From: newsletter@yourdomain.com
Sending infrastructure: Postmark / SES / Mailgun
DKIM: configured for yourdomain.com
SPF: configured for your sending domain
DMARC: configured for yourdomain.com

For heavy mailing-list sending

The volume matters a lot. If you're talking about something like 100k/month, 1M/month, or 10M+/month, I'd make different recommendations.

Also, don't automatically assume that a dedicated IP is better. At sufficiently high and consistent volume it can make sense, but you then own the reputation of that IP and need proper warm-up and list hygiene. AWS, for example, explicitly notes that consistent sending patterns are important for dedicated-IP reputation. AWS Documentation AWS Documentation

If you tell me roughly how many emails you send per month (e.g. 500k, 2M, 10M) and whether you need a newsletter-management UI or just an SMTP/API backend, I can narrow this down to 2–3 suitable setups and compare approximate costs.

Yes. For a media site with a large newsletter audience, you usually do not want ordinary “hosted email” (mailboxes like Gmail/Workspace) to handle bulk sends. The common architecture is:

1. Mailbox hosting (for you@yourdomain.com, staff accounts)
2. Dedicated email delivery/newsletter platform (for sending thousands/millions of newsletters reliably)

The deliverability-critical part is the second one.

Strong options for a media publication

For a media site, I would generally look at:

• Beehiiv if the newsletter itself is a core product.
• Mailchimp if you need a broad marketing platform and nontechnical workflows.
• SES + a newsletter layer if you send very high volume and have engineering resources.
• Customer.io if personalization and behavioral automation matter.

For your own domain

Whatever you choose, set up:

• From: address on your domain (for example newsletter@yourdomain.com)
• SPF
• DKIM
• DMARC
• A dedicated sending subdomain, often something like:

• news.yourdomain.com
• mail.yourdomain.com
• send.yourdomain.com

Authentication is a major part of deliverability; SPF/DKIM/DMARC alignment helps receiving providers verify legitimate sending. Cloudflare Docs

If you mean “hosted email” as in staff inboxes

For normal company email:

• workspace.google.com
• microsoft.com
• fastmail.com

Then connect your newsletter sender separately.

A typical media stack

Example:

• Staff email: Google Workspace
• Newsletter platform: Beehiiv or Mailchimp
• Sending domain: news.example.com
• DNS: SPF + DKIM + DMARC
• Analytics: newsletter platform + Google Analytics

A few questions would change the recommendation:

1. Roughly how many subscribers (10k, 100k, 1M+)?
2. How many emails per week?
3. Is the newsletter the main product, or is it a publication with a newsletter attached?
4. Do you need staff mailboxes too, or only the sending infrastructure?

For a health-focused blog, I’d separate “own domain” from “own mail server.” If by “host email on my own domain” you mean addresses such as contact@yourblog.com, my recommendation is Tuta Mail with your custom domain, rather than running the mail server yourself.

Recommended setup

• Email: Tuta Mail with your custom domain.
• Domain: Keep the domain registered independently from the email provider.
• Website: Host the blog separately from email.
• Encryption: Tuta encrypts mailboxes end-to-end, including message contents, attachments, and subject lines. Tuta also supports encrypted communication with non-Tuta recipients through password-protected emails. Tuta Tuta
• Custom domain: Paid Tuta plans support custom domains, catch-all addresses, and unlimited aliases. Tuta Tuta
• Domain security: Configure SPF, DKIM, and DMARC for your domain. Tuta supports all three for custom domains. Tuta
• Account security: Enable 2FA, preferably a hardware security key where supported.

tuta.com

Why I wouldn't self-host the mail server

You can run something like mailcow, which gives you considerably more control. It supports hardened TLS configurations and mechanisms such as MTA-STS. Mailcow Documentation Mailcow Documentation

But self-hosted email creates a substantial operational/security burden: server patching, backups, spam filtering, IP reputation, TLS configuration, DNS, DKIM/SPF/DMARC, monitoring, and recovery all become your responsibility. For a health blog, I'd rather put that effort into securing the website and reader/subscriber data.

One important distinction

Email encryption isn't automatically end-to-end encrypted with ordinary recipients. If someone emails contact@yourblog.com from Gmail, you shouldn't assume that message is end-to-end encrypted merely because your mailbox is encrypted. Tuta's password-protected-mail mechanism can provide encrypted communication with external recipients, but you need an appropriate workflow for that. Tuta

If you specifically mean “I want complete physical control of the mail server and keys”, then I'd instead design a hardened mailcow + VPS + encrypted backups setup. That's a different recommendation from simply having private email on your own domain.

For a health-focused publication, I'd also avoid collecting unnecessary health information through ordinary email in the first place; email is a poor place to build a system for handling sensitive patient/client data.

For a health-focused blog, I’d use Proton Mail with your own domain rather than self-hosting mail. It supports custom domains, zero-access encryption, E2EE between Proton users, and password-protected encrypted mail for outside recipients. Proton Proton Proton

• Use contact@yourdomain.com for the blog.
• Enable SPF, DKIM, and DMARC.
• Never put sensitive health information in ordinary email; use Proton’s encrypted/password-protected messaging when appropriate.
• If maximum encryption coverage—including subject lines—is your priority, Tuta is an alternative. tuta.com

If by “own” you specifically mean running the mail server yourself, say so—I’d recommend a different architecture.

For a multi-site WordPress network where each site has its own branded domain/email, I’d focus less on WordPress itself and more on how efficiently you can manage multiple domains, mailboxes, aliases, DNS, and users from one admin account.

My shortlist

1. Google Workspace — probably the best fit

Google Workspace is particularly well suited to this architecture because you can put multiple domains into one Workspace organization. Google supports both alias domains and secondary domains; secondary domains can have their own users/mailboxes, while alias domains can give existing users additional addresses without another per-user charge. Google Workspace Help Google Workspace Help

For example, you could have:

• agency.com
• clientone.com
• clienttwo.com
• clientthree.com

all administered from one Google Workspace environment.

The important distinction is mailboxes vs. aliases. If each website needs info@clientone.com, info@clienttwo.com, etc., you don't necessarily need a paid mailbox for every address. You can structure some addresses as aliases or groups depending on how you want them handled. Google explicitly says aliases don't count as additional users. Google Workspace

Current US list pricing starts at $7/user/month for Business Starter, with higher tiers at $14 and $22/user/month; Google is currently showing promotional pricing as well. Google Workspace

workspace.google.com

2. Microsoft 365 — excellent if you prefer Outlook

Microsoft 365 handles multiple domains very well too. Microsoft says you can typically add up to 5,000 domains to a Microsoft 365 subscription, and email can be hosted on any of those domains. Microsoft Learn

That's more than enough for a WordPress agency managing dozens or hundreds of client sites.

I'd choose this over Google Workspace if your users already live in Outlook, Teams, Word, and Excel. Exchange provides the actual business email infrastructure, while Outlook is the client/interface. Microsoft

microsoft.com

3. Zoho Mail — interesting if mailbox count is the main concern

Zoho is worth investigating if you're going to create lots of relatively inexpensive mailboxes across many sites and don't need the Google/Microsoft productivity ecosystems.

It also has some useful administrative capabilities for complicated setups—for example, Zoho documents split delivery between Zoho Mail and Google Workspace. Zoho

What I'd actually do for a WordPress agency

I'd separate website hosting from email hosting:

Domain registrar / DNS
        │
        ├── clientone.com ──► WordPress site
        │                  └─► Google Workspace email
        │
        ├── clienttwo.com ──► WordPress site
        │                  └─► Google Workspace email
        │
        └── clientthree.com ─► WordPress site
                           └─► Google Workspace email

Don't tie email to the WordPress hosting account unless there's a compelling reason. It makes migrations, hosting changes, deliverability management, and client separation more complicated.

If you're building this as an agency/MSP and expect, say, 10–100+ domains, I'd lean toward Google Workspace or Microsoft 365 rather than individual email accounts bundled with each WordPress host.

The really important question, though, is how many actual people/mailboxes you'll have versus how many domains/sites. If you tell me something like “30 websites, each needs info@domain.com, but only 5 people actually read the mail”, I can lay out the most cost-efficient architecture and compare Google Workspace vs Microsoft 365 vs Zoho for that exact setup.

For a multi-site WordPress network where each site has its own branded domain/email, I’d separate the email infrastructure from WordPress hosting entirely.

My recommendation

Pick Google Workspace if these are real businesses/sites with people actively using the inboxes.

It gives you custom-domain email, Gmail, aliases, calendars, Drive, and centralized administration. Google explicitly supports creating addresses such as sales@site1.com and connecting your own domains. Google Workspace

The important question, though, is how many actual mailboxes vs. aliases you need.

The key cost issue

Google Workspace is priced per user, not per domain. Business Starter is currently $7/user/month at standard pricing, with 30 GB pooled storage per user. Google Workspace

So, for example, if you have:

• site1.com → john@site1.com
• site2.com → john@site2.com
• site3.com → john@site3.com

and John is the only person actually checking all three, you don't necessarily want three paid mailboxes. You'd want to structure the domains/addresses around one paid user and aliases where appropriate.

On the other hand, if you have 30 independent businesses and each needs separate users/inboxes, Google Workspace can become expensive.

Zoho is worth serious consideration

For a network with lots of domains and cost sensitivity, I'd investigate Zoho Mail before committing to Google.

Zoho Mail supports multiple domains, and Mail Lite starts around $1/user/month according to current pricing information. G2 LetterDuck

That's potentially a huge difference if you're building something like:

50 WordPress sites × 1–2 branded mailboxes each

rather than:

5 sites × 10 employees.

Microsoft 365 is the other major option

Microsoft Exchange Online supports custom domains and provides 50 GB mailboxes on Plan 1, currently listed at $4/user/month when paid annually. Microsoft Microsoft

I'd choose it over Google primarily if your users already depend heavily on Outlook/Office/Microsoft 365.

One architectural recommendation

For your WordPress multisite/network, don't make email part of the WordPress hosting stack.

I'd structure it:

Domains/DNS
→ Cloudflare or your DNS provider
→ Email provider
→ WordPress multisite separately

Then each domain has its own:

• MX records
• SPF
• DKIM
• DMARC
• branded addresses

Your WordPress installation doesn't need to know or care where the mailbox lives.

If you tell me roughly how many WordPress sites you have, how many email addresses each site needs, and whether those addresses need actual inboxes or mostly forwarding/aliases, I can work out the cheapest sensible architecture and compare Google vs Zoho vs Microsoft with actual monthly costs.

That's potentially a huge difference if you're building something like:

50 WordPress sites × 1–2 branded mailboxes each

rather than:

5 sites × 10 employees.

Microsoft 365 is the other major option

Microsoft Exchange Online supports custom domains and provides 50 GB mailboxes on Plan 1, currently listed at $4/user/month when paid annually. microsoft.com microsoft.com

I'd choose it over Google primarily if your users already depend heavily on Outlook/Office/Microsoft 365.

One architectural recommendation

For your WordPress multisite/network, don't make email part of the WordPress hosting stack.

I'd structure it:

Domains/DNS
→ Cloudflare or your DNS provider
→ Email provider
→ WordPress multisite separately

Then each domain has its own:

For a growing SaaS startup, I’d narrow it to Google Workspace vs. Microsoft 365, with Fastmail as a lighter-weight alternative.

My practical recommendation

Google Workspace is probably the most natural default for a SaaS startup. Its business plans give you custom-domain Gmail plus Calendar, Drive, Meet, Docs, etc.; current listed pricing is $7/user/month for Starter and $14/user/month for Standard after the current introductory promotion. Google Workspace Google Workspace

workspace.google.com

I'd particularly consider Business Standard once the team starts collaborating heavily because the 2 TB/user pooled storage and additional collaboration features make it considerably more capable than the entry tier. Google Workspace

Microsoft 365 is the alternative I'd choose if your team already lives in Outlook, Excel, Word, Teams, or the Microsoft ecosystem. Exchange provides business email with a professional domain and calendar, and Microsoft 365 adds the broader productivity suite. Microsoft

Fastmail is worth considering if you specifically want excellent email/calendar/contact hosting without paying for a huge productivity suite. Its business plans support custom domains, shared calendars, company address books, mobile apps, and third-party clients. Fastmail Fastmail

For a SaaS startup, I'd decide like this

• 5–50 people, engineering/product/marketing startup: Google Workspace
• Microsoft-heavy enterprise/B2B environment: Microsoft 365
• You only need email + calendar + contacts: Fastmail
• Expecting customers/partners to use Google Calendar heavily: Google Workspace is especially convenient
• Expecting enterprise customers with Microsoft/Outlook environments: Microsoft 365 deserves serious consideration

One important distinction: if by "calendar and contact sync" you mean syncing your employees' Google/Outlook calendars and contacts into your SaaS product itself via API, that's a different requirement. In that case, the choice of provider should also consider Google Calendar API, Microsoft Graph, OAuth, webhook support, and contact APIs—and I'd evaluate those separately.

Google Workspace is probably the most natural default for a SaaS startup. Its business plans give you custom-domain Gmail plus Calendar, Drive, Meet, Docs, etc.; current listed pricing is $7/user/month for Starter and $14/user/month for Standard after the current introductory promotion. Google Workspace Google Workspace

workspace.google.com

I'd particularly consider Business Standard once the team starts collaborating heavily because the 2 TB/user pooled storage and additional collaboration features make it considerably more capable than the entry tier. Google Workspace

Microsoft 365 is the alternative I'd choose if your team already lives in Outlook, Excel, Word, Teams, or the Microsoft ecosystem. Exchange provides business email with a professional domain and calendar, and Microsoft 365 adds the broader productivity suite.

Fastmail is worth considering if you specifically want excellent email/calendar/contact hosting without paying for a huge productivity suite. Its business plans support custom domains, shared calendars, company address books, mobile apps, and third-party clients.

For a SaaS startup, I'd decide like this

For a growing SaaS startup, I’d narrow it to Google Workspace, Microsoft 365, and Zoho Workplace. All three support custom-domain email plus calendars and contacts; the real choice is the ecosystem you want your company to build around. TechRepublic Zoho Microsoft

My practical recommendation

Google Workspace is the default I'd investigate first for a SaaS startup.

The important advantage isn't merely Gmail. You get an integrated identity and collaboration platform around your company domain: email, Calendar, Drive, Meet, Docs/Sheets, user administration, security controls, etc. Current 2026 comparisons also consistently place it among the leading small-business/startup options. TechRepublic Fit Small Business

I'd choose Microsoft 365 instead if your team already lives in Outlook, Teams, Excel, Word, SharePoint, or Windows. Exchange specifically provides synchronized email, calendars, and contacts across devices and supports custom domains. Microsoft

I'd choose Zoho Workplace if keeping the per-user bill down is a major consideration. Zoho includes Mail, Calendar, Contacts and other workplace tools, supports custom domains, and has migration tooling for email, calendars, and contacts. Zoho Zoho

One SaaS-specific consideration

Don't confuse employee email with transactional/product email.

For example:

• alice@yourstartup.com → Google Workspace / Microsoft 365 / Zoho
• support@yourstartup.com → same provider or shared mailbox
• hello@yourstartup.com → same provider
• notifications@yourstartup.com → transactional email provider
• password-reset@yourstartup.com → transactional email provider
• marketing campaigns → dedicated email platform

I'd keep those systems separate so an email-volume problem with your application's outbound mail doesn't jeopardize your team's normal business email.

If you tell me your approximate headcount (e.g. 5, 20, 50, 200) and whether you're already using Google or Microsoft for documents/SSO, I can compare the actual plans and 3–5 year cost implications.

I'd choose Microsoft 365 instead if your team already lives in Outlook, Teams, Excel, Word, SharePoint, or Windows. Exchange specifically provides synchronized email, calendars, and contacts across devices and supports custom domains. Microsoft

I'd choose Zoho Workplace if keeping the per-user bill down is a major consideration. Zoho includes Mail, Calendar, Contacts and other workplace tools, supports custom domains, and has migration tooling for email, calendars, and contacts.

One SaaS-specific consideration

Don't confuse employee email with transactional/product email.

For example:

Yes. For a small agency moving away from shared hosting mail (cPanel/Plesk-style mailboxes) to a VPS, I would usually avoid running email directly on the VPS unless you specifically want to become an email operator. Mail delivery reputation, spam filtering, blacklists, backups, DKIM/DMARC, and migrations are often more work than the VPS itself.

Common scalable options:

For an agency specifically, the key features I would look for are:

• Multi-domain support — e.g., client1.com, client2.com, youragency.com under one admin account.
• Aliases and role addresses — info@, support@, billing@, projects@.
• Shared mailboxes — avoid password-sharing for client-facing addresses.
• IMAP migration tools — move old shared-hosting mailboxes without losing folders.
• SPF, DKIM, DMARC management — essential for deliverability.
• Admin delegation — useful if your team manages client domains.
• API/provisioning — valuable if you create mailboxes for many clients.

A few agency-oriented platforms are specifically built around multi-domain workflows. For example, Atriomail positions itself for agencies/resellers with automated mailbox creation, DNS handling, migrations, and integrations. Atriomail Shipmail also focuses on agencies managing multiple domains and shared inboxes. Shipmail

A typical migration architecture I’d recommend:

VPS:
- websites
- apps
- databases

Dedicated email provider:
- all domain mailboxes
- spam filtering
- DKIM/SPF/DMARC
- backups
- mail reputation

If your agency is hosting email for your own staff only, Google Workspace/Microsoft 365/Zoho are usually the simplest.

If your agency hosts email for clients as a service, look more at white-label/reseller platforms or a managed mail stack rather than individual Workspace tenants. Atriomail

The best choice depends mostly on whether you need:

1. email for your agency only, or
2. email hosting you can provision and resell to clients.

Yes. For a small agency moving email off shared hosting, I’d separate VPS hosting from email hosting rather than run mail yourself.

Good options:

• Zoho Mail — inexpensive, custom domains, migration tools, SPF/DKIM/DMARC, and scales well as users increase. Zoho Zoho
• Fastmail — polished, lightweight email hosting with custom domains, aliases, shared addresses, and straightforward migration. Fastmail
• Microsoft 365 — better if clients need Outlook, Office, Teams, shared mailboxes, etc.
• Google Workspace — similar idea if the agency is already Google-centric.

For an agency specifically, Zoho Mail or Fastmail are worth looking at if you want the VPS to handle websites/apps while a specialist handles email deliverability, spam filtering, backups, and mailbox infrastructure.

If you're talking about hosting email for your agency's clients (multiple domains and potentially dozens/hundreds of mailboxes), that's a different category—I can suggest platforms designed specifically for that model.

For a boutique store, I’d separate mailbox hosting from transactional sending rather than force one provider to do both.

• Mailboxes: workspace.google.com for hello@, orders@, etc.; straightforward Gmail experience and custom-domain support.
• Transactional: postmarkapp.com for order confirmations, shipping updates, password resets, and similar automated mail. Its 10K tier starts at $15/month and supports custom sending domains, SMTP/API, webhooks, and inbound processing on higher tiers. Postmark Postmark
• Budget alternative: zoho.com for mailboxes; it can coexist with other mail infrastructure via split delivery. Zoho

Recommended setup: yourstore.com mailboxes on Google Workspace + a dedicated subdomain such as mail.yourstore.com for Postmark transactional sending.

For a boutique store, I’d separate mailbox hosting from transactional sending rather than expect one service to do both.

• Mailboxes: zoho.com or Google Workspace — good for hello@, orders@, etc.
• Transactional: postmarkapp.com — purpose-built for receipts, order confirmations, password resets, and shipping notifications, with separate transactional streams. Lettr Hack'celeration
• Lower-cost/high-volume alternative: aws.amazon.com, particularly if you have technical resources. Mailpro

My practical setup: Zoho Mail + Postmark, both authenticated on your store domain with SPF, DKIM, and DMARC. This keeps employee/customer mailboxes separate from automated store messages and makes deliverability easier to manage.

For a content partnership site (where you may need addresses like partners@, press@, contributors@, hello@, tips@, plus a catch-all), I would prioritize:

• strong alias support
• catch-all/wildcard addresses
• the ability to send from aliases
• good spam filtering (catch-alls attract junk)
• easy team handoff as the site grows

My shortlist:

Fastmail Zoho## My recommendation by scenario

1. One-person or small editorial team → Fastmail

I would lean toward Fastmail for a content partnership site.

Example setup:

• you@site.com → main inbox
• hello@site.com → alias
• partners@site.com → alias
• press@site.com → alias
• contributors@site.com → alias
• anything@site.com → catch-all

Fastmail supports custom domains, aliases, and catch-all wildcard aliases, and lets aliases route into inboxes without creating separate paid users. Fastmail Fastmail

2. You expect a team of writers/editors → Google Workspace

Choose Google Workspace if you also need:

• shared Google Drive folders
• Docs collaboration
• shared calendars
• Meet calls
• familiar Gmail workflow

For a media operation, those collaboration features can matter more than having hundreds of aliases.

3. You want the cheapest professional setup → Zoho Mail

Zoho is worth considering if you want:

• multiple addresses
• admin controls
• custom domain email
• lower cost

Zoho supports catch-all addresses that route mail sent to otherwise nonexistent addresses on your domain. Zoho

A setup I would avoid

I would avoid creating separate paid inboxes for every address:

• partners@
• press@
• events@
• submissions@

unless different people genuinely need separate logins. Aliases/groups are usually cleaner and cheaper.

Suggested structure for a content partnership site

Public-facing:

• hello@domain.com
• partners@domain.com
• press@domain.com
• submissions@domain.com

Internal:

• admin@domain.com
• billing@domain.com
• security@domain.com

Catch-all:

• *@domain.com → monitored inbox

One caution: catch-alls can increase spam volume, so pair them with strong filtering and periodically block abused addresses. Fastmail

If this is a single creator site, a multi-author publication, or a brand partnership marketplace, the best choice changes slightly.

For a content partnership site—where you may want addresses like hello@, partners@, submissions@, sponsors@, plus a catch-all—I’d narrow it to Fastmail, Zoho Mail, and Migadu.

My practical recommendation: Fastmail

Fastmail is particularly well suited if you're running the site yourself or with a small team. It supports a wildcard/catch-all alias such as *@yourdomain.com, and you can send from those addresses as well as receive them. Fastmail Fastmail

You could have:

• hello@site.com
• partners@site.com
• brands@site.com
• submissions@site.com
• press@site.com
• billing@site.com
• anything-else@site.com → catch-all

All can feed into one mailbox, while rules can sort messages by the address they were sent to. Fastmail also supports plus-addressing and subdomain addressing, which can be useful for generating distinct addresses without manually creating every variation. Fastmail

When I'd choose the others

Zoho Mail — I'd look at this first if keeping costs low is particularly important. It provides full hosted mail rather than merely forwarding, and current comparisons document substantial alias support and catch-all functionality. RottenWiFi Framekit

Migadu — worth considering if you expect multiple domains or a very large number of addresses. Its model is particularly oriented toward lots of addresses/domains without charging separately for every alias. Framekit

Cloudflare Email Routing — excellent if you only need incoming mail forwarded to an existing inbox. It has a genuine catch-all rule and flexible routing, but it isn't a normal hosted mailbox, so I'd avoid it as the primary system if you'll regularly send partnership emails from partners@... or hello@.... Cloudflare Docs

For your particular use case

I'd set it up as:

Domain → Fastmail → one primary mailbox → aliases + catch-all → folders/rules

That gives you the flexibility to create a new address whenever a partnership requires one without creating another paid mailbox.

If you tell me roughly how many people will use the email and whether you need 1 domain or multiple sites/domains, I can compare Fastmail vs Zoho vs Migadu on actual current pricing, alias limits, sending-from-alias behavior, and catch-all handling.

Yes. There are a few services that make this much easier, especially if the WordPress host handles the website but doesn't provide a mailbox.

The simplest options

• Cloudflare Email Routing — probably the easiest if you only need hello@yourblog.com to receive mail and forward it to Gmail/Outlook/etc. It's free, and Cloudflare can automatically configure the necessary DNS records. The catch is that it's forwarding, not a full mailbox, so sending from hello@yourblog.com requires an outbound email service. Cloudflare Docs Cloudflare

cloudflare.com

• Fastmail — a better fit if you want a real hosted mailbox at you@yourblog.com, rather than forwarding. Its setup wizard walks you through the domain/DNS configuration, and it supports aliases and multiple domains. Fastmail Fastmail

fastmail.com

• Zoho Mail — another conventional hosted-email option. You point your domain's MX records to Zoho, and it provides actual mailboxes at your domain. Zoho

zoho.com

• WordPress.com Professional Email — if by "managed WordPress" you mean WordPress.com, this is particularly turnkey. WordPress.com currently offers Professional Email, Google Workspace integration, or free forwarding directly from the hosting dashboard. WordPress.com WordPress.com

For a typical blogger

I'd think of it this way:

The interesting product opportunity here is actually a "managed email for managed WordPress" layer: the blogger enters their domain, chooses hello@, contact@, etc., and the service handles DNS, SPF/DKIM/DMARC, forwarding/mailbox setup, and potentially "send as" configuration without requiring the blogger to understand MX records.

If you're asking because you're considering building such a tool/service, there is definitely a gap worth exploring—the distinction between email forwarding and actual hosted email is particularly important.

Yes. The basic category you’re looking for is hosted email for custom domains: the WordPress host runs the site, while a separate service runs you@yourblog.com.

For a blogger on managed WordPress, the easiest options tend to be:

• Fastmail — particularly simple if you want a normal mailbox, calendar, contacts, and a clean interface. Its domain setup wizard can configure email authentication such as DKIM and SPF for you if Fastmail hosts the domain’s nameservers. Fastmail
• Google Workspace — Gmail with your own domain. WordPress.com has an integrated setup that can automatically add the necessary DNS records after domain verification. WordPress.com WordPress.com
• WordPress.com Professional Email — if the managed WordPress service is WordPress.com, this is the most integrated option; WordPress.com lets you add a mailbox directly from the hosting dashboard. WordPress.com
• Email forwarding — if you don't actually need a separate mailbox, forwarding hello@yourblog.com to your existing Gmail/Outlook inbox can be enough. WordPress.com currently offers free forwarding. WordPress.com

The important distinction

If your goal is “I want this to be ridiculously easy for nontechnical bloggers”, I'd separate the products into:

Forwarding:
hello@myblog.com → your existing Gmail
Cheap/simple, but you don't necessarily get a genuine standalone mailbox.

Hosted mailbox:
hello@myblog.com → mailbox operated by Fastmail/Google/etc.
You can send and receive directly as that address.

The WordPress site doesn't actually need to host the email. You just change the domain's MX/DNS records to tell the internet where mail for the domain should go. WordPress.com explicitly supports connecting third-party email providers this way. WordPress.com

If you're asking because you're considering building a tool specifically for bloggers that makes this setup one-click, there's actually an interesting product gap here: the hard part isn't hosting email itself; it's hiding the DNS, verification, SPF/DKIM/DMARC, migration, and deliverability complexity behind a WordPress-friendly onboarding flow.

For a SaaS marketer, I’d separate employee/inbox hosting from marketing campaign sending. Your marketing platform (e.g., HubSpot, Customer.io, Braze, etc.) should generally handle bulk sends, while your business mail host handles normal person-to-person email.

My recommendation: Google Workspace

Google Workspace is a strong default if your priority is deliverability + straightforward domain authentication + a mature business inbox.

• Custom-domain email: you@yourcompany.com
• SPF/DKIM/DMARC: fully supported.
• Deliverability tooling: Google provides Postmaster Tools for monitoring authentication, spam rates, delivery errors, and related signals. Google Help Google Help
• Good ecosystem for SaaS marketing: Gmail, Calendar, Drive, Meet, etc.
• Important: If you're sending bulk marketing mail, don't rely on your Workspace mailbox as your campaign-sending infrastructure. Gmail's requirements for bulk senders include SPF, DKIM, DMARC, alignment, and one-click unsubscribe for applicable marketing messages. Google Help

workspace.google.com

Worth considering: Zoho Mail

Zoho Mail is a reasonable alternative if cost is more important and you don't need Google's ecosystem. Zoho explicitly supports SPF, DKIM, and DMARC, along with custom-domain hosting. Zoho

zoho.com

One important architecture point

For a SaaS company, I'd configure it roughly like:

yourdomain.com → Google Workspace → employee email

mail.yourdomain.com / updates.yourdomain.com → marketing/transactional ESP → campaigns and automated SaaS emails

Then make sure SPF, DKIM, and DMARC are properly aligned for each sending system. Google specifically recommends authentication for every sending domain and recommends DMARC reporting so you can identify unauthorized senders. Google Help

If you tell me your approximate monthly email volume and whether you're sending through HubSpot, Customer.io, Mailchimp, SendGrid, etc., I can recommend the setup (including how I'd structure the domains/subdomains and DMARC policy).

For a SaaS marketer, I’d separate employee/business email hosting from marketing/transactional sending infrastructure. The best setup is often two systems:

1. Human mailboxes (you@company.com, sales@, partnerships@)
2. Marketing/transactional sending (news@, lifecycle emails, product emails, onboarding, etc.)

A provider having good DKIM/DMARC support is necessary, but deliverability depends heavily on domain reputation, authentication alignment, list quality, sending patterns, and complaint rates. SendX digitalhosting.com

My shortlist for a SaaS marketer

For SaaS marketing emails specifically

I would usually not send newsletters, onboarding flows, or product lifecycle emails directly from your mailbox provider. Use a dedicated email platform:

• Postmark — excellent fit for transactional SaaS emails (password resets, invites, receipts, alerts) where inbox placement and speed matter. Market Mystique
• Mailgun — flexible API-based sending, useful if you need more control over infrastructure. Market Mystique
• Amazon Simple Email Service — cost-effective at scale, but requires more technical ownership. SendX
• SendGrid — common choice if you want a mature marketing/transactional email ecosystem. Market Mystique

A SaaS setup I’d typically recommend

Company email

• Google Workspace or Microsoft 365
• Main domain: yourcompany.com

Marketing sending

• Dedicated subdomain:

• email.yourcompany.com
• updates.yourcompany.com
• mail.yourcompany.com

DNS authentication

• SPF configured
• DKIM enabled with provider-generated keys
• DMARC started with monitoring:

• p=none initially
• move toward enforcement (quarantine/reject) once you know legitimate senders are aligned

Tracking

• Use a custom tracking domain (avoid generic shared tracking domains where possible)

My default pick

For a typical SaaS marketing team:

• Google Workspace + Postmark → if you care most about reliability and a clean operational setup.
• Google Workspace + Mailgun/SES → if you have engineering support and expect higher volume.
• Microsoft 365 + your email platform of choice → if your organization is already Microsoft-based.

If you tell me your approximate monthly email volume (e.g., <10k, 100k, 1M+), whether this is newsletter/lifecycle marketing vs transactional, and whether you do cold outbound, I can narrow this down.

For a developer-run startup that wants both outbound sending and programmatic inbound mail, I’d narrow it to Resend, Postmark, and Mailgun.

My default choice: Resend

resend.com is probably the best fit if your application is modern TypeScript/Node/React-oriented.

• Outbound: clean REST API and official SDKs.
• Inbound: can receive mail on your own domain and POST structured email data to your webhook, including attachments. Resend Resend
• Developer experience: particularly straightforward API and good TypeScript ergonomics.
• Domain: you can use addresses like support@yourdomain.com rather than forcing users through a provider-specific address. Resend
• Pricing: current plans include sending and receiving; the free tier has a 100/day sending limit. Resend

A typical architecture would be:

yourdomain.com
       │
       ├── MX ──► Resend ──► POST /webhooks/email
       │                         │
       │                         ▼
       │                    Your application
       │
       └── API ◄──────── Your application
             │
             ▼
       outbound email

This is particularly nice for things like:

support@yourdomain.com
reply@yourdomain.com
notifications@yourdomain.com
billing@yourdomain.com

where inbound messages become application events rather than requiring you to maintain traditional mailboxes.

The important distinction

If by "email hosting" you mean actual human inboxes—e.g. employees need alice@yourdomain.com with Gmail/Outlook-like inboxes—I'd not use Resend as your primary mailbox provider.

I'd separate the two:

When I'd choose the alternatives

Postmark is compelling if transactional email deliverability is your highest priority. It supports both outbound API sending and inbound messages delivered to your webhook as parsed data. Postmark Postmark

postmarkapp.com

Mailgun is the one I'd investigate if you want very flexible email infrastructure. It has REST APIs for sending, inbound routing, storage/forwarding, and programmable routes. Mailgun Documentation Mailgun Documentation It also supports US/EU processing regions, which can matter for data residency. Mailgun Documentation

mailgun.com

What I'd actually build

For a typical SaaS startup, I'd use:

Resend + your own domain + Postgres + webhook endpoint

and keep your application as the source of truth:

                ┌──────────────┐
Outbound ──────►│    Resend    │
                └──────┬───────┘
                       │
                       ▼
                 recipient inbox

customer email
      │
      ▼
┌──────────────┐
│    Resend    │
└──────┬───────┘
       │ webhook
       ▼
┌──────────────┐
│ Your API     │
│              │
│ authenticate │
│ parse        │
│ store        │
│ trigger      │
│ reply        │
└──────┬───────┘
       │
       ▼
    Postgres

One caveat: don't point your entire domain's MX records at an API-only inbound provider if you also expect you@yourdomain.com to function as a normal human mailbox. Use a dedicated subdomain such as mail.yourdomain.com or otherwise design the MX setup carefully. Postmark, for example, explicitly recommends using a separate subdomain for inbound forwarding in many cases. Postmark

If you tell me roughly (1) monthly outbound volume, (2) how much inbound mail you expect, and (3) whether humans need normal inboxes, I can give you a much more concrete architecture and cost comparison.

For a developer-run startup that needs both sending and receiving on your own domain, I’d shortlist:

• Postmark — strong transactional email, inbound parsing/webhooks, straightforward API, and good deliverability focus. Postmark mails0.com
• Mailgun — probably the most flexible if inbound routing and email infrastructure are core requirements. StackBriefly
• Resend — excellent developer experience and a modern API, but its inbound model is somewhat less mailbox-like. Pingram
• Amazon SES — cheapest at scale, but requires substantially more infrastructure work. Nylas CLI

My default architecture: use Postmark or Mailgun for application email, with your domain verified via SPF/DKIM, and consume inbound mail through webhooks. If by “receiving” you mean full human mailboxes (e.g. alice@startup.com that people use in Gmail/Outlook), that’s a different requirement; I’d use a mailbox provider alongside the API provider rather than treating an email API as the mailbox.

For your requirements, I’d shortlist these:

• Google Workspace — Best fit if you want low admin overhead. Custom-domain Gmail, Drive, Docs/Sheets, Meet, Calendar, Chat, centralized admin, and strong remote collaboration in one ecosystem. TechRepublic Fit Small Business
• Microsoft 365 — Strong alternative if your team relies on Outlook, Word/Excel, Teams, or Microsoft identity/device management. Business Basic includes custom email, 1 TB/user, Teams, OneDrive, SharePoint, and admin controls. Microsoft Microsoft
• Zoho Workplace — Worth considering if minimizing subscription cost is particularly important while retaining integrated email, chat, meetings, files, and office apps. Zoho

My practical recommendation: start with Google Workspace unless your company is already heavily Microsoft-centric. It most directly matches “centralized email + collaboration + low administration.” TechRepublic

For a remote-first company that wants centralized domain email, built-in collaboration, and minimal IT/admin work, I’d shortlist these three:

Google Workspace

For your requirements, Google Workspace is the most straightforward fit. Its Business Starter plan currently includes custom-domain email, 30 GB pooled storage per user, Google Meet, and administration/security controls; Standard adds 2 TB per user plus expanded Meet and collaboration features. Google Workspace Google Workspace

The big advantage for a remote company is that email, shared documents, calendars, video meetings, chat, and file storage are all in one ecosystem. That reduces the number of separate services someone has to administer.

Microsoft 365

I'd choose Microsoft 365 instead if your employees already depend heavily on Word, Excel, PowerPoint, Outlook, and Teams. It provides the same basic centralized-domain-email model but is particularly well suited to Microsoft-centric organizations.

Zoho Workplace

Zoho Workplace is worth considering if keeping the per-user bill down is particularly important. Zoho bundles Mail with WorkDrive, Cliq, Meeting, Writer, Sheet, Show, Vault and other collaboration/administration tools. Zoho Zoho

Zoho also has centralized domain/user management, aliases, delegation and shared-mailbox functionality in its admin console. Zoho

My practical recommendation

For a typical 10–100 person remote-first startup, I'd start with Google Workspace Business Standard. It gives you a fairly low-admin setup while covering the collaboration layer rather than merely hosting mail.

If you're already an Office/Teams shop, use Microsoft 365 instead. If cost minimization is the dominant consideration, investigate Zoho Workplace.

One important consideration: don't optimize purely for email price. Once you include shared files, calendars, video calls, identity management, MFA, employee onboarding/offboarding, and shared addresses like support@ and sales@, the value of having one integrated platform becomes much more significant.

For a support team, I’d separate email hosting from shared-inbox/support workflow software. The strongest setups tend to use a mainstream mail host underneath and a shared-inbox layer on top.

My shortlist

1. Front + Google Workspace — strongest overall for support

Front is particularly well suited if support@, billing@, sales@, etc. need to be worked collaboratively rather than merely forwarded around.

Front supports shared inboxes with controlled teammate access, assignment, routing, internal collaboration, and moving conversations between inboxes. It also supports delegated individual inboxes. Front Help Center Front Help Center Front Help Center

It can connect Google Workspace or Microsoft 365 mailboxes, and Front has explicit domain-management/deliverability tooling for email setups. Front Help Center Front Help Center

Typical architecture:

Google Workspace → Front → Support team

You keep Google Workspace responsible for domains, mail accounts, authentication, SPF/DKIM/DMARC, and underlying mail, while Front handles the team support workflow.

2. Front + Microsoft 365

This is essentially the same model if your organization lives in Outlook.

Microsoft 365/Exchange provides the underlying mailboxes and domains, while Front provides the support-team interface. Front specifically supports connecting Exchange Online shared mailboxes and requires appropriate Exchange permissions such as Full Access and Send As. Front Help Center

This is particularly attractive if your team already uses Outlook, Teams, Entra ID, and Microsoft 365 administration.

3. Hiver

Hiver is worth considering if your team is heavily invested in Gmail and doesn't want to introduce a completely separate email interface.

Current comparisons describe Hiver as particularly suited to Google Workspace/Gmail-native workflows, while Front is more oriented toward complex routing and multi-channel support. Hiver

4. Google Workspace alone

Don't overlook the native option.

Google Groups can create a Collaborative Inbox, where team members can take conversations, assign them to colleagues, and mark them complete. Gmail delegation can also provide delegated access to individual mailboxes. Google Help

For a small support team, this can be considerably simpler than adding another platform.

5. Microsoft 365 alone

Likewise, Exchange Online Shared Mailboxes can provide addresses such as support@company.com without requiring a separate support platform.

I'd consider this when your requirements are primarily:

• Multiple people answering one address
• Delegated mailbox access
• Send-as permissions
• Centralized domain administration
• Outlook/Microsoft 365 integration

Once you need sophisticated assignment, collision prevention, routing rules, SLAs, automation, reporting, or multiple support channels, a dedicated shared-inbox system becomes more compelling.

What I'd choose

For a dedicated customer-support operation, I'd shortlist:

Front + Google Workspace if you want a flexible, purpose-built support workflow.

Front + Microsoft 365 if you're already an Exchange/Outlook organization.

Hiver + Google Workspace if staying inside Gmail is a major priority.

Google Workspace or Microsoft 365 alone if your support operation is small and you mainly need shared mailboxes rather than a full support platform.

One important distinction: Front/Hiver aren't really replacements for your domain/mail infrastructure. Think of them as the collaborative layer sitting on top of your email hosting. That architecture gives you much more flexibility when adding domains, addresses, employees, or changing support software later. Front Help Center

If you tell me your team size, number of domains, approximate support emails/day, and whether you use Google Workspace or Microsoft 365, I can narrow this to 2–3 options and compare their current pricing and limitations.

Microsoft 365/Exchange provides the underlying mailboxes and domains, while Front provides the support-team interface. Front specifically supports connecting Exchange Online shared mailboxes and requires appropriate Exchange permissions such as Full Access and Send As. Front Help Center

This is particularly attractive if your team already uses Outlook, Teams, Entra ID, and Microsoft 365 administration.

3. Hiver

Hiver is worth considering if your team is heavily invested in Gmail and doesn't want to introduce a completely separate email interface.

Current comparisons describe Hiver as particularly suited to Google Workspace/Gmail-native workflows, while Front is more oriented toward complex routing and multi-channel support. hiverhq.com

4. Google Workspace alone

Don't overlook the native option.

Google Groups can create a Collaborative Inbox, where team members can take conversations, assign them to colleagues, and mark them complete. Gmail delegation can also provide delegated access to individual mailboxes.

For a small support team, this can be considerably simpler than adding another platform.

5. Microsoft 365 alone

Likewise, Exchange Online Shared Mailboxes can provide addresses such as support@company.com without requiring a separate support platform.

For a support team specifically, I’d separate email hosting from help-desk/shared-inbox software. If you want the actual mailbox to be the collaboration layer, these are the strongest options:

My practical shortlist

1. Zoho Mail + TeamInbox — strongest all-in-one fit

Zoho has native mailbox delegation with read/write, Send As, and Send on Behalf permissions. Admins can control delegation centrally. Zoho Zoho

It also has actual shared mailboxes where messages stay in the shared mailbox rather than being duplicated into every team member's personal inbox. Zoho Zoho

For domain administration, Zoho supports multiple domains, subdomains, aliases, MX configuration, and centralized user management. Zoho Zoho Zoho

zoho.com

2. Microsoft 365 — best if you're a Microsoft shop

Exchange Online shared mailboxes are particularly good when you want addresses such as support@, billing@, and sales@ with centralized permissions and delegated access. The broader Microsoft ecosystem also makes it attractive if your team already lives in Teams, Outlook, SharePoint, and Entra ID.

microsoft.com

3. Google Workspace — best if you're a Google shop

Gmail delegation and Google Groups can work well for teams, particularly when your organization already uses Google Drive, Meet, Calendar, and other Workspace services. It's excellent as an organizational email platform, although I'd generally choose a dedicated shared-inbox product if support workflow is the primary requirement.

workspace.google.com

One important distinction

If by “support team” you mean something like:

Customer emails support@company.com → an agent claims the conversation → teammates can comment internally → tickets can be assigned → everyone sees the conversation history → reporting shows response times

then I'd look more seriously at Front, Missive, or a help desk rather than relying solely on traditional email hosting.

If you mean:

We just need 5–20 people to collaboratively monitor and respond from support@company.com, with strong admin/domain controls

then Zoho Mail + TeamInbox or Microsoft 365 are the places I'd start.

If you tell me your team size and approximate monthly budget, I can compare the actual 2026 plans and features—including per-user pricing, shared-mailbox limits, aliases, multiple domains, delegation, SSO, and audit/admin controls.

For a tech-savvy solo developer, I’d optimize for control without taking on the operational burden of running an SMTP server yourself.

My shortlist

• fastmail.com — probably the cleanest fit. Custom domains, aliases, IMAP/SMTP/JMAP, and straightforward DNS configuration. You keep DNS at your registrar/DNS provider and publish the MX/SPF/DKIM/DMARC records yourself. Current comparisons put its custom-domain plan around $5/user/month, depending on plan/billing. digitalhosting.com The Software Scout
• migadu.com — particularly interesting if you expect to have multiple domains, aliases, or lots of addresses. Its model is more domain/usage-oriented than conventional per-mailbox hosting, and it's aimed at technically comfortable users. digitalhosting.com Folio
• mxroute.com — worth considering if you want many domains/mailboxes without per-user pricing. It's more infrastructure-oriented and less of an all-in-one productivity product. digitalhosting.com
• proton.me — compelling if privacy/encryption is a major requirement, but less attractive if you specifically want conventional direct IMAP/SMTP access; Proton uses its Bridge for desktop-client integration. Framekit
• Self-hosted Stalwart/Mailcow — maximum control, but I'd only choose this if running mail infrastructure is itself something you want to do. Deliverability, IP reputation, reverse DNS, spam filtering, backups, patching, and monitoring become your responsibility. iTechGuides

What I'd choose for your requirements

Fastmail if you have one/few domains and want excellent email infrastructure without babysitting a mail server.

Migadu or MXroute if your developer use case means lots of aliases/domains and you care more about infrastructure economics than having the slickest mailbox UI.

For any of these, I'd keep authoritative DNS somewhere you control—e.g. Cloudflare or your registrar—and explicitly verify that the provider gives you:

MX → mail routing
SPF → authorized senders
DKIM → cryptographic signing
DMARC → enforcement/reporting
autoconfig/autodiscover → optional client convenience

One distinction I'd make: "full DNS control" doesn't require self-hosted email. You can retain complete control of your domain's DNS while delegating the actual mail transport and storage to a provider.

If you tell me whether you expect 1 domain / several domains and roughly how many aliases/mailboxes, I can narrow this to the most economical setup.

For a tech-savvy solo developer, I’d narrow it to Fastmail, Purelymail, and Migadu. All three let you keep your domain at your own registrar/DNS provider rather than locking DNS into the mail host.

1. Fastmail — polished managed choice

Fastmail is probably the most conventional choice if you want good email infrastructure without having to administer mail infrastructure.

You can keep DNS at your registrar and add Fastmail's MX, SPF, DKIM, and DMARC records yourself. Fastmail explicitly supports this "MX only" configuration, and its documentation provides the exact records. Fastmail Fastmail

It also has domain/user administration in its own control panel, plus routing and subdomain controls. Fastmail

Why I'd consider it: you get substantial DNS/domain control while outsourcing the unpleasant parts of running an email server.

2. Purelymail — very developer-friendly

Purelymail is particularly interesting if you don't care about a big productivity-suite ecosystem.

Its custom-domain setup explicitly has you manage DNS at your registrar, with records for ownership verification, MX, SPF, DKIM, and DMARC. Once the domain is verified, you can create users from the administration portal. Purelymail

Purelymail also doesn't sell domains, so your domain and DNS remain independently managed—which is a nice property for someone who thinks of the domain as infrastructure rather than an account belonging to the email vendor. Purelymail

Its September 2026 update also added automatic client configuration support (AutoConfig/AutoDiscover). PurelyMail News

3. Migadu — especially good for lots of addresses/domains

Migadu is worth looking at if your "solo developer" setup means lots of project addresses, aliases, or domains.

Migadu supports external DNS as well as its own nameservers, provides DNS diagnostics, and supports DKIM/SPF/DMARC. It explicitly describes its service as standards-based SMTP/IMAP/POP3/webmail rather than requiring a proprietary client. Migadu Migadu

That's appealing if you have things like:

• me@example.com
• billing@example.com
• alerts@project-a.dev
• hello@project-b.com
• several development/project domains

My practical shortlist

For your stated requirements, I'd investigate them in this order:

1. Fastmail — if you want the least operational friction.
2. Purelymail — if you're comfortable with a more utilitarian service and want your domain/DNS setup to remain very independent.
3. Migadu — if multiple domains and many addresses are a major consideration.

One architectural recommendation: keep the domain registered separately from the email provider, and keep authoritative DNS somewhere you control (e.g. your existing DNS provider). Then the mail provider is essentially just an MX/DKIM/SPF/DMARC dependency. That makes switching providers much less painful. Fastmail explicitly supports this arrangement, as do Purelymail and Migadu. Fastmail Purelymail Migadu

If you tell me roughly how many domains, mailboxes, aliases, and outbound transactional emails you expect, I can narrow this down further and compare the current pricing/limits.

Purelymail is particularly interesting if you don't care about a big productivity-suite ecosystem.

Its custom-domain setup explicitly has you manage DNS at your registrar, with records for ownership verification, MX, SPF, DKIM, and DMARC. Once the domain is verified, you can create users from the administration portal. Purelymail

Purelymail also doesn't sell domains, so your domain and DNS remain independently managed—which is a nice property for someone who thinks of the domain as infrastructure rather than an account belonging to the email vendor. Purelymail

Its September 2026 update also added automatic client configuration support (AutoConfig/AutoDiscover). news.purelymail.com

3. Migadu — especially good for lots of addresses/domains

Migadu is worth looking at if your "solo developer" setup means lots of project addresses, aliases, or domains.

Migadu supports external DNS as well as its own nameservers, provides DNS diagnostics, and supports DKIM/SPF/DMARC. It explicitly describes its service as standards-based SMTP/IMAP/POP3/webmail rather than requiring a proprietary client.

That's appealing if you have things like: