MailOps
Get started
MailOps

SMTP in · 30+ vendors out · diagnosed by AI

Mail that actually arrives, diagnosed when it doesn’t.

MailOps accepts SMTP from your apps, routes it across 30+ delivery vendors — SendGrid, Mailgun, Postmark, Amazon SES, Resend and more — and lets AI explain — and fix — bounce storms before customers notice.

View live dashboard How it works

SMTP EDGE · ROUTING LEDGER · N°03

Carrying mail for every product team

Checkout Billing Identity Onboarding Invoicing Growth Campaigns Support Desk CRM Sync Data Exports Mobile Alerts Dunning Status Pages

The quiet math

99.2% Delivery rate

Every accepted message is delivered — or explained, with the SMTP receipt attached.

960M Emails per month

Marketing and transactional traffic carried across 30+ vendors, one API.

<60s To fail over

When a circuit breaker trips, traffic re-routes before the queue backs up.

04 teams · one routing brain

Who it serves

Built for the teams behind the send button

Deliverability runs on people who refuse to fly blind. MailOps works the way they work.

On-call Engineers

Get paged with the root cause already attached — and a routing fix you can approve from the alert.

Watch it work

Deliverability Leads

Reputation, bounce mix and suppression across every vendor and domain, in one place.

Watch it work

Platform Engineers

One SMTP edge and one API for the whole company — no more per-app vendor wiring.

Watch it work

Engineering Leadership

Delivery rate as a product metric, with the receipts to stand behind it in any review.

Watch it work
Dark horizon under a faint green glow, scattered with star-like points

Always on · 24/7 · Global

The mail stream never sleeps.

Neither does the routing brain.

SMTP accepts, vendor webhooks and bounce clusters settle into one timeline — scored, searchable, and ready when you are. While your team is offline, MailOps keeps watching: every deferred delivery retried, every reputation dip absorbed, every anomaly read and written up before the morning stand-up.

3 a.m. is rush hour somewhere

EU marketing sends land while APAC users reset passwords. The routing layer treats both as first-class traffic — no business-hours bias.

Every webhook, one timeline

Delivery, bounce and complaint events from every connected vendor flow into a single ledger. Searchable in seconds, retained for a year.

Diagnosis before the pager

Bounce clusters are scored and read by AI as they form — the 02:14 alert already carries the root cause and the proposed fix.

How the engine runs

Watch a bounce become a fix.

Accept

Every app hands mail to one SMTP edge — no per-team vendor wiring, no stray API keys.

Route

Domain-level rules pick the right vendor for every send — SendGrid, Mailgun, Postmark, SES — weighted by live reputation.

Diagnose

AI reads each bounce cluster, explains the root cause and proposes the fix — one click approves it.

Case file · verified

Incident review

The SendGrid reputation dip that customers never saw

A bounce storm hit marketing traffic mid-campaign. The breaker tripped, TEM took the load, and AI had the postmortem drafted before the stand-up.

47s from spike to failover
0 customer tickets opened
100% of queued mail re-routed

Reconstructed from the routing ledger and vendor webhook archive for the week of the incident.

Read the postmortem
Routing-ledger chart of the bounce storm: spike at 14:02, breaker trip at 14:03, re-route to Mailgun at 14:03:47, baseline by 14:09
Fig. 01 — bounce storm absorbed: 47 seconds to re-route
Mesh · 13 connections

Vendors

30+ vendors. One routing brain.

Every provider your stack speaks — SendGrid, Amazon SES, Mailgun, Postmark, Brevo, Mailjet, Resend, Scaleway TEM and more — sits behind one edge. When a circuit breaker trips, MailOps re-routes in under a minute and opens a diagnosis you can approve with one click.

Routing · live rules

Vendor routing

Every provider. One routing brain.

Domain-level rules decide who carries your traffic — across any of your 30+ connected vendors. When a circuit breaker trips, MailOps re-routes in under a minute and opens a diagnosis you can approve with one click.

THIS WEEK

messages accepted
412,380
bounce rate
0.61%
auto failovers
4
LLM diagnoses approved
97

EXAMPLE ROUTING RULES

  • acme.com marketing & bulk SendGrid failover AWS SES
  • app.acme.com transactional AWS SES failover Scaleway TEM
  • eu.acme.com EU residency Scaleway TEM failover SendGrid

Migration

Switch to MailOps. Keep your code.

MailOps speaks the same API as your current provider — repoint one line and mail keeps flowing. No SDK swaps, no payload rewrites, no re-verification.

See the migration guide

Privacy, by architecture

Your mail is yours. We don’t process it. We don’t store it.

We don’t process

MailOps never reads, analyses, or transforms message content. The routing decision needs only the envelope — recipient, sender, and vendor replies.

We don’t store

Message bodies pass through in memory and are gone the moment the vendor accepts them. What persists is metadata: timestamps, SMTP codes, routing outcomes.

The vendor is the processor

SendGrid, Amazon SES, Mailgun — whichever vendor carries the message processes and transmits it under their own data agreement. MailOps sits on the side — a routing layer, not a mailbox.

Read the full privacy policy
Audit posture · current

Security baked into the architecture.

TLS everywhere — every SMTP accept, every vendor hand-off, every webhook. Vendor credentials and signing keys live in HashiCorp Vault, encrypted and rotated on schedule, never in a repo or config file. Suppression synced across every provider, and a full audit trail on every routing change — not just badges you can’t read.

SOC 2 Type II TLS everywhere HashiCorp Vault GDPR Data residency controls DKIM / SPF / DMARC enforced SSO & SCIM

Deliverability, autonomous. Mail on autopilot.