Pricing & ownership
Why Pay Per Domain? The Case for Unlimited-Domain Email Hosting
Draw two lines on a napkin. One steps up every time you register a domain and never comes back down. The other runs flat across the page no matter how many names you add. Every argument about multi-domain email comes down to one question: where do those two lines cross, and how long do you spend on the wrong side of it?
This article does the arithmetic. No prices — you do not need them to see the shape — just the two curves, a worked break-even in relative units you can run yourself, and a migration sequence for getting a portfolio off per-domain billing once the math has made up your mind.
The two curves, named
Pick one unit and hold it fixed: the cost of a single hosted mailbox for a single month. Call it one unit. Everything below is measured in that unit, so there are no prices here — only ratios, which is all a break-even needs.
The rented curve. Under per-domain or per-mailbox pricing you pay, roughly, one unit per domain per month. Hold three domains and you spend three units a month; hold thirty and you spend thirty. The line's slope is your domain count, and it keeps climbing for as long as you own the names.
The owned curve. A one-time software purchase is a single upfront lump — call it P units — after which your only ongoing cost is the infrastructure it runs on, billed to you directly and essentially flat however many domains you point at it. Three domains or thirty, the slope barely moves.
So one line's steepness grows with your portfolio and the other does not. That is the entire argument; the rest is just finding where they cross.
A break-even you can run yourself
Put rough magnitudes on it. Say the one-time purchase P is worth about twelve months of a single hosted mailbox — twelve units — and the owned setup's flat monthly infrastructure is a small fraction of one unit, call it a sixth. Cumulative cost after N months is then:
- Rented: D × N units (domains times months).
- Owned: 12 + (1/6) × N units (the purchase, plus a flat trickle).
Break-even is the month where those two match. The table shows how fast it arrives as the portfolio grows:
| Domains held | Rented cost / month | Break-even arrives around |
|---|---|---|
| 3 | 3 units | month 4–5 |
| 10 | 10 units | early in month 2 |
| 30 | 30 units | inside the first month |
Read the extremes. At three domains the owned model has paid for itself before the fifth month is out. At thirty, it is ahead almost immediately — the one-time purchase is smaller than a single month of the rented meter. And these are only the break-even points; every month afterward the rented line keeps adding its full slope while the owned line barely ticks up — so the gap you see at break-even is the smallest it will ever be.
The cost that never shows on the invoice
There is a second line item the meter hides. When each domain carries a monthly fee, you start pricing your own ideas before you have them. A name you would have grabbed on a whim now has to justify a recurring charge, so you do not grab it. The pricing has quietly cast a vote on which projects you are allowed to start. A flat model removes that veto: registering a name and giving it mail costs you nothing extra, so the portfolio can grow at the speed of your curiosity instead of your budget.
A per-domain fee does not just cost money. It taxes your curiosity and makes you count before you create.
The migration order: moving a portfolio off per-domain billing
Deciding is one thing; doing it without dropping a single password reset is another. Here is the exact order — each step gated on the one before it, lowest-stakes names first and the ones you cannot afford to miss last — so the switch from a metered setup to a flat one never leaves a domain unable to receive:
- Inventory everything first. List every domain, the addresses that actually receive mail on each, and where each currently points. The names you forgot you owned are the easiest wins — and the ones most likely to be quietly bouncing already.
- Stand up the owned system on your own account before you move a single live name, and prove it out end to end with one throwaway test domain you do not mind breaking.
- Move the forgettable names first. Re-point the lowest-traffic, lowest-stakes domains — parked ideas, defensive misspellings — before anything you depend on. These are your rehearsal, chosen because a mistake on them costs nothing.
- Verify before you continue — this is the gate. For each migrated name, send a message in and a reply out, and confirm both land and authenticate. Do not touch the next wave until this one passes. The whole reason the order exists is that nothing advances past an unverified step.
- Cut over the critical names last. Only once the pattern is proven, flip MX on the domains you cannot afford to miss, then watch them for a few days with the old subscription still paying in parallel.
- Cancel per-domain billing only at the very end, once every name both receives and sends from the new setup. A short overlap costs a little; a gap costs a bounced password reset. That final cancellation is the moment the rising line finally goes flat.
Where this is the wrong math
The model only favors ownership when the rented slope is steep enough to matter. If you own a single domain and always will, the crossing point sits far enough out that a simple hosted mailbox is the honest answer — buy the convenience and stop reading. The owned curve wins specifically when your names outnumber your people and keep climbing; below that line, the arithmetic is close to a wash and you should optimize for ease instead.
The dividend the math does not capture
One payoff never shows up on either curve. When you run your own mail on your own account, you stop renting permission to read your own correspondence — no tier that can be narrowed, no feature pulled out from under you, no billing cycle that quietly decides your access. And with a zero-access design the archive is encrypted at rest under a key only you hold, so the host stores ciphertext it cannot open. That is a limit on who can read your mail, not a promise that anything is unbreakable: mail still arrives in the clear and is encrypted on receipt, and sending still depends on a provider to relay it. The curve that matters most, in the end, is the one measuring how much of all this you actually control.
- Is unlimited-domain hosting really free?
- No, and anyone claiming that is overselling. You pay once for the software and you pay the modest infrastructure cost to run it on your own account. What you do not pay is a fee that multiplies with every domain you add.
- At how many domains does this start to make sense?
- There is no single number, but the logic kicks in as soon as your domains outnumber your people and keep growing. If you already hesitate before registering a name because of the email cost, you are past the line.
- What happens to my cost when I add a domain?
- Nothing changes in the deal itself. There is no per-domain fee and no seat count, so an added domain does not raise a subscription. You simply point its records and it starts receiving.
- What am I actually paying for, then?
- The software, once, and the real infrastructure it runs on, paid by you directly to the platform. That is the whole cost structure: a thing you own plus the ground it stands on.