Amazon SES Alternative: AWS SES Alternatives and Competitors

There is no single best Amazon SES alternative, because the reason people leave SES is rarely price. For transactional email under 10,000 messages a month, Mailgun and Postmark both start at $15 and include the dashboard and logs SES makes you build. For developer experience, Resend at $20 covers 50,000. For cold outreach, no relay is the right answer and a sending application on your own mailboxes is.

That is the short version. The longer version is that SES is priced so far below everything else that a straight cost comparison is not really a comparison. At $0.10 per thousand a la carte, SES is roughly 15 times cheaper than Mailgun at 10,000 emails a month and 150 times cheaper at 1,000 emails a month. If your only complaint about SES is the invoice, you are almost certainly better off staying and fixing something else.

What people actually leave over is the sandbox, the review thresholds, and the fact that SES ships no application. Those are the three problems worth choosing an alternative for, and they point at three different products.

SES sells the same emails four different ways: a la carte, and then three plans. AWS publishes a per-1,000 rate for each plan at each of three volume tiers, and adds a fixed monthly fee on the two upper plans. Every figure below came off aws.amazon.com/ses/pricing on 2 September 2026.

The volume tiers step down as you send more. Essentials runs $0.16 up to 10M, $0.14 from 10M to 100M and $0.11 above 100M. Pro runs $0.22, $0.17 and $0.12. Enterprise runs $0.23, $0.18 and $0.13. AWS notes that these rates are applied marginally, so each rate applies only to the emails inside that tier rather than to your whole volume.

One detail the plan table hides: the fixed fees are per account per Region. Teams that send from two AWS Regions for redundancy pay $105 or $500 twice, and the sandbox is tracked per Region as well, so production access granted in us-east-1 does nothing for eu-west-1.

On Amazon SES, climbing the plan ladder makes every email more expensive, not less. Pro costs $0.22 per thousand against Essentials at $0.16, a 37.5% higher unit rate, and adds $105 a month on top. Enterprise costs $0.23 and adds $500. There is no volume at which Pro is cheaper than Essentials for the same emails.

That is unusual enough to be worth stating plainly, because most price lists reward volume with a lower unit rate. On SES the volume discount comes from the volume tiers, and the plan tiers work in the opposite direction. You buy Pro for features, never for price.

Which features? Pro bundles managed dedicated IPs, email validation and the global side of the Virtual Deliverability Manager. Here is the part nobody prints: AWS's own footnote says Essentials customers pay $1,250 per month for that global deliverability feature, while Pro includes it in the $105. If you need it, Pro saves you $1,145 a month. If you do not, Pro is a $105 tax plus a worse rate.

AWS publishes exact thresholds, and the complaint one is tighter than most senders realise. Its enforcement FAQ says to maintain a complaint rate below 0.1%, and that at 0.1% or greater it will place your account under review. The recommended ceiling and the review trigger are the same number.

Do the arithmetic for outbound. At 10,000 emails a month, ten spam-button clicks is 0.1%. At 2,000 a month it is two. Cold prospecting to a list that is even slightly off-target crosses that line inside a single campaign, and the bounce threshold is easy to hit too if your data is stale.

AWS is also explicit that a review is not guaranteed first. Its FAQ states that in some situations it might pause sending without placing the account under review, for example if the issue is very serious or if the account has been under review for the same issue before. There is no appeal queue with a service level attached; you reply to the support case AWS opens on your behalf and wait.

This is the single best reason to look for an alternative, and it is also the reason a different relay will not save you. Every provider on this page watches complaints. What changes the outcome is sending from mailboxes and domains you control, so a bad segment damages one domain rather than your entire sending account.

Every new SES account starts in the sandbox, and the sandbox status is unique per Region. The AWS developer guide lists the restrictions directly: you can only send to verified email addresses and domains or to the SES mailbox simulator, a maximum of 200 messages per 24-hour period, and a maximum of 1 message per second. Account-level suppression list management via the API is disabled too.

Getting out is a production access request through the SES console, which AWS reviews. Verifying your sending domain before you ask is the documented way to get approved faster. There is no published turnaround time, and if you are sending from an EC2 instance AWS notes you may separately need the throttle removed from port 25.

None of this is unreasonable for a service that carries other people's mail on shared IPs. It is simply the opposite of what a team with a deadline wants. Postmark, Resend and Mailgun all let you send real mail on the day you sign up, at a price that buys back the week you would otherwise spend in a support case.

Here is what the same month costs on four providers. SES is shown a la carte, which is its cheapest configuration. Mailgun, SendGrid and Postmark are shown at the smallest published plan that covers the volume in the row, so a low-volume sender is paying for headroom they will not use.

The gap is not close at any row. At 10,000 emails a month SES a la carte costs $1.00 against Mailgun's $15 and Postmark's $15, a 15 times difference. At 1,000 emails a month it is 150 times. The honest reading is that the $14 or $19 you pay elsewhere is not really buying delivery, it is buying the dashboard, the retained logs, the support inbox and the absence of a sandbox ticket.

Note also that SendGrid's floor is 50,000 emails. A project sending 1,000 a month still pays $19.95, an effective $19.95 per thousand. Plan floors distort small-volume comparisons far more than unit rates do.

The per-thousand rate is the beginning of an SES invoice, not the end. These are the a la carte add-on prices published on the same page, and they apply on top of whatever plan you are on.

The endpoint line deserves a sentence of its own. AWS states that charges apply even when the endpoint status is Closed, and that you have to delete the endpoint to stop them. That is $50 a month for a thing you thought you had turned off, and it is the sort of detail that only shows up on an invoice.

