Shared, dedicated or self-run: comparing email hosting arrangements

Shared, dedicated or self-run: those are the three email hosting arrangements most small organizations weigh. The choice decides whose machines your mailboxes sit on, whose staff get out of bed when delivery stops, and whose sending reputation you borrow.

That is an operations question, not a features one. Two offers with identical descriptions can behave completely differently on the one morning it matters.

Decide how much of the running you want to be responsible for. Then check what each arrangement does to you on a bad day.

What to take away

Shared hosting, dedicated providers and self-run servers compared

Compare them on three criteria: cost per user per month, control over the mailbox, and what you can do during an outage. List prices here are as of 2026 and move with billing term and annual commitment.

Bundled with your website: Bluehost, HostGator, GoDaddy, Namecheap

Mail comes with the package that runs your site. It is convenient and usually cheap: shared plans from Bluehost, HostGator and GoDaddy typically cost $3 to $12 per month, and Namecheap sells extra mailboxes as Private Email at roughly $1 per mailbox per month.

Bundling also ties two unrelated decisions together: moving your site later means dealing with your mail at the same time. Support is generalist, mail is rarely the provider's main business, and administrative controls tend to be thin.

On a bad day you sit in a general support queue with everyone whose website is down.

A dedicated mail provider: Google Workspace, Microsoft 365, Zoho Mail, Fastmail, Rackspace Email

Here mail is the product. Google Workspace Business Starter lists at about $7 per user per month; Microsoft 365 Business Basic sits near $6 on an annual commitment; Zoho Mail Lite is about $1. Fastmail Individual runs about $5, and Rackspace Email lists at $2.99 per mailbox per month.

You get the administrative apparatus, a published status page, and staff whose specialty is deliverability. Google's Workspace status dashboard, the Microsoft 365 status page and Fastmail's status history are all public.

You are one of a very large number of customers, so individual attention is limited. The systems are built by people who do this all day.

Two of these differ from the pack. Proton Mail sells end-to-end encryption between Proton accounts, and Fastmail sells standards-based mail with no office suite attached.

On a bad day there is usually a status page telling you what is happening, which is worth more than it sounds.

Self-managed: Mailcow, Mail-in-a-Box, iRedMail, Zimbra, Postfix and Dovecot

You run it, or you pay somebody to run it. The common stacks are Mailcow or Mailu in Docker, Mail-in-a-Box on a plain Ubuntu server, iRedMail or Zimbra for a heavier install, and hand-built Postfix with Dovecot.

A virtual server from DigitalOcean, Linode or Hetzner typically costs $5 to $20 per month. Amazon SES relays outbound mail at about $0.10 per 1,000 messages. You still own patching, spam filtering, storage, backups, and building sending reputation from nothing.

This is a legitimate choice for organizations with a specific reason and the staff to sustain it. It is a poor default, because the failure modes are quiet and the recovery is on you.

The question that separates these three is not which is best. It is what you will actually do at nine in the morning when mail stops, and which arrangement leaves you with an action rather than a wait.

One delivery pointer, and that is the architecture

A domain's mail is delivered wherever its MX records say, and for most organizations that is one destination.

Before any change, inventory everything that sends as your domain, because each item has to be carried across deliberately. The inventory is always longer than anyone expects.

Shared reputation is a real cost

On shared infrastructure, your mail leaves from addresses that other customers also use. Their behavior becomes part of the history that receiving systems evaluate when they decide what to do with your message.

You cannot inspect this directly, but you can ask about it, and the answers are informative:

A provider that has thought about this will answer readily. A provider that treats the question as unusual is telling you something.

Deliverability is not a feature you buy, but a standing you maintain.

The guidance the National Institute of Standards and Technology publishes for small business cybersecurity is a reasonable orientation to the practices that keep it intact.

Availability is the feature nobody trials

Everyone evaluates storage and interface. Almost nobody evaluates what happens during an outage, which is the thing they will actually care about.

Ask for the public status history rather than a percentage in a contract. A published record of past incidents, with honest write-ups, tells you more than an availability figure, because it shows how the provider behaves when something breaks.

Google Workspace and Microsoft 365 both advertise 99.9% uptime commitments. Those numbers say less than the incident history behind them.

Then ask the questions that determine your own exposure:

What "unlimited" is measuring

Storage claims deserve a specific reading, because mail volume only grows and nobody deletes anything.

Find out whether the allowance is per mailbox or pooled across the organization. Google Workspace pools Business Starter storage at 30 GB per user, Microsoft 365 Business Basic gives each user a 50 GB mailbox, and Zoho Mail Lite lists 5 GB per user. Those models behave very differently as you grow.

Check what happens when a mailbox hits its limit: does incoming mail bounce, get held, or get silently discarded? See whether archived mail, deleted items and shared mailboxes count against the same allowance. Ask how long deleted mail is recoverable, the only real protection against a mistake.

Where an offer is described as unlimited, ask what the acceptable use policy says, because that is where the actual limit is written.

The exit is a data question

Assume you will leave eventually, and check the exit on day one rather than at renewal.

You need to export complete mailboxes in a standard format, with folder structure, timestamps and attachments intact, for every account including shared ones, without asking permission and without a fee decided at the time.

MBOX covers most providers, PST covers Microsoft 365, and Maildir or EML covers smaller hosts. Google Takeout handles Workspace exports; Microsoft's compliance portal exports to PST.

Run that export during your trial on a real mailbox, then open the result. An export you never tested is a plan, not a capability.

Two other things belong in the same check. How long does the provider retain your data after cancellation, and can you get it back within that window? And is your domain independent of the provider, so that leaving is a change of destination rather than a change of address?

Questions to put to a host before you commit

Question seven links hosting to who controls identity. The guide to what you are actually buying with business email sets out that question.

Strong authentication is the single control with the largest effect here. For that conversation, the public guidance on authenticator strength and account recovery is a better basis than a vendor's feature grid.

Common questions

Should mail live with my website or somewhere else?

Separating them is usually the safer default, because it lets you change one without disturbing the other. Bundling is defensible for a very small team that values one bill and one support contact, as long as the administrative controls are adequate and the exit is clean.

Is self-managed mail cheaper?

Rarely, once staff time is counted. The costs that catch people out are not the server: they are spam filtering, storage growth, patching, backup verification, and the months it takes to build sending reputation from nothing. A $6 virtual server running Mailcow still needs somebody to own it.

How long does moving take?

The delivery change is quick. The preparation is not, and it is dominated by the inventory of everything that sends as your domain and by the volume of mail being copied across. Plan the preparation, and expect a period where both old and new destinations need watching.

Does more storage solve the mailbox limit problem?

It postpones it. What actually solves it is knowing whether the allowance is pooled, what happens at the limit, and what your retention policy should be, which is a decision about obligations rather than about capacity.