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 arrives with its own editor, its own list, its own unsubscribe state. Then sales adds a sequencing tool — a third sender, a third reputation, a third place someone can complain. Before long, "email" is three bills, three dashboards, and three versions of the truth about the same customer.

The absurd part is that it's all the same channel. The same domain. Often the same recipient, on the same day.

One substrate, in layers

rootmail is built as one platform with layers, so you adopt exactly as much as you need:

• The send layer — one API for transactional, marketing, and sales mail, with idempotency keys for exactly-once delivery, scheduling, priority lanes, and Handlebars templates.
• The trust layer — automatic DKIM, SPF/DMARC/BIMI guidance, suppression checked before every send, a 0–100 reputation score from real outcomes, and an append-only audit trail for every message's life.
• The audience layer — contacts, lists, drip sequences that exit on reply, list-based campaigns, and a shared inbox for what comes back. Each campaign and sequence carries its own engagement funnel.
• The operating layer — an in-app AI assistant that doesn't just answer questions about your email but does the work: builds templates and sequences, runs sends, and diagnoses problems ("why did this bounce?") with the actual evidence, inside your plan and permissions.

One audience. One suppression state. One audit trail. One bill.

Sub-tenancy from day one

The moment your product sends email for your customers — invoices from their brand, notifications from their domain — most stacks fall apart. rootmail treats sub-tenancy as a first-class primitive: every customer gets their own verified sending domain with isolated DKIM keys and isolated reputation, managed through the same API you already use. A platform with a thousand customers is a thousand clean senders, not one shared blast radius.

Trust as a feature, not a promise

Email is evidence. Companies get asked to prove a message was sent, when, and what it said. rootmail's audit log is append-only — events are written, never edited — and you can export Ed25519-signed proof bundles that anyone can verify without trusting us. Retention policies (redact or delete on your schedule) are configurable per workspace, so compliance is a setting, not a project.

Honest economics

Usage-based pricing that scales with what you send, a free sandbox that never expires, yearly plans that show exactly what you save, and an upgrade path that appears where you actually hit a limit — not buried three menus deep. When you outgrow a tier, the platform tells you what fixes it and what it costs.

We built rootmail because email infrastructure should be one coherent thing you can trust and operate — not a committee of tools that have never met. If that's the mess you're in, the migration importer takes about ten minutes, and your reputation comes with you.