Internal platform · engineering only

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

MailOps accepts SMTP from our apps, routes it across SendGrid, AWS SES and Scaleway TEM, and lets an LLM explain — and fix — bounce storms before customers notice.

% delivery rate M emails / month + adapters, one API

Built for the 3 a.m. bounce storm

Everything an on-call engineer needs, nothing they don't.

⇄

Smart vendor routing

Route each domain to SendGrid, AWS SES or Scaleway TEM — automatically fail over when a vendor's reputation dips.

◈

LLM bounce diagnosis

An Anthropic model reads bounce clusters, explains the root cause and proposes a routing fix for one-click approval.

⛨

Circuit breakers

Automatic per-vendor breakers stop the bleeding the moment hard bounces spike past your threshold.

◷

Full message journey

From SMTP acceptance to final webhook — every hop, header and SMTP reply, searchable in seconds.

✓

Suppression guard

Global suppression list keeps chronic complainers and dead addresses out of every vendor at once.

▤

Deliverability analytics

Volume, delivery and bounce rates by vendor, domain and category — with a read-only API for pulling data into your own stack.

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.

Every provider.
One routing brain.

Domain-level rules decide who carries your traffic — across any of your 32+ connected adapters. 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
%
bounce rate
auto failovers
LLM diagnoses approved
Example routing rules
acme.com marketing & bulk → SG SendGrid → failover → SE AWS SES
app.acme.com transactional → SE AWS SES → failover → TE Scaleway TEM
eu.acme.com EU residency → TE Scaleway TEM → failover → SG SendGrid

Any provider in.
One brain on top.

32+ adapters feed one normalized event stream — and MailOps adds the layer no provider ships: circuit breakers, LLM diagnosis on redacted metadata, and routing fixes you approve with one click.

32+
Adapters in, one event stream out
<60s
Circuit-breaker re-route
0
Message bodies sent to the LLM
1
Suppression list across every vendor
⛨

Breakers trip first

Per-vendor hard-bounce spikes pause a sender automatically — before the damage reaches your domain reputation.

◈

The LLM names the cause

An Anthropic model reads redacted bounce clusters across vendors and explains the root cause in plain language. Message bodies never leave your stack.

✓

Approve, don't debug

One click applies the proposed routing rule and drains queued mail down the new path — no 3 a.m. dashboard spelunking.

Switch vendors by changing one line.

MailOps exposes the same API surface as your provider. Repoint your existing integration at MailOps — same endpoints, same payloads, same auth headers. Nothing to reintegrate, on any vendor.

  • ✓ No reintegration — your existing API calls keep working
  • ✓ Provider-compatible endpoints — SendGrid-style interfaces already supported
  • ✓ Same delivery semantics — webhooks and suppression behavior unchanged
See the switch for every vendor →
# your existing SendGrid integration
- https://api.sendgrid.com/v3/mail/send
+ https://mailops.eu/v3/mail/send
# same payloads, same auth — one-line change
# routing, suppression & events unchanged
Heard on the bridge

The people the pager calls

Field reports from the teams carrying mail for every product surface.

“The pager went off at 3 a.m. with the diagnosis already written. I approved the failover from my phone and went back to sleep.”
MV Maren VossStaff SRE, Checkout Team
“We found a suppression-list sync bug that had been silently eating password resets for weeks. Nobody had a dashboard for that.”
IK Ilya KadeDeliverability Lead
“Vendor reviews used to be an argument. Now we open MailOps and the routing evidence settles it in thirty seconds.”
PL Petra LindqvistVP Platform Engineering
Incident review
Case file · verified

The SendGrid reputation dip that customers never saw

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

47s
from spike to failover
0
customer tickets opened
100%
of queued mail re-routed
Read the postmortem Reconstructed from the routing ledger and vendor webhook archive for the week of the incident.
Security

Guardrails you can point to.

Vendor keys vaulted and rotated, 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 GDPR EU data residency DKIM / SPF / DMARC enforced SSO & SCIM