Email hosting pricing: plans, fees and buying questions

Hosting is priced like capacity rather than like headcount. You are buying domains, mailboxes, storage, and message volume, and the bill responds to how much of each you consume rather than to how many people you employ.

That difference matters, because the two shapes fail in opposite directions. A per person price is predictable and punishes you for addresses that are not people. A capacity price absorbs extra addresses cheaply and surprises you when one mailbox grows, one mailing goes out, or one introductory term ends. This page is about spotting which surprises apply to you.

What to take away

• The first term and the renewal term are frequently different prices. Find the second number before you sign, not eleven months later.
• Count what your bill is actually measured in. Domains, mailboxes, aliases, storage, and message volume are separate meters and rarely move together.
• Mail bundled with web hosting has no visible price. Work out what you would pay for equivalent mail alone before treating the bundle as free.
• Price the exit as a line item. Migration help, overlapping months, and the retained archive are real costs at the end of every contract.

The meters your bill is measured in

Read any offer and identify which of these it counts. Most count several, and the one that binds you is rarely the one in the headline. Where an offer uses a term loosely, the standard definitions of cloud service models are a fair reference for deciding whether two offers are even the same kind of purchase.

• Domains. How many separate domain names can receive mail on one account, and whether an additional domain is a line item or included. Organizations with a trading name, an old name they still accept mail on, and a country variant discover this quickly.
• Mailboxes versus aliases. A mailbox stores mail; an alias points at one. Whether aliases are unlimited, capped, or chargeable is the single largest variable in what a small organization actually pays.
• Storage, and whether it is pooled. A shared allowance across the account behaves very differently from a fixed amount per mailbox, especially when two people hold most of the mail.
• Message volume, or a sending cap. Some offers meter outbound mail. All of them limit it somewhere, and the limit only becomes visible when you cross it, which is why it belongs in the console setup rather than in a later surprise.
• Retention and archiving. Frequently a separate product rather than a setting.
• Address reputation. Whether you are on shared sending infrastructure or have an address of your own is sometimes a paid option, and it changes what your neighbors can cost you.

Write down which meters apply to you, then find each candidate's number for each. Offers that look similar usually differ on two of the six, and those two are where your money goes.

The introductory term is not the price

The most reliable way to misjudge hosting cost is to read the first number and assume it repeats.

Ask, in writing, and record the answers:

• What is the price on renewal, at the same specification?
• Is the initial rate tied to a term length, and what is the price if you choose a shorter one?
• What happens at renewal if you do nothing: does it renew automatically, at which rate, and how much notice do you get?
• Which components renew separately? A domain name, a certificate, a backup add-on, and the hosting itself may all renew on different dates at different rates.
• Can you leave partway through a term, and is anything refunded?

None of this is hidden information, and almost nobody asks for it before committing. Do the arithmetic across three years rather than one, and compare that total, which is the number you will actually pay.

What the entry tier holds back here

The pattern in hosting differs from the pattern in per person services. What the cheapest tier withholds is usually operational rather than administrative, and the line that grows on its own is retention, because nobody ever deletes mail. Deciding what to keep by what it is rather than by how much room is left is the whole discipline of digital preservation, and it applies to a mail bill as directly as to an archive:

Commonly held back	Why you notice
Backup with a usable restore, as opposed to the provider's own disaster recovery	Their backup protects the platform. Yours has to be able to restore one deleted mailbox
Log retention long enough to investigate anything	An incident is discovered after the window in which the evidence existed
Sending capacity above a modest daily cap	Discovered by an account suspension during a mailing
Any support commitment with a time attached	Matters exactly once, and matters a great deal then
Administrative delegation, so more than one person can run it	Otherwise every task queues behind one login
Migration assistance	Charged for, or absent, at the moment you most want it

The useful move is to decide which of these you need before comparing headline rates, because they set the tier, and the tier sets the price. A comparison of entry tiers is only meaningful if the entry tier is one you could actually run on, and several of these items are things you can test during a trial rather than take on trust.

The bundled case

When mail comes with your website hosting, its price is invisible, which makes it feel free and makes it impossible to evaluate.

Split the bundle on paper. Ask what the hosting costs without mail, or what a comparable mail-only offer would cost for the same mailbox count and storage. Then judge the difference against what you give up: the two decisions become one, so moving your website later means moving your mail at the same time, and support is generalist rather than specialist. The hosting overview sets out what each arrangement costs you operationally; this is the same question expressed as money.

For a very small team the bundle is often the right answer anyway. Make it a decision rather than an accident.

Build the model yourself

Fill this in with figures you look up from each provider's current published terms. The numbers change; the fields do not.

Line	What to enter
Domains receiving mail	Including old names and variants you still accept
Mailboxes	Real ones that store mail
Aliases and forwarding addresses	And whether each is free, capped, or charged
Shared and role addresses	And whether they consume a mailbox
Storage today	Measure it rather than estimating
Storage in three years	Your growth rate applied to the figure above
Pooled or per mailbox	And the ceiling that applies
Sending volume	Peak day, not average
Backup and retention	As a separate line, because it usually is one
Log retention required	Driven by what you would need after an incident
Support tier required	The one with a time commitment, if you need one
First term price	At the term length you would actually choose
Renewal price	The number that matters
One-off costs	Migration, setup, any assistance charged separately
Cost of leaving	Overlap months, export effort, and any early termination term

Then run it twice, at today's size and at the size you would consider a good outcome in three years. If the second number is unacceptable, you have learned it now. The same discipline applied to a per person offer produces a different set of fields, which is why the per seat model is worth filling in separately rather than adapting.

Common questions

Is unlimited storage worth paying for?

Find out what it means first. In most offers it describes a limit that is not published rather than the absence of one, and there is usually a fair use provision. The useful questions are what happens as one mailbox becomes very large, and whether performance or search changes with size.

Does a dedicated sending address pay for itself?

It depends entirely on volume. Below a certain amount of regular mail, a dedicated address has no established reputation and can perform worse than a well run shared one. Ask the provider what volume makes it worthwhile on their platform, and treat a confident answer with no volume attached as a sales answer.

Should we pay annually?

Annual is cheaper and fixes your specification for the term. If your headcount or storage is moving quickly, the monthly premium buys real flexibility. If they are stable, it does not.

How do we avoid paying for capacity we do not use?

Measure before you buy, and measure again before every renewal. Most organizations carry mailboxes for people who left, aliases nobody uses, and a storage tier chosen years ago. An hour with the console before renewal is usually the highest paid hour of the year, and it fits neatly alongside the administrative review you should already be doing.