Closed betaInvite-only access. Ask for an invite

Email is a chain of custody. Nobody was keeping the record.

rootmail sends your email and can account for every piece of it — including the email you send on someone else's behalf.

one core · two wings · one record per message

Grow past the basics and email becomes four products.

A service for receipts

does not know who asked you to stop emailing them

A tool for newsletters

does not know which addresses bounced yesterday

A tool for sales sequences

does not know either of the two above

A spreadsheet of opt-outs

does not know nothing enforces it at send time

None of them share a contact, a reputation or a history. The day you switch, you re-import everything and start your deliverability at zero.

You never re-platform. You turn on the next layer.

01

Send

One message, authenticated, with a record of what happened to it.

messages · audit_entries · append-only

02

Converse

The reply comes back to a thread instead of a mailbox nobody reads.

threads · one inbox · both wings

03

Prove

A signed bundle a third party can check without trusting us.

ed25519 · pins a content hash

Two front doors. One product.

For people who just want to reach their people

One place to design an email, build a list, send a campaign, follow up and read what comes back.

studio · campaigns · inbox · no code

For developers who would rather not become email operators

The same product, through a REST API, a typed Node SDK and a CLI. The same data, the same records.

idempotent sends · webhooks · sub-tenancy

An unsubscribe means everywhere.

suppressions · enforced at send · both wings

A number without a window is not a number.

every figure · window · method

We never draw a solid line through something we did not observe.

opened · inferred · hollow, forever

If email is the part of your product you cannot account for, that is the part we built.