Why we built rootmail

Every company sends email, and almost every company ends up with the same mess. You start with one service for receipts and password resets. Then marketing wants newsletters, so a second tool shows up. Sales wants sequences, so does a third. None of them share a contact list, a sender reputation, or a history — and the day you want to switch, you re-import everything and start your deliverability over from zero.

We kept hitting that wall, and we noticed something: the underlying job is the same every time. Take a message, render it, authenticate it, deliver it, track what happened, and don't email people who asked you to stop. The differences between “transactional,” “marketing,” and “sales” are mostly product packaging on top of one identical pipeline.

One data model, all the way up

So we built rootmail around a single core. The same model that sends one welcome email scales up to give every one of your customers their own verified sending domain, and up again to produce cryptographically signed proof of a message's entire lifecycle. You don't migrate between products as you grow — you switch on the next layer.

• Send transactional, marketing, and sales mail from one place.
• Give each of your own customers an isolated sending domain when you need it.
• Prove exactly what you sent, signed and timestamped, when compliance asks.

For everyone who sends

The other thing we refused to accept was the split between “tools for marketers” and “APIs for developers.” A founder should be able to point and click their way to a campaign; an engineer should be able to do the identical thing with a typed SDK. rootmail is one product with two front doors — a no-code dashboard and a clean API — over the same data.

Getting into the inbox and being able to prove what you sent shouldn't be add-ons. They should be the product.

That's the bet. If it resonates, start free and send your first email today — or tell us what you're building. We read every note.