Order confirmations, password resets, newsletters, and the replies people send back — one system, one contact list, one address of your own.
four example emails, and what rootmail recorded about each
msg_01J9Q7F2XKB4M0RVTC8Hana@sunsetvillas.com
A pixel loaded at 09:41:55. Roughly a third of these are a mail client prefetching an image, so we draw it hollow. Always.
msg_01J9QB4T7NC2X8HKD3M0dana@lakeshore.co
A redirect was followed at 08:38:02. A security scanner opening every link in a message follows it the same way a person does, and we cannot tell them apart — so this stays hollow too.
msg_01J9QC8W2PD5R1TFN6Y4sam@northgate.co
Solid, where the open above it is hollow. A reply is not a guess: their message arrived at our inbound server and is in the thread. It is the one engagement signal we witness rather than infer.
msg_01J9QDF6ZQ0B8VMH4K2Sold@vantagepartners.io
The provider's own words, kept verbatim. The address went onto your suppression list at the same second, so the next send to it never leaves — and nothing is drawn past the bar, because nothing happened past it.
One editor, one contact list, one address of your own. Below is a single email at three moments: the morning it went out, the minute she wrote back, and the day somebody asked us to prove it.
Everything here is also one API call. If you have developers, they get the same product.
Tuesday, 09:14 — a customer books a room, and your site asks rootmail to send the confirmation.
Filled means the mail provider told us it happened. Hollow means we are guessing — an “open” is a tracking image loading, and a mail app can load it with nobody in the room. Nothing was recorded for a click, so that one is left blank rather than counted as a no.
11:47 — she writes back. It is a conversation now, not a send.
follow-up cancelled 11:47 · contact replied
Her reply arrives in the shared inbox with the original underneath it, so whoever is on duty can answer without asking who sent what. And the follow-up email that was queued for her tomorrow morning cancelled itself the second she replied — nobody has to remember to stop it.
Three weeks later — a customer says the confirmation never arrived.
signature valid (Ed25519) · content hash matches
This is the receipt for the receipt: what went out, to whom, at what second, sealed at the moment of sending so nobody — including us — can edit it afterwards. Download it and their lawyer, their auditor or their bank can check the seal themselves, without taking our word for anything.
Who it's for
Six businesses with nothing in common, except that somebody is waiting on an email.
booking software, a CRM, a clinic system, a marketplace
Every one of your customers sends from their own web address, with their own contacts, their own bounces and their own score. When one of them uploads a list they should not have, rootmail warns you, slows that customer down, and then stops them — before it costs you the rest.
a studio running email for a dozen businesses
Run every client from one login, and switch into a client to see only their work. Each keeps their own domain, their own list and their own history, so handing an account back at the end of a contract is a handover, not an excavation.
a clothing label, a gym, a morning newsletter
Announce the new drop to your customers and let your website send its own order confirmations. Design everything by dragging, with no code and no developer. Replies come back to a shared inbox, and new subscribers get a welcome series that sends itself.
a developer, or a two-person team with one
Stop hand-rolling email inside every backend. One API key and a POST; retries never double-send. Templates, sequences and domains stay editable in the dashboard afterwards — by you, or by the client you built it for.
a school office, a five-a-side league, a choir
The term dates, the fixture change, the one email that has to reach every parent. Write it by dragging, send it to the list you already keep, and see what actually reached them. Nobody has to be the email person.
a consultancy, a landlord, a freelancer with a list
No developer, no email person, and no budget for either. The parts that normally need somebody watching them — bounces, unsubscribes, the DNS records behind your domain — watch themselves and tell you when something needs a decision.
Most senders are none of the six — a council office sending twelve emails a week, a lab, a letting agent. It is the same product underneath, and the free plan is sized for exactly that.
An ordinary Tuesday
One small business, one day, nothing on fire. This is the whole product at the size most people actually use it — and exactly one of these six hours needed somebody at a desk.
06:00
recorded, nothing needed doing
4,812 subscribers. You wrote it yesterday and scheduled it.
09:14
recorded, nothing needed doing
Your website asks. Delivered from your address four seconds later.
11:47
somebody had to act
It lands in the shared inbox, original underneath. Tomorrow's follow-up cancels itself.
14:20
rootmail did something about it
The mail bounces. On your do-not-send list the same second, so it never counts twice.
16:05
rootmail did something about it
The newsletter stops. Their receipts and password resets keep coming — that is what they asked for.
22:00
recorded, nothing needed doing
Your DNS was re-checked every hour. Had a record gone, you would have had an email within the hour, and six hours to put it back.
It does not break. It quietly starts landing in spam folders, and you find out from a customer three weeks later asking why they never got their receipt.
Two numbers decide it: how many of your addresses reject the mail, and how many people mark it as spam. rootmail watches both, separately for every sender on your account, and does something about them before anybody has to notice.
The whole job is to move the moment you find out. With rootmail that moment is one complaint in a thousand, while it is still a list you can fix. Without it the moment is the one where a mail provider has already decided about you — and by then the decision covers everything you send.
Out of everyone you mailed. It is the number mailbox providers use to decide whether the rest of your email is worth delivering, and it moves slowly enough that by the time you notice, weeks of mail have already gone to spam folders.
The three points below are ours. We set them deliberately under the point where an email provider starts acting on its own — because when the provider acts, it acts on your whole account, and everything you send stops at once.
What you see with rootmail
What you see without it
1 person in every 1,000 marked it as spam
0.10%complaint rate
rootmail does this
rootmail emails you, and names the client whose mail it is
This is where you find out
what usually happens
nothing happens, and nobody tells you
3 people in every 1,000 marked it as spam
0.30%complaint rate
rootmail does this
that client is slowed to 60 emails an hour — held back, never dropped
what usually happens
nothing happens, and nobody tells you
5 people in every 1,000 marked it as spam
0.50%complaint rate
rootmail does this
that one client is stopped. Everyone else keeps sending.
what usually happens
your email provider suspends the whole account. You hear about it from a customer.
This is where you find out
Example figures for one client, counted over the last 7 days — and never on fewer than 20 emails the mail provider actually ruled on, so one bad afternoon on a brand-new client cannot trip it.
One of your customers buys a mailing list. Two days later your own mail is landing in spam folders and you have no idea which of them caused it.
In rootmail each client sends from their own web address and is measured on their own. When one starts going wrong, we email you, then slow that client down, then stop them — at four in the morning, without waiting for you to look.
The thick line is the part everybody shares — one provider account, one set of sending addresses, one history built up over months. Each client hangs off it. Press the button and watch what happens when one of them uploads a bought list.
A bought or scraped list is full of addresses that no longer exist. Every one of them is a rejection, and mail providers read a rising rejection rate as a sender who does not know who their own customers are.
0.4%
sending normally
a normal list
3.1%
sending normally
climbing, still under the line
6.0%
we email you
past 5% — something is wrong with this list
8.4%
slowed to 60 an hour
past 8% — held back, never dropped
11.2%
this client is stopped
past 10% — everyone else keeps sending
Counted over the last 7 days, and never on fewer than 20 emails the mail provider actually ruled on — so a brand-new client with three sends and one bounce is not treated as a 33% failure.
Already sending through Amazon SES or Mailgun? Keep them. Paste in your credentials and your mail still leaves on your account, on your addresses, with the months of sending history you have already built up. Disconnect rootmail and nothing has moved: you are exactly where you started. If you do not have a provider, use ours.
Setting up a domain is five DNS records. Here they are, in order.
Five choices that quietly decide whether your email helps you or hurts you. On the left is how rootmail arrives, out of the box, before you touch anything. On the right is how they are usually set instead.
None of them is a setting you have to find. That is the point of putting them here: you should be able to see what you are getting without reading a manual.
how rootmail arrives
credentials checked live before they are stored
how it is usually set
you start your sending history over from zero
how rootmail arrives
enforced in the send pipeline · scoped by message type
how it is usually set
one unscoped list stops both
how rootmail arrives
test sends excluded from scoring
how it is usually set
the test never actually left the building
how rootmail arrives
one export call · one erase call
how it is usually set
and deleting them forgets that they opted out
how rootmail arrives
signed · independently verifiable · content hash included
how it is usually set
a screenshot proves nothing to anyone
Every answer comes out of one record. Point at a question and the part of the record that answers it is marked — and under each question is the exact field we read it from, so you can check us.
And where we do not know, the record says so. An “open” is a tiny image loading, and roughly a third of the time it is a mail app fetching pictures with nobody in the room — so we draw an open hollow and a confirmed delivery solid, everywhere, for ever. You will not find a chart here that quietly turns a guess into a fact. It costs us a tick in a comparison table, and it is the reason the rest of the numbers on this page are worth reading.
How many emails you send, and how many contacts you keep. They are billed separately, so if you only ever send receipts you never pay for a contact list, and if you only send a newsletter you are not paying per send.
Everything else is on every plan, the free one included: the drag-and-drop editor, the shared reply inbox, the AI assistant, per-client scoring, signed records, the API. We charge for volume, never for features.
rootmail is in closed beta, so every account is capped at 12 sends a day right now
One account, and you are never asked to choose. Use one meter, the other, or both — they are billed independently, so a meter you do not use costs nothing.
Receipts, resets, alerts — priced by send volume.
Size it
$32/mo
$8/block · $320/yr — 2 months free
Past your blocks it's $0.4/1,000. Sending never stops.
| Blocks | Per block | Emails / month |
|---|---|---|
| 1–4 ← you | $8 | up to 100,000 |
| 5–20 | $7 | up to 500,000 |
| 21+ | $6 | 525,000+ |
Campaigns, sequences, replies — priced by audience size.
Your contacts
Starter
60,000 emails/mo · 5,000/day · 3 audiences
$60/mo · $600/yr
GrowthRecommended
100,000 emails/mo · 10,000/day · 10 audiences
$90/mo · $900/yr
Pro
200,000 emails/mo · 20,000/day · 50 audiences
$140/mo · $1,400/yr
Pay yearly, get two months free.
One bill for everything — both meters and any extras. Buying more capacity part way through a month never re-bills what you have already paid for.
on the free plan too — you pay for volume, never for features
Import your contacts (or paste them in), group them into a list, and send a campaign to the whole list from the dashboard — or set up a sequence that emails people automatically over days. Already on another provider? You can bring your contacts and your unsubscribe/suppression list straight over from a SendGrid, Postmark, or Mailgun export, so you keep your history and don't email anyone who opted out.
Four things, none of them a promise about the inbox — nobody can make that promise. We authenticate with DKIM, SPF and DMARC and generate the records to publish. We stop sending to addresses that bounced or marked you as spam, before each send. We score you 0–100 from what actually happened over the last 7 days, and name what is moving it. And we re-check your DNS hourly, so a record that disappears is something you hear from us within the hour.
You can start sending right away while you get set up. To send from your own address (you@yourbusiness.com), you add a few DNS records we generate for you — copy, paste into your domain provider, and we verify them for you. The dashboard walks you through it and tells you the moment everything checks out. You never click 'verify' twice: we do the waiting.
Mail is encrypted in transit and credentials are stored only in protected form. Two-factor sign-in, login lockout and per-person permissions protect the account. Every request is scoped to your organization and workspace, and that scoping is covered by tests written to fail if it regresses — which is more useful than an absolute promise about the future. You can export everything or delete your account at any time.
You pay for two things and nothing else: how many emails you send, and how many contacts you keep. Sends: 3,000 sends a month free, then blocks of 25,000 with rates that drop as you grow, and going over never stops your sending. Contacts: free up to 500, then the size of your list sets the price. Every feature is on every plan including the free one; extras like seats, workspaces, SSO, AI credits and dedicated IPs are bought one at a time if you want them. Yearly is 2 months free, and sandbox sends are always free.
Yes — point a webhook endpoint at your app and rootmail sends signed, idempotent events for the full lifecycle (delivered, opened, clicked, bounced, complained) plus inbound replies, with a per-endpoint delivery log you can inspect and replay.
Yes — that's what client domains are for. Each client sends from their own name and web address, with their bounces, complaints, contacts and history scored and stored separately. Clients share one provider account and one IP pool, which we draw rather than hide: what we do about it is measure each client on its own and throttle, then pause, the one going wrong. Agencies run all their clients from one account; most other senders never need this.
Those are separate products for separate jobs, so you pay two bills, keep two contact lists, and build two sending reputations — for the same customers. rootmail puts every email your business sends in one place, which is why an unsubscribe here means everywhere. The sharper difference is what we draw: an open is a tracking pixel firing, and we render it as an inference rather than at the same weight as a delivery the provider confirmed.
Type in your web address. We look up the records that tell mail providers your email is really from you, and show you which are in place and which are missing. It takes about five seconds, and it is the same drawing you have been reading all the way down this page: solid where we checked it ourselves, dotted where we could not.
no account · nothing sent · nothing stored