Unlimited mailboxes, on a domain you own

A mail server does not spend money on people. It spends money on disk, on bandwidth, and on the outbound relay that carries what you send. A mailbox receiving four messages a week costs almost precisely what an empty one costs: the row in a table and the bytes it holds.

Per-seat pricing measures your headcount instead, because headcount is what a buyer will agree to grow. It is a fine model for software where every extra person is extra load — a video call, a shared document, a seat in a CRM. It is a strange model for a mailbox, and it produces the situation everyone in this category recognises: an address for the accountant who checks it monthly, priced identically to the founder living in it.

The consequence is not just the invoice. It is that per-seat pricing makes you ration addresses. Teams end up cramming four humans behind one login, or routing a department through a personal address, because the honest arrangement costs $84 a year more. Removing the count removes the rationing, and the rationing was always the bigger cost.

It means we do not count. There is no soft cap that triggers an email at forty mailboxes, no fair-use number withheld until you cross it, and no higher tier that unlocks the twenty-first address. The panel will make the mailbox.

It does not mean an account is a pool other people can draw on. One account is one organisation — a person, a household, a team, a company — using it for its own mail. An agency running twenty of its own projects on one account is exactly what this is for. An agency putting twenty clients on one account is not: each of those clients is its own organisation, and reselling mailboxes is the one use the terms refuse outright.

There is deliberately no number attached to that. A number would be a target to sit just under, and it would be wrong for somebody. If an account stops looking like one organisation’s own mail we write and ask, and nothing is suspended over fair use before that conversation.

There is no account-level sending limit, and that phrasing is chosen rather than rounded up. Outbound mail leaves through Amazon SES, which bills per message, so a claim that sending is unlimited would be one we could not fund. What actually bounds it is a per-sender throttle, which exists so that one compromised mailbox cannot empty an account’s reputation overnight, and the bounce and complaint rates that any relay watches.

In practice that means normal mail — a team, a household, a busy founder — never meets a limit. Bulk, marketing and newsletter sending is refused, and it is refused as a product decision rather than by a quota: shared sending reputation is the asset every mailbox on the platform depends on, and it is not ours to spend on a campaign.

Every one of them gets the full protocol set, because there is no tier holding anything back: IMAP on 993, POP3 on 995, SMTP submission on 465, all over TLS, plus JMAP and webmail. Aliases, catch-all addresses and Sieve filters are in the same plan for the same reason.

Each mailbox can carry its own storage cap if you want one, which is useful for the address that receives every automated report. Read the storage page before you set one, though: a cap is a ceiling, never a reservation, and it can only ever subtract from what a mailbox could otherwise use.