Resend charges $20 per month for 50,000 transactional emails (Resend, 2026). Amazon SES charges roughly $5 for the same volume at its published $0.10 per 1,000 rate (AWS, 2026). At 1 million emails per month, Resend's Scale tier is $650 versus Amazon SES at $100. Mailtrap matches Resend at $20 for 50,000 emails and charges $300 at 500,000 (Mailtrap, 2026). The cost difference is real, persistent, and gets larger as volume grows.
Resend itself sends through Amazon SES: its sending regions are AWS regions, and its own sending subdomain authorizes amazonses.com in SPF (Resend, 2026). So the premium buys a developer layer, not different infrastructure. Whether that layer is worth it depends on developer experience, vendor risk, AWS integration, deliverability operations, and team skills, not price alone.
Amazon SES vs Resend vs Mailtrap Pricing: Real Math at Every Volume Tier
Amazon SES costs $0.10 per 1,000 emails, with no monthly minimum (AWS, 2026). Resend's pricing is tiered: $0 for 3,000 emails per month (limited to 100 per day), then $20 per month for 50,000 emails, scaling up through several tiers to $1,150 per month for 2.5 million emails (Resend, 2026). Mailtrap's Email API is tiered the same way: 4,000 free emails per month (150 per day), then $15 for 10,000, $20 for 50,000, and up to $1,250 for 2.5 million (Mailtrap, 2026). SES has no free tier in the same sense, but $0.10 per thousand is functionally free for anything under a few thousand sends.
One SES change to check before you budget: since July 21, 2026, new SES accounts start on the Essentials plan at $0.16 per 1,000 emails, which bundles Virtual Deliverability Manager (AWS, 2026). AWS lets you switch to à la carte pricing at $0.10 per 1,000 at any time, and the SES figures below assume you have.
The cost gap is consistent across every meaningful volume tier:
| Monthly volume | Amazon SES | Resend | Mailtrap | SES vs Resend ratio |
|---|---|---|---|---|
| 3,000 emails | $0.30 | $0 (free tier) | $0 (free tier, up to 4,000) | Resend free |
| 10,000 emails | $1.00 | $20 (Pro 50k) | $15 (Basic 10k) | 20x |
| 50,000 emails | $5.00 | $20 (Pro 50k) | $20 (Basic 50k) | 4x |
| 100,000 emails | $10.00 | $35 (Pro 100k) | $30 (Basic 100k) | 3.5x |
| 500,000 emails | $50.00 | $350 (Scale 500k) | $300 (Business 500k) | 7x |
| 1,000,000 emails | $100.00 | $650 (Scale 1M) | $750 (Enterprise 1.5M) | 6.5x |
| 2,500,000 emails | $250.00 | $1,150 (Scale 2.5M) | $1,250 (Enterprise 2.5M) | 4.6x |
The 3.5-7x premium above 50,000 emails is consistent, not a quirk at one tier. For a SaaS sending 1 million transactional emails per month, switching from Resend to SES saves roughly $550 monthly, $6,600 annually. The same calculation in reverse: choosing Resend over SES at 1 million emails costs an extra $6,600 per year for the developer experience and platform features.
Developer Experience: Where Resend Wins Decisively
Resend was built developer-first. The API surface is small (one main endpoint: POST /emails), quickstarts cover nine languages (Node.js, Python, Go, Ruby, PHP, Java, .NET, Rust, and Elixir), the dashboard shows per-message status with delivery, bounce, complaint, and click events in real time, and the React Email companion library lets you write transactional templates as React components. From npm install to a sent test email, Resend can be working in 10 minutes.
Amazon SES is a general-purpose AWS service. The API is larger and lower-level - separate endpoints for verifying identities, managing suppression lists, configuration sets, event destinations, dedicated IPs, and a few different sending modes. The AWS SDKs are powerful but verbose, the SES console is functional but not delightful, and the per-message visibility lives across CloudWatch, SNS, and S3 rather than in a single pane of glass. From AWS-account-setup to first sent email, SES typically takes a couple of hours plus IAM policy debugging.
Three specific DX differences matter operationally:
- Debugging a delivery failure. Resend's dashboard shows the SMTP response, the bounce type, and the receiving server message inline. SES requires setting up SNS topics, subscribing to them, and parsing JSON event payloads to get the same information. A first-time SES integrator spends real time on this; Resend hands it over in the UI.
- Sandbox-to-production friction. Both services start in a sandbox mode that only sends to verified addresses. Resend's transition is a button in the dashboard. SES's transition is a production access request with a use-case description, which AWS typically answers within 24 hours but sometimes takes longer.
- Template management. Resend's React Email templates live in your codebase. SES templates live in a separate SES Templates resource managed via API, which is functional but feels like a different surface.
Mailtrap is an email API and SMTP relay for developer and product teams, and its setup overhead sits closer to Resend than to SES: no IAM policies, no SNS topics, and delivery events in the dashboard without extra wiring. It ships official SDKs for eight languages (Node.js, Python, Go, PHP, Ruby, Java, .NET, and Elixir), plus code snippets for frameworks including Laravel, Rails, Django, and Next.js. The difference from Resend shows up after the send. Mailtrap says it breaks delivery down by mailbox provider, domain, and sending stream, so you can see Gmail delivery drop while Outlook stays clean without building a separate monitoring layer.
For prototypes, side projects, and small-to-medium transactional volumes, Resend's DX premium pays for itself in saved developer hours. For high-volume production systems running other AWS services, SES is worth the slight DX cost because it integrates natively with the surrounding infrastructure.
Deliverability: Two Different Models
Both services are well-regarded on deliverability, but they manage reputation differently. Amazon SES gives each account its own sender reputation, calculated from your account-level hard bounce rate and complaint rate. AWS places accounts under review at a 5% hard bounce rate or a 0.1% complaint rate, and may pause sending at 10% or 0.5% (AWS, 2026). Our guide to fixing a high SES bounce rate covers what to do when you cross the first line. Your deliverability is your problem; AWS will tell you when it's broken but won't proactively manage it.
Resend runs a managed deliverability layer on top of SES. New senders share Resend's pool by default, which gives them an established reputation from day one. Resend monitors per-account behavior and enforces internal limits before any single bad sender damages the shared pool. For most senders this is a feature - good deliverability without operational work. For senders with unusual patterns or specific compliance needs, the shared-pool model can occasionally feel restrictive.
The dedicated IP question splits the same way. SES dedicated IPs cost $24.95 per month each and you manage the warmup (AWS, 2026). Resend sells dedicated IPs as a $30 per month add-on on Scale plans for senders above 3,000 emails per day, and only as managed pools: Resend handles warmup and scaling but doesn't expose the IP list (Resend, 2026). The cost difference matches the rest of the pricing pattern: SES is cheaper, Resend is managed.
Mailtrap takes a managed approach like Resend but puts more weight on visibility after the send. Transactional and bulk email go out through separate streams, so a bulk campaign can't drag down the reputation your password resets send from. Delivery analytics are split by mailbox provider, domain, and stream rather than a single account-level rate, which can surface a reputation problem before an aggregate bounce rate moves. Dedicated IPs come with the Business plan, from $85 per month at 100,000 emails, with automatic warmup instead of the manual warmup SES requires (Mailtrap, 2026).
Lock-in and Vendor Risk
Amazon SES sits inside AWS. The IAM model, the operational tooling, and the pricing curve are predictable in the way AWS services are. If AWS changes SES pricing it's likely to be a small annual adjustment, not a 2x jump. Resend is a venture-funded startup with strong recent growth. The product is excellent today, but the pricing structure has changed multiple times in the company's history and may change again. Vendor stability matters more for some teams than others.
The migration cost is asymmetric. Moving from Resend to SES means rewriting integration code (different SDK), redoing template management (Resend's React Email templates don't run natively in SES), and rebuilding deliverability monitoring. Moving from SES to Resend is somewhat easier because the API surface is smaller, but you still pay for the new pricing tier. Either way, the mail still leaves through SES; what changes is the API, the tooling, and who manages the account. Build with this in mind: starting on the cheaper, less proprietary infrastructure costs less to leave if you change your mind.
Mailtrap sits in the same hosted-service category as Resend: you rent deliverability rather than own it inside your AWS account. Leaving either one means rewriting the SDK integration and rebuilding whatever delivery monitoring you set up. For teams where infrastructure ownership and long-term pricing predictability matter most, SES remains the answer either way.
When to Choose Each
The decision usually comes down to volume and team. Under 50,000 emails per month with a developer-led product team, Resend's $20 Pro tier is cheap relative to engineering time and the DX premium pays for itself. Over 100,000 per month with AWS infrastructure already in place, Amazon SES at $0.10 per 1,000 (AWS, 2026) is hard to argue against. The cleanest rules:
Choose Amazon SES if you're sending over 100,000 emails per month, you're already inside AWS infrastructure (Lambda, EC2, RDS), you need fine-grained IAM policies and CloudTrail audit logs, you have or can hire AWS engineering skill, or you want predictable pricing for the long term.
Choose Resend if you're sending under 50,000 emails per month, you value developer experience over cost, you don't have AWS engineering capacity, you're building a prototype where speed matters more than the long-term cost curve, or you specifically want the React Email templating workflow.
Choose Mailtrap if you're a developer or product team sending both transactional and bulk email through one API and SMTP relay, and you want delivery analytics split by mailbox provider, domain, and stream rather than a per-message event log. Paid plans start at $15 per month for 10,000 emails, with a free tier of 4,000 emails per month (Mailtrap, 2026).
Use both is also valid for some teams: Resend for transactional (login emails, receipts, password resets where reliability and DX matter most) and Amazon SES for high-volume marketing campaigns where the per-thousand pricing dominates total cost. Resend now sells marketing email too, but priced by contact: $250 per month for 50,000 contacts (Resend, 2026), against about $50 for 500,000 emails on SES directly.
If you want SES economics for marketing email without the AWS console - the question that pulls many developers toward Resend in the first place - an SES management layer puts a campaign UI on your own SES account. Mailblast is hosted and runs $40 per month for 50,000 contacts plus AWS's SES fees; Sendy is self-hosted. See our overview of Amazon SES pricing for the underlying numbers, our SES platform review for the platform-level take, or Amazon SES vs Postmark and Amazon SES vs Mailgun for the other developer-first options.
FAQ
Is Resend cheaper than Amazon SES?
No. At 50,000 emails per month, Resend charges $20 while Amazon SES charges roughly $5 at $0.10 per 1,000 emails (Resend, 2026; AWS, 2026). At 1 million emails, Resend's Scale tier is $650 versus Amazon SES at $100. Resend's pricing premium pays for developer experience, dashboard tooling, and managed deliverability, not for cheaper sending.
Is Resend built on top of Amazon SES?
Yes, by the public evidence. Resend's sending regions use AWS region codes (us-east-1, eu-west-1, sa-east-1, ap-northeast-1), and the SPF record on its own sending subdomain authorizes amazonses.com (Resend, 2026). Choosing between them is choosing between SES directly and SES with Resend's API, dashboard, and deliverability management on top.
Which has better developer experience: Amazon SES or Resend?
Resend is built for developer experience: a small REST API, React Email templating, quickstarts for nine languages, and a dashboard with per-message debugging. Amazon SES is a general-purpose AWS service with the IAM and tooling that comes with that. Resend wins on time to first sent email; SES wins on integration with existing AWS infrastructure.
When should I use Amazon SES instead of Resend?
Choose Amazon SES when cost matters at scale (over 100,000 emails per month), when you're already inside AWS infrastructure (Lambda, EC2, EKS, RDS), when you need fine-grained IAM policies and CloudTrail audit logs, or when you want long-term independence from a single startup vendor's pricing changes. SES is the right answer for high-volume marketing campaigns where the $0.10 per 1,000 economics matter.
When should I use Resend instead of Amazon SES?
Choose Resend when developer experience matters more than cost: prototypes, side projects, transactional email under 100,000 per month, teams without AWS experience, or projects built on React Email. If you also send bulk email and want delivery analytics by mailbox provider, compare Mailtrap, which is priced in the same range as Resend at most tiers.
Disclosure: Mailblast is a hosted management layer for your own Amazon SES account. We have a vested interest in SES as a sending infrastructure but no commercial relationship with Resend. Mailtrap was added to this comparison as part of a link exchange with Mailtrap. All pricing reflects published rates as of October 2026.