OutSend and Amazon SES
This is the least adversarial comparison on the site, because OutSend sends through SES. The question is not which provider — it is whether you want to build the control plane yourself.
Unbeatable per-message economics
Nothing else comes close at volume. If cost per message is the dominant factor and you have the engineering time, raw SES is the rational answer.
Enormous scale and reliability
It is AWS. The sending infrastructure is not the part that will let you down.
You may already have it
If you are on AWS, the account, the IAM, and the billing relationship already exist.
We are the part you were about to build
Event storage, suppression handling, bounce classification, reputation scoring, webhook delivery with signing and retries, DKIM key management, and a UI a non-engineer can use during an incident.
Idempotency out of the box
A retried SendEmail call on a timeout sends twice. An Idempotency-Key header does not. This alone removes a class of bug most hand-rolled SES integrations still have.
You keep your AWS account
Point us at your existing verified identities and keep paying AWS directly for sending. We are the control plane, not a reseller in the middle.
Or pay us nothing
The core is open source. Self-host it and you are back to an AWS bill plus your own operations — which is exactly where you started, but with the control plane already written.
If you have already built event ingestion, suppression, and reputation tooling on top of SES and you are happy with it, keep it. If you are about to, talk to us first — or clone the repo.
We do not publish competitor pricing tables. Prices change, our table would go stale, and a stale number on a site arguing that claims should be checkable would be the worst possible own goal. Compare our pricing against Amazon SES's directly.
Think something on this page is unfair or out of date? Tell us — corrections get published.
Switching from Amazon SES?
The migration guide has the field map, the event map, and the checklist — including the suppression-list import everybody forgets.
Open core · never venture-backed · operated by Martin Business Consultants