Business email hosting, in one screen
Every comparison of business email hosting ranks on price and storage. Those two numbers are the least likely to break your setup. What breaks setups is a plan that will not let your mail client connect, or a sending ceiling you meet on your third campaign.
| What it is | Mailboxes on your own domain, hosted by a provider, with MX records pointed at their servers. |
| The trap nobody prices | Three of the six providers here gate IMAP and SMTP behind a tier or a piece of software. A cheap plan you cannot connect Outlook to is not cheap. |
| Google Workspace | 2,000 messages per day per user, but only 100 recipients per message when you send through POP or IMAP. |
| Microsoft 365 | 10,000 recipients per day, up to 1,000 recipients per message, and 30 messages per minute. Identical across every Business and Enterprise plan. |
| Zoho Mail free tier | Five users on one domain, and Zoho states plainly that IMAP, POP and Active Sync are not included. |
| Not what this is for | Mailbox hosting is not a bulk sender. Application mail and campaigns belong on a relay or an ESP. |
A business email hosting service does one narrow thing: it runs mailboxes on a domain you own, so that people write to you at your company name instead of at a consumer provider. The comparison articles that rank for this all sort the same providers by starting price and gigabytes. Both of those move, and neither of them is what people come back and complain about six weeks later.
What people complain about is the plan that does not do the thing they assumed every email plan does. This page compares six business email services on the axes that actually differ, and every figure below comes from the provider’s own documentation rather than from another comparison article. Prices are deliberately absent: the vendors render them from a calculator that changes by region, term and headcount, so any number printed here would be wrong for most readers and stale for the rest.
What business email hosting is, precisely
Business email hosting means a provider operates the mail servers that receive messages for your domain, and you point your domain’s MX records at them. You keep the domain. They keep the mailboxes, the spam filtering, the webmail and the storage.
That is the whole of it, and the distinction that matters is what sits either side. A business email server you run yourself gives you total control and total responsibility, including reverse DNS, patching and blocklist monitoring. A corporate email service, at the other end, bundles mailboxes into a productivity suite where email is one component among documents, calendars and video. Most small teams are buying the middle: mailboxes on a domain, nothing more.
Whichever you choose, you still publish and own the authentication records. SPF and DMARC live in your DNS zone, not the host’s, and a provider that configures them for you has still left you accountable for what is published there.
Six providers, on the axes that differ
Every figure in this table is quoted from the provider’s own pricing page or documentation.
| Provider | IMAP and SMTP access | Stated sending ceiling | Storage |
|---|---|---|---|
| Google Workspace | Yes, on paid plans | 2,000 messages per day; 10,000 total recipients per day; 100 recipients per message over POP or IMAP | 30 GB pooled per user on Starter, 2 TB on Standard, 5 TB on Plus |
| Microsoft 365 | Yes | 10,000 recipients per day; up to 1,000 recipients per message; 30 messages per minute | Varies by plan |
| Zoho Mail | No on the Forever Free plan; yes on paid | Not published as a single figure | 5 GB per user free; 5 to 10 GB on Mail Lite; 50 GB plus 50 GB retention on Mail Premium |
| Fastmail | No on Business Basic; yes on Standard and Professional | Not published as a single figure | 6 GB per user on Basic, 60 GB on Standard, 150 GB on Professional |
| Proton Mail | Only through Proton Mail Bridge, paid plans only | Not published as a single figure | Varies by plan |
| Migadu | Yes | Per account, not per mailbox: 2,000 out per day on Maxi, 500 on Standard, 100 on Mini, 20 on Micro | Unlimited mailboxes per account |
Read the second column before the fourth. Storage is a number you can grow into. Protocol access is a yes or no that decides whether the plan works at all with the software your team already uses.
The three ways a plan blocks your email client
The assumption almost everyone makes is that an email account is an email account, and that Outlook, Apple Mail or Thunderbird will connect to any of them. Three of the six providers here break that assumption, each in a different way.
Check this before you buy, not after
Zoho’s Forever Free plan states “IMAP/ POP/ Active Sync not included”, which makes it a webmail-only account. Fastmail’s Business Basic plan does not carry the use with third-party apps entitlement that its Standard and Professional plans do. Proton Mail does not expose IMAP or SMTP at all: desktop clients connect through Proton Mail Bridge, which runs a local mail server on your machine, and Proton states that Bridge “is available only with a paid plan that includes Proton Mail”.
None of these are defects. Webmail-only free tiers are a reasonable way to give away a product, and Proton’s design follows from end to end encryption: a standard IMAP client cannot read encrypted mail, so the Bridge decrypts locally instead. They are simply the kind of constraint that a price and storage comparison cannot show you, and the kind that makes a migration fail on the first afternoon.
If your team lives in a desktop client, that requirement outranks every other line item. The protocols and ports behind those connections are the same everywhere; what differs is whether the provider opens them for your tier, and increasingly whether they require an app password or OAuth rather than your login password.
Sending limits, and why the number depends on how you send
A business email service is sized for correspondence, and every provider enforces that with limits. The useful detail is that the limit is often not a single number.
Google Workspace
Google publishes a daily cap of 2,000 messages per user, with 10,000 total recipients per day, 3,000 external recipients per day and 3,000 unique recipients per day. A single message can address 2,000 recipients, of which at most 500 may be external. Trial accounts are cut to 500 messages per day.
The line that catches people is the per message recipient cap on the protocol path: 100 recipients per message for POP and IMAP users, against 2,000 through the web interface, and 500 through the Gmail API. The same mailbox therefore behaves differently depending on how the message was submitted, which is why a script that worked in testing fails when it is pointed at the IMAP endpoint. Google also notes that limits differ again for organisations using its SMTP relay service.
Microsoft 365
Exchange Online sets a recipient rate limit of 10,000 recipients per day, a recipient limit customisable up to 1,000 recipients in a single message, and a message rate limit of 30 messages per minute. Microsoft documents these as identical across Business Basic, Business Standard, Business Premium, Enterprise E1, E3, E5 and F3, which is unusually clean: upgrading the plan does not raise the ceiling.
Migadu, and a different model
Migadu bills per account rather than per mailbox and allows unlimited mailboxes and addresses, but applies its limits at the same level: outgoing messages per day are capped at 2,000 on Maxi, 500 on Standard, 100 on Mini and 20 on Micro, and those quotas are shared by every mailbox and domain on the account. The trade is the opposite of the usual one. Adding people costs nothing and consumes headroom, where the per user providers charge for each person and give each of them their own allowance.
Provider by provider
Google Workspace
The default recommendation for a reason: familiar interface, strong filtering, and every third party integration written for it first. Storage is pooled per user, starting at 30 GB per user on Business Starter and rising to 2 TB on Standard and 5 TB on Plus, and Google caps the Starter, Standard and Plus plans at 300 users. Connection details for clients are in the Google Workspace SMTP, IMAP and POP3 settings.
Microsoft 365
The right answer when the organisation already runs Office desktop applications, or when procurement wants one vendor for the suite. Exchange Online’s limits are the same on every tier, so the plan choice is about the applications rather than the mail. The Microsoft 365 client settings cover the server names and authentication requirements.
Zoho Mail
The most common answer to “business email free”: the Forever Free plan hosts one domain for up to five users with 5 GB of mail storage each. Read the protocol line before committing, because that plan is webmail and mobile app only. Paid plans restore client access, with Mail Lite at 5 to 10 GB per user and Mail Premium at 50 GB plus 50 GB of retention storage. Zoho runs regional servers, so the hostnames differ by the datacentre your account sits in, which the Zoho Mail settings reference sets out.
Fastmail
An independent, ad free option with a long track record, sold both to individuals and to businesses. Business Standard gives 60 GB per user and Professional 150 GB, both with custom domains and third party app access; Business Basic is 6 GB per user and does not carry that entitlement. Fastmail requires an app password rather than your account password for client connections, which the Fastmail settings page walks through.
Proton Mail
The choice when confidentiality is the requirement rather than a preference. The cost is the one described above: no direct IMAP or SMTP, and desktop clients work only through Bridge on a paid plan. For a team that lives in webmail and on mobile, that constraint never surfaces; for one standardised on Outlook, it is the deciding factor. The Proton Mail settings page covers what Bridge exposes locally.
Migadu
The specialist pick, and the one that changes the arithmetic for teams with many addresses. Flat rate per account, unlimited mailboxes and domains on the upper plans, and quotas that belong to the account rather than to any mailbox. It suits an agency running mail for several domains, and it suits nobody who needs high volume from a single tier. The Migadu settings page covers the connection details and the no per mailbox limits model.
What business email hosting is not for
The most expensive mistake in this category is using a mailbox plan as a sending platform. The limits above make the reason concrete: 2,000 messages a day, or 30 a minute, is correspondence volume, and the moment a newsletter or an application’s notification mail starts flowing through the same account you are one campaign away from throttling, and one complaint spike away from a suffering business domain.
Application and campaign mail belong on separate infrastructure. Notification and receipt traffic goes to a provider built for it, covered in the transactional email services comparison, and mail that must leave from your own systems goes through an SMTP relay. Keeping those streams off the mailbox domain is the same reasoning that keeps cold outreach off it, and it costs far less than repairing a reputation afterwards.
Choosing, in the right order
- Does the plan open IMAP and SMTP? If your team uses desktop clients, this is a filter, not a feature. It eliminates the Zoho free tier and Fastmail Business Basic immediately, and it makes Proton a Bridge decision rather than a mail decision.
- Does the ceiling clear your real volume? Count recipients rather than messages, since that is what most providers meter, and remember that automated mail from your website counts too.
- Per user or per account? Five people with one address each and one person with forty aliases are different problems, and the second is where Migadu’s model wins.
- Do you need the suite? If documents and calendars come with the decision, the choice is really between Google Workspace and Microsoft 365, and the mail is a detail.
- Who controls DNS? Whoever it is has to be available on cutover day. The migration is a DNS project more than a mail project.
One last practical note. Whatever you pick, the clients your team uses will need server names, ports and an authentication method, and increasingly an app password or OAuth rather than the account password. The directory of desktop, web and mobile email clients covers what each one supports, and the per provider settings pages linked above carry the values.
Frequently asked questions
Which hosting service is best for business email?
There is no single answer, and the useful question is narrower: which one clears your constraints. Google Workspace and Microsoft 365 are the defaults for teams that also want documents and calendars, and Microsoft publishes identical mail limits on every tier so the plan choice is about the applications. Zoho is the budget option once you are past the free tier’s protocol restriction. Fastmail suits teams that want mail without a suite. Proton suits confidentiality requirements. Migadu suits many addresses on few people.
Is Zoho email still free?
Yes. Zoho still publishes a Forever Free plan that hosts email for one domain with up to five users and 5 GB of mail storage per user. The restriction to check is not the storage but the access: Zoho’s own pricing page states that IMAP, POP and Active Sync are not included on that plan, which makes it a webmail and mobile app account. If you intend to connect Outlook, Thunderbird or Apple Mail, you need a paid plan.
Is there genuinely free business email hosting?
There is, at small scale and with conditions. Zoho’s free tier is the best known and covers five users on one domain, without client protocol access. Some registrars and web hosts bundle a mailbox or two with a domain or hosting plan. What no free tier gives you is headroom: storage is small, sending ceilings are low, and support is minimal. Free works for a founder and a couple of aliases, and stops working roughly when the second employee arrives.
Can I use my own domain with any of these?
Yes, that is the point of the category, and you keep ownership of the domain throughout. You point its MX records at the provider and publish the authentication records they specify. One detail worth knowing in advance: a CNAME cannot coexist with MX and TXT records at the same name, so a domain whose root is a CNAME to a website builder can need rearranging before mail will work on it.
Can I send marketing or bulk email from business email hosting?
You should not, and the published limits explain why. Google caps a Workspace user at 2,000 messages a day, and Exchange Online allows 30 messages per minute and 10,000 recipients a day. Those are correspondence figures. Beyond the throttling, running campaigns through the mailbox that receives your customer replies puts your business domain’s reputation on the line for every send. Campaigns belong on an email service provider and application mail on a relay.
Should my website and my email be with the same host?
They do not have to be, and separating them is usually the more robust arrangement. Bundled mailboxes from a web host are convenient and often cheap, but they tie your mail to the fortunes of a hosting account, and website migrations are a common way to lose email: changing nameservers or the root A record can drop the MX and TXT records that mail depends on. Keeping DNS somewhere you control, with mail and web pointed at whoever is best at each, survives that.
What do I need to change in DNS to move to a new host?
At minimum the MX records, the SPF record and the DKIM selectors your new provider issues, plus a DMARC policy if you do not already publish one. The safe sequence is to lower the TTL on those records a day ahead, add the new provider’s records alongside the old ones, cut the MX at a quiet hour, verify delivery in both directions from outside accounts, and only then remove what is obsolete. Most failed migrations are a forgotten SPF include or a DKIM key that was never republished.
What is the difference between business email hosting and a business email server?
Hosting means somebody else runs the mail servers and you point your domain at them. Running your own server means you own the machine, the IP address and everything attached to it: patching, spam filtering, storage, backups, reverse DNS on the sending IP and the blocklist monitoring that goes with it. Self hosting is a legitimate choice for teams with the operational appetite for it. For most businesses the hosted option costs less than the hours the alternative consumes.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
