Email Bump vs Amazon SES
We send through Amazon SES. So this comparison isn't about the pipe — it's about whether you build the software above it or rent it.
Nine rows below, and the first is the one that matters: SES is roughly a fortieth of our price per email.
Which one you want, in three sentences
Pick Amazon SES if you have engineering time, high volume, and a need for a specific AWS region. At ten million emails a month the saving pays for someone to own it, and the control is real.
Pick Email Bump if you'd rather not build a dashboard, a suppression system and a bounce classifier — and if you also want campaigns, segments and flows rather than only a send call.
Pick something in between useSend or FreeResend: open source, self-hosted, sending through your own SES account. SES rates with an interface, and you run the container.
9 differences that matter
Amazon SES's column comes from their published pricing and documentation on 2 August 2026.
Three places Amazon SES is the better choice
Price, by a factor of forty. $0.16 per 1,000. There is no argument here and we're not going to construct one. If email is a commodity to you and you have the engineering time, SES wins on cost and it isn't close.
Regions, including the EU. Data residency is a config value in SES. We send from us-east-1 with no European option. For a GDPR-driven requirement, SES solves it and we don't.
Scale without a conversation. SES will take volumes no SaaS plan will sell you, at rates that keep dropping. Past a certain size you stop being a customer of a product and start being a customer of infrastructure, and that's the right place to be.
Email Bump vs Amazon SES, asked and answered
Is Email Bump more expensive than SES?
Per email, dramatically — SES is $0.16 per 1,000 and we don't sell email by the thousand at all. What you get for the difference is everything above the send call.
For a product with 25,000 contacts, we're $29/mo including campaigns, flows, segments, the API, SMTP and inbound. Building that on SES is a project, not a purchase.
Can I keep using SES for transactional and use you for marketing?
You can, and some people do. The cost is that your unsubscribe state, your contact records and your delivery logs live in two places, so answering "what did this person receive" means checking both.
Putting both on one plan is the reason our transactional API exists.
Do you have an EU region like SES does?
No. Sending is from us-east-1 only. SES has EU regions and so do AhaSend, Scaleway TEM and Mailgun.
If EU residency is a requirement, that's a genuine reason to stay on SES or move to one of those.
Import a segment and compare
5,000 contacts and 5,000 emails free. Run one campaign through both and let the delivery and click numbers decide.