The bring-your-own-IP floor is worth flagging too. The published minimum is 256 addresses, which AWS itself works out as $24.95 x 256 = $6,387.20 per month. BYOIP is not a small-team option.

If what you liked about SES was the API and what you disliked was everything around it, three products cover that shape.

Mailgun starts at $15 a month with 10,000 emails included and overage at $1.80 per thousand. It adds inbound routing, email validation and webhooks. Two things to know before you commit: log retention on Basic is one day, and additional dedicated IPs are $59 per month each. Mailgun's own documentation puts it bluntly, there is no send button in Mailgun. It is a wire, not an application.

Postmark starts at $15 for 10,000 and is the least surprising invoice in the set: Pro is exactly 1.10 times Basic and Platform exactly 1.20 times Basic at every one of its six volume steps. It is transactional-first and unapologetic about it. A dedicated IP costs $50 a month and requires the Pro plan plus 300,000 emails a month.

Resend starts at $20 for 50,000 with a free tier of 3,000 capped at 100 a day. It is the friendliest SDK of the three if you are in React or Next.js. Its API rate limit is 10 requests per second per team, which is a real constraint for burst sending, and additional sending domains are an add-on at $20 per month per 100.

All three are relays. None of them changes the consent question, and all three write it into their terms.

The other half of the search traffic for this term is not looking for a cheaper API. It is looking for something SES was never going to be: software with a screen.

For marketing email, Brevo starts at $9 a month and Mailchimp at $13 for 500 contacts. Both give you a campaign builder, lists, segmentation and automation. Watch the billing model. Mailchimp bills on your peak contact total and counts unsubscribed and non-subscribed contacts as billable, and a contact stored in two audiences is billed twice. Your invoice can rise in a month when you sent nothing at all.

For cold outbound, the answer is a different category again. You want sequences with reply detection, per-prospect personalization, warm-up and rotation across several mailboxes, and you want the sending to happen through Google Workspace or Microsoft 365 accounts you own rather than through anyone's shared pool. That is what ColdMailer does, from $29 a month, with no per-inbox seat fee.

The distinction matters more than the price. On a relay, your reputation is entangled with other customers on the same IP range and with the relay's tolerance for your complaint rate. On your own mailboxes, the only relationship that matters is the one between your domain and the receiving provider, and you can retire a burned domain without losing the account.

Technically yes, practically it is the wrong tool, and the numbers explain why better than any policy argument. SES will accept and deliver cold email. The problem is that AWS measures you on complaint rate, its review threshold is 0.1%, and cold outbound generates complaints at rates well above that even when the targeting is good.

The second problem is that SES gives you nothing that makes cold email work. There is no sequence engine, so every follow-up is code you write. There is no reply detection, so you will keep emailing people who already answered. There is no rotation across mailboxes, so all your volume lands on one sending identity. There is no warm-up, so a new domain goes from zero to full volume on day one, which is the fastest way to build a spam-folder reputation.

Teams do build all of this on top of SES. It takes weeks, and the thing they end up with is a worse version of software that costs $29 a month. The cost saving is real but small in absolute terms: 5,000 cold emails a month is $0.50 on SES a la carte against $0.80 on Essentials. Nobody's outbound programme is limited by 50 cents.

If you want the detail on which providers permit prospecting and which do not, our comparison of SMTP providers for cold email works through each one's terms.

Search for SES pricing and you will get four different numbers from four different articles. All four were true at some point. Here is what changed.

They quote the retired free tier. For years SES included 62,000 free emails a month when sent from an EC2 instance. That tier is gone, and articles that still mention it are describing a service that no longer exists.

They quote $0.10 without the plan default. Since 21 July 2026, new accounts and account and Region combinations with no metered SES activity since 1 June 2025 start on Essentials, at $0.16. You can switch to a la carte at any time, but $0.10 is no longer where you land by default.

They omit the fixed fees, and the word Region. Pro's $105 and Enterprise's $500 are per account per Region per month. An article quoting Pro as $105 for a multi-Region deployment is understating it by a multiple.

They rank send-billed and contact-billed products in one list. Putting Mailchimp's $13 next to Mailgun's $15 next to SES's $0.10 is not a comparison, because those three numbers measure three different things: contacts stored, emails included, and emails sent. The roundup format hides that.

For the record, we deliberately did not reprint SES's star rating or review count from any review site. Those numbers move, we cannot verify how they were collected, and they tell you nothing about what you will pay.

A migration is the moment your sending reputation is most exposed, because you are asking receiving providers to trust a new path overnight. Four things keep it boring.

Move the volume, not the domain, first. Keep your existing authenticated domain and add the new provider's DKIM record alongside the old one. Both can be valid at once. Verify the new path with a small share of real traffic before you cut over.

Ramp rather than switch. Send 10% of your volume through the new provider for a few days, then 25%, then half. Receiving providers score the sending path, and a path with no history that suddenly carries your full volume looks exactly like an account takeover.

Carry your suppression list across. SES holds an account-level suppression list of addresses that bounced or complained. If you leave it behind, you will re-mail every one of those addresses on day one at the new provider and reproduce the bounce rate that caused the problem in the first place. Export it before you disable the account.

Keep SES alive for a month. Do not delete the identity the day you migrate. Leave it configured so you can fall back, and so any in-flight webhooks and bounce notifications still have somewhere to land. At $0.10 per thousand, an idle SES account costs nothing.

If your reason for leaving was deliverability rather than product fit, fix the authentication first. Our guide to SPF, DKIM and DMARC for cold email covers the records every provider will check, and mailbox warm-up covers the ramp itself.