About
We ship transactional email. That's it.
SESMetric runs the receipts, password resets, alerts, and system mail that has to land in an inbox the second it leaves your server. No newsletters. No marketing. No drip funnels. Just delivery.
Story
Started in 2018 because the existing options were either too expensive or too unreliable. Still feels like the right gap to fill.
Mission
Make a transactional message land — every time, fast.
Password resets, payment receipts, alert webhooks. The mail that breaks a product if it doesn't arrive within seconds. That is what SESMetric is for.
We deliberately don't offer broadcast features. The moment a stack tries to do both marketing and transactional on the same IPs, the transactional side loses.
Why teams pick us
Single-purpose stack
Transactional only. No marketing-blast UI that drags reputation down for everyone.
Reputation isolation
Bad senders get routed off the shared SES pool before they hurt anyone else's deliverability.
Global footprint
Sends from us-east-1 with PoPs in 4 regions, signed by SPF + DKIM out of the box.
Engineer-friendly support
Email + chat answered by people who can read SMTP logs. No tier-1 deflection.
Timeline
2018
Founded
Started as a side project to fix transactional deliverability for one company. It worked, so we kept going.
2019
First million
Crossed the first million sent at >99.5% inbox placement on the major mailbox providers.
2021
100+ customers
Hit 100 paying companies, mostly in fintech, infra tooling, and developer platforms.
2023
Recognised
Picked as 'Best ESP under the radar' by TechReview. We didn't apply — they emailed us.
Values
Four rules we wrote on the wall in 2018 and never edited.
Land the mail
Latency and inbox placement are the only metrics that count. The dashboard is the receipt, not the product.
Quiet about your data
SOC 2 Type II, single-region storage by default, no third-party trackers in the dashboard.
Boring tech wins
Postgres, Redis, ClickHouse, Go, FastAPI. No NewMagicQueue. If a piece breaks at 3am, an oncall engineer can read it.
Read the logs first
Support is people who SSH into the relay before they ask you to clear your cache.