Should a SaaS use Resend or Amazon SES for transactional email?
It depends on volume and how much setup you will tolerate. Resend is the faster start: a free tier of 3,000 emails a month, one API key, and a verified domain. Amazon SES is cheaper per email, $0.10 to $0.16 per 1,000 against Resend's $0.90 overage rate, but new accounts start in a sandbox and need IAM credentials. Below roughly 50,000 emails a month the difference is a few dollars, so start with whichever ships today and keep the provider swappable.
The short answer
Start on Resend, move to Amazon SES when the invoice justifies an afternoon of AWS setup. Sign-in codes, receipts, and invites are low volume for most early products, and at low volume the price gap between the two is smaller than the cost of your time.
The numbers below were read from each vendor's public pricing page on November 15, 2026. Both pages change, so treat the figures as a dated snapshot and check the linked sources before you budget.
What each one costs at three volumes
Monthly cost for transactional email only, at the listed rates. SES figures exclude attachment data ($0.12 per GB) and optional add-ons.
How the Resend column is built: Free includes 3,000 emails a month with a 100 per day cap. Pro is $20 a month for 50,000 emails, and extra emails are $0.90 per 1,000. Scale is $90 a month for 100,000 emails. How the SES columns are built: the Basic plan is $0.16 per 1,000 emails for the first 10 million, and on-demand pricing is $0.10 per 1,000.
One detail worth noticing in the 100,000 row: at the listed rates, Pro with pay-as-you-go overage ($20 plus 50 times $0.90) comes to $65, which is less than Scale at $90. Scale buys more domains, a dedicated support channel, and dedicated IP eligibility, not cheaper email.
Per email, the gap is wide. Resend's overage rate is roughly six to nine times the SES rate. In dollars it stays small until volume grows: about $12 to $15 a month at 50,000 emails, and about $49 to $55 at 100,000. Sources: Resend pricing and Amazon SES pricing.
| Emails per month | Resend | SES Basic plan | SES on-demand |
|---|---|---|---|
| 3,000 | $0 on Free (100 per day cap) | $0.48 | $0.30 |
| 50,000 | $20 on Pro | $8.00 | $5.00 |
| 100,000 | $65 on Pro with overage, or $90 on Scale | $16.00 | $10.00 |
The 2026 SES change older comparisons miss
Many comparisons still quote a single SES price of $0.10 per 1,000 emails. That rate still exists, but it is now the on-demand option. Amazon SES pricing lists three plans, Basic, Pro, and Enterprise, and states that new SES accounts, plus account and region combinations with no metered SES activity since June 1, 2025, default to the Basic plan from July 21, 2026.
Basic costs $0.16 per 1,000 emails and bundles the SES deliverability features of Virtual Deliverability Manager, which on-demand pricing bills separately at $0.07 per 1,000. So Basic is the cheaper route if you want those insights, and on-demand is cheaper if you do not. AWS says you can switch between a plan and on-demand pricing at any time.
Pro adds a fixed $105 per account per region each month, and Enterprise adds $500. Neither makes sense for a product that sends sign-in codes and receipts.
Setup: minutes versus an approval step
Resend needs an account, DNS records for one sending domain, and one API key. Before the domain verifies you can send from onboarding@resend.dev, but only to the address you signed up with. The Resend setup guide walks through each screen.
Amazon SES needs a verified identity in a specific region and credentials from IAM. AWS places every new account in a sandbox, and documents that sandbox status is unique to each region. In the sandbox you can send only to verified addresses or the mailbox simulator, at most 200 messages per 24 hours and 1 message per second. You request production access to lift those limits.
Two SES details cost people time. The SMTP password AWS issues is not an IAM secret access key, so API credentials and SMTP credentials are not interchangeable. And the optional open ingress endpoint in Mail Manager is listed at $50 a month per endpoint, which plain sending does not need. The Amazon SES setup guide covers both.
| Resend | Amazon SES | |
|---|---|---|
| First email to a real customer | After the domain verifies | After the identity verifies and production access is granted |
| Starting limits | 100 emails a day on Free | 200 messages per 24 hours and 1 per second in the sandbox |
| Credentials | One API key | IAM access keys, or separate SMTP credentials |
| Dedicated IP | $30 a month add-on on Scale | $24.95 a month per standard dedicated IP |
When switching is worth it
Use the invoice, not the per-email rate. At 50,000 emails a month the move saves about $12 to $15. At 100,000 it saves about $49 to $55. Once the monthly saving is clearly more than the hours you will spend on IAM, the sandbox request, and a second round of DNS, switch.
Price does not settle deliverability. On either provider your domain reputation is yours: publish SPF, DKIM, and DMARC, send only mail people asked for, and watch bounces and complaints. A cheaper rate will not rescue a sender that recipients mark as spam.
- Stay on Resend while you are under the free tier or a few thousand emails above it.
- Plan the SES move when a paid Resend tier becomes a line you notice on the monthly bill.
- Do the sandbox exit early if you expect a launch spike, because it is an approval step you do not control.
Keep the provider behind one setting
The decision is cheap to reverse if the application never talks to a vendor directly. In supastack, templates and send calls go through one email boundary, and EMAIL_PROVIDER selects the transport: local, resend, ses, smtp, postmark, sendgrid, mailgun, or brevo. EMAIL_FROM keeps the same meaning for all of them.
The default is local, which writes every message to a preview page instead of sending it, so you can build sign-in and invite flows before choosing anyone. Moving from Resend to SES later is a change of environment variables on the server, with no template edits. The web, mobile, and desktop apps all send through the same backend, so no client ever holds a mail credential.
The email setup overview lists the variables for each transport.
Common questions about Resend and Amazon SES
- Is Amazon SES always cheaper than Resend?, Per email, yes at the listed rates. In total, not always: under 3,000 emails a month Resend's free tier costs nothing, while the SES rates above apply from the first email unless AWS credits cover them.
- Can I send through Amazon SES with SMTP instead of the AWS SDK?, Yes. SES issues SMTP credentials that are separate from IAM access keys, and they only work with the SMTP endpoint for the region where they were created.
- Does the SES sandbox apply to every region?, Yes. AWS documents sandbox status as unique to each region, so production access in one region does not carry over to another.
- Does Resend offer SMTP?, Yes. Resend lists an SMTP relay next to its REST API, so tools that only speak SMTP can still use it.
- Which one should a new SaaS start with?, Resend, in most cases. It reaches a real inbox with less setup, and its free tier covers early sign-in and receipt volume. Keep the provider behind one setting so the later move to SES is a configuration change.