Updated

Amazon SES vs Resend

Of the 2,461 makers' products we know the transactional email of, 1,080 chose Resend (44%) and 5 Amazon SES (0%); 1 uses both. Among the 343 launched in 2026, Amazon SES is in 0% and Resend in 82%, against 0% and 41% of those launched in 2024 or earlier. They're different kinds of tool, raw infrastructure and transactional API, so the counts don't measure the same choice. At our calculator's default usage, Amazon SES comes to $5.00 a month and Resend $20, at list prices. On GitHub, 16 public pull requests moved projects from Amazon SES to Resend, and 15 the other way.

Two sides of the transactional email decision: raw infrastructure and transactional API. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.

Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Which fits you

Choose Amazon SES if
  • You send at high volume and cost per email matters most

Use it whenYou already run on AWS, or your email volume makes per-message price the main cost.

Trade-offBare-bones; you build templates, bounce handling and tooling yourself.

Choose Resend if
  • You write React or TypeScript and want email templates as components in the same codebase

Use it whenYou're setting up sign-up and reset emails in a TypeScript app and want templates to live next to your UI code.

Trade-offA younger service than Postmark or SES, and costlier than SES at very high volume.

At a glance

Amazon SESResend
Used by5 makers' products · 38 open-source projects1080 makers' products · 58 open-source projects
Cost at default usageemails 50k emails$5.00/mo À la carte$20/mo Pro 50k
Moved to it on GitHubpull requests since Oct 202415 from Resend16 from Amazon SES
Downloads3.6M/wk−28% vs npm10.7M/wk3.9× vs npm
PricingPay per message; the cheapest option at high volume. · paid from $0.10 per 1k emailsFree tier for small volume; paid plans by monthly emails. · paid from $20/mo
Free tierNoYes
Open sourceNoNo

Which makers on your framework pick

Makers' products built with each framework that chose either one, for transactional email.

New launches vs older products

A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the transactional email decision (by the year they launched on Product Hunt).

LaunchedAmazon SESResendProducts
2022 or earlier0% 021% 30144
20231% 135% 2778
20240% 050% 176349
20250% 065% 225345
20260% 082% 282343

Cost as you grow

At 1k emails Resend costs less ($0 vs $0.10); from about 5k emails Amazon SES does ($0.50 vs $20). They're different kinds of tool — raw infrastructure and transactional API — so the prices don't buy the same thing.

$0$50$200$500$1,000$2,0001k5k10k25k50k100k250k500k1M5M
ResendAmazon SESx: emails per month (email) · cheapest usable plan at each point, list prices · try your own numbers
The numbers, plan by plan
Emails per monthAmazon SESResend
1,000$0.10 À la carte$0 Free
5,000$0.50 À la carte$20 Pro 50k
10,000$1.00 À la carte$20 Pro 50k
25,000$2.50 À la carte$20 Pro 50k
50,000$5.00 À la carte$20 Pro 50k
100,000$10 À la carte$35 Pro 100k
250,000$25 À la carte$170 Pro 100k
500,000$50 À la carte$350 Scale 500k
1,000,000$100 À la carte$650 Scale 1M
5,000,000$500 À la carte$2,300 Scale 2.5M

From each vendor's pricing page: Amazon SES, Resend.

Who moves from one to the other

Public pull requests on GitHub since Oct 2024 whose title says "Amazon SES to Resend" or the reverse — real code changes, by developers in general rather than makers only.

Resend → Amazon SES15 PRs
All matching pull requests on GitHub ↗
Amazon SES → Resend16 PRs
All matching pull requests on GitHub ↗

What makers say

Makers on using it for transactional email, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.

On Amazon SES

No maker quote about Amazon SES for transactional email yet.

On Resend
SendGrid and Mailgun still work but feel like 2015. Resend has the cleanest API and React-based email templates, so all my transactional mail took an afternoon instead of a sprint.
VC Boom, the makerSep 2026 ↗
Here’s what we use for marketing and operations: Stripe (payments) ConvertKit & Resend (email marketing) Plausible Analytics & Mixpanel (web and product analytics) Senja (testi…
FounderPal, the makerMar 2024 ↗
Configuring email is usually a headache. And when you just about get it right, it goes into recipients’ spam folder. Resend just takes the pain out of email and just works every time.
JotMe, the makerSep 2026 ↗
120 more on the Resend page →

Loved and watch-outs

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

Amazon SES
Most loved
  • Sending costs pennies per thousand emails, with a free monthly allowance through the API. HNHN 2HN 3HN 4
  • Relaying outgoing mail through it fixes deliverability for self-hosted mail servers. HNHN 2HN 3HN 4
  • It enforces anti-spam discipline, warning senders early when complaint rates spike. HNHN 2
Watch-outs
  • Getting out of the sandbox is hard, and requests can be rejected with no clear reason. HNHN 2
  • Shared IP reputation is outside your control, and a dedicated IP costs extra without guaranteeing delivery. HNHN 2HN 3HN 4
  • The console is clunky, and domain and DNS setup often needs hand-holding. HNHN 2
Resend
Most loved
  • The API is clean and TypeScript-first, simple enough to call with a plain fetch and no SDK. PHPH 2
  • Transactional email goes live within a day, with DNS setup and deliverability basics handled. PHPH 2
  • The free tier is generous enough to build and test before paying. PHPH 2HNHN 2
Watch-outs
  • It runs on AWS SES, so an AWS us-east-1 outage stopped both its dashboard and email sending. HNPH
  • API gaps remain, such as the broadcast API not returning email content and no stored copy of sent threads. HNHN 2
On Product Hunt: 4.9★, 260 reviews · mentioned most: easy setup, developer-friendly API, reliable delivery · complaints: slow performance

Who uses each

Used by both — often one replacing the other, or each for a different part of the product

What makers pair each with

With Amazon SES
With Resend
PostmarkTransactional APIDeliverability when the mail has to arrive within seconds.vs Amazon SES →vs Resend →
MailgunTransactional APIHigh volume and inbound email parsing and routing.vs Amazon SES →vs Resend →

Questions

Amazon SES or Resend: which do makers choose?

Of the 2,461 makers' products we know the transactional email of, 1,080 chose Resend (44%) and 5 Amazon SES (0%); 1 uses both. Among the 343 launched in 2026, Amazon SES is in 0% and Resend in 82%, against 0% and 41% of those launched in 2024 or earlier. They're different kinds of tool, raw infrastructure and transactional API, so the counts don't measure the same choice. At our calculator's default usage, Amazon SES comes to $5.00 a month and Resend $20, at list prices. On GitHub, 16 public pull requests moved projects from Amazon SES to Resend, and 15 the other way. Choose Amazon SES if you send at high volume and cost per email matters most; choose Resend if you write React or TypeScript and want email templates as components in the same codebase.

When should I pick Amazon SES over Resend?

Pick Amazon SES if: You send at high volume and cost per email matters most.

When should I pick Resend over Amazon SES?

Pick Resend if: You write React or TypeScript and want email templates as components in the same codebase.

Which is cheaper, Amazon SES or Resend?

At emails 50k emails: Amazon SES $5.00/mo (À la carte), Resend $20/mo (Pro 50k), at list prices.

How do Amazon SES and Resend compare in cost as you grow?

At 1k emails Resend costs less ($0 vs $0.10); from about 5k emails Amazon SES does ($0.50 vs $20). Cheapest usable plan at each scale, at list prices.

Are people switching from Amazon SES to Resend?

Public GitHub pull requests since 2024-10-02: 16 from Amazon SES to Resend, 15 from Resend to Amazon SES.