Resend vs Amazon SES

Resend vs Amazon SES is really a question of whether you want to pay for convenience. SES is raw sending infrastructure at $0.10 per 1,000 emails, which makes it the cheapest mainstream option per email by a wide margin. Resend charges more ($20 for 50k, $35 for 100k on Pro) but gives you a modern API, React Email, a dashboard and managed suppression out of the box. Resend was, historically, built on top of SES.

All prices are as of October 2026, from third-party pricing trackers. Confirm on Resend's pricing page and the Amazon SES pricing page before deciding.

Resend vs Amazon SES at a glance

SES figures are simple arithmetic on the per-email rate and exclude dedicated IPs and any other AWS charges you may incur.

How much do Resend and SES cost at scale?

The gap is large and grows with volume. At 100k emails a month, SES costs about $10 against Resend's $35. At 500k, it is about $50 against $350. At 2.5M, about $250 against up to $1,150.

But the SES number is only the sending bill. With SES you also pay, in engineering time, for:

• Handling bounce and complaint notifications and keeping a suppression list.
• Building logs, search and dashboards to answer "did this email go out?"
• Managing IAM credentials, sending quotas and the sandbox exit.
• Responding if AWS reviews or pauses your account over complaint rates.

For a team that already lives in AWS, that work may be small. For a two-person startup, Resend's extra $25 a month at 100k is often cheaper than a day of building. Our post on transactional email cost at scale looks at how this changes as volume grows, and the email cost calculator lets you plug in your own numbers.

Free tier

Resend's free plan gives 3,000 emails a month with a 100/day cap. For SES, check AWS's pricing page for any current free allowance; it was not in our sources. Note that a new SES account starts in the sandbox regardless, so "free" doesn't mean "ready for production".

Account control and the SES sandbox

This is a real difference. New SES accounts start in a sandbox: you can only send to verified addresses until AWS grants production access. AWS then sets your sending quota and can pause sending if bounce or complaint rates rise. That protects AWS's IP reputation, and it is reasonable, but it means a third party decides when you can send.

Resend also has terms and will act on abuse, as any provider does. The difference is that Resend handles much of the hygiene (suppression, bounce handling) that keeps you out of trouble in the first place.

Dedicated IPs

SES publishes dedicated IP pricing: $24.95 per IP per month for standard dedicated IPs, or managed dedicated IPs at $15 per account per month plus a per-email fee. For Resend, check their pricing page. Whichever you choose, a new IP needs a warm-up period and consistent volume.

Inbound email

SES can receive email and hand it to other AWS services, though availability depends on region; check AWS's docs. For Resend's inbound support, check its documentation.

Developer experience

Resend is built for developers who want to ship quickly: a small API, React Email templates, a clean dashboard, and SMTP if you prefer it.

SES uses the AWS SDKs, IAM credentials and AWS's console. It is powerful and very reliable infrastructure, but it expects you to assemble the rest. If you already use Terraform or CDK and AWS everywhere, that may feel natural.

There is also a middle path: open-source projects such as useSend (formerly Unsend, AGPL-3.0, hosted from $10/month) and FreeResend (MIT, Resend-API compatible) add an interface on top of SES. See open-source Resend alternatives for a fuller list.

Moving between Resend and SES

Teams often start on Resend and consider SES once volume grows, or the other way round. The move is mostly mechanical: both support SMTP, so if your app already sends over SMTP you mainly change credentials. On the DNS side, add the new sender's DKIM records alongside the old ones, keep SPF as a single record, leave DMARC unchanged, and carry over your bounce and complaint list before sending.

The extra work when moving to SES is everything Resend did for you: processing bounce and complaint notifications, maintaining suppression, and getting out of the sandbox with a sending quota that fits your volume. Budget time for that before you switch.

Which should you choose?

Choose Resend if:

• You want to ship email features this week without building infrastructure.
• You use React Email or a TypeScript stack.
• Your volume is modest, so the per-email premium is small in dollars.
• You'd rather not deal with the SES sandbox and quota process.

Choose Amazon SES if:

• You send high volume and the per-email price dominates your bill.
• You already run on AWS and are comfortable with IAM and SNS-style notification handling.
• You have engineers who can build and maintain bounce handling and suppression.

Consider an open-source layer on SES if: you want SES pricing with a dashboard, and you are happy to run or pay for the layer.

A third option: your own server

SES and Resend both leave someone else in control of your sending account. A self-hosted mail server (Postfix on a VPS you control) removes that: your own IP, no per-email fees, no sandbox, and your mail data on your server. You do take on the things SES also leaves to you, plus server upkeep.

On cost, be realistic. SES is very cheap per email, so self-hosting rarely beats it on price alone. Compared with Resend, a managed self-hosted server (about $99/month plus a VPS, typically $5–20/month) is more expensive up to about 100k emails a month and tends to win roughly above 200k. Note that AWS blocks outbound port 25 by default, so a self-hosted server usually runs elsewhere, on a VPS provider that allows it.

Read self-hosted email vs Resend and our Amazon SES alternative page for more. If you want a server built or managed for you, see our pricing.