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. The cost difference is real, persistent, and gets larger as volume grows.
The question this post answers is not "which is cheaper" - Amazon SES wins that comparison at every volume tier - but "which is the right call for your specific situation." Cost isn't the only variable. Developer experience, vendor risk, AWS integration, deliverability operations, and team skills all matter. This post walks through the real tradeoffs with current pricing.
Amazon SES vs Resend 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). Resend's free tier is generous for prototypes; SES doesn't have a free tier in the same sense, but $0.10 per thousand is functionally free for anything under a few thousand sends.
The cost gap is consistent across every meaningful volume tier:
| Monthly volume | Amazon SES | Resend | SES vs Resend ratio |
|---|---|---|---|
| 3,000 emails | $0.30 | $0 (free tier) | Resend free |
| 10,000 emails | $1.00 | $20 (Pro 50k) | 20x |
| 50,000 emails | $5.00 | $20 (Pro 50k) | 4x |
| 100,000 emails | $10.00 | $35 (Pro 100k) | 3.5x |
| 500,000 emails | $50.00 | $350 (Scale 500k) | 7x |
| 1,000,000 emails | $100.00 | $650 (Scale 1M) | 6.5x |
| 2,500,000 emails | $250.00 | $1,150 (Scale 2.5M) | 4.6x |
The 4-7x cost premium 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), the SDKs are clean and modern (TypeScript, Python, Go, Ruby with native types), 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 written request to AWS Support with use-case justification, typically approved within 24 hours but sometimes 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.
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 and may pause sending at 10% (AWS, 2026). Your deliverability is your problem; AWS will tell you when it's broken but won't proactively manage it.
Resend operates a managed deliverability layer. New senders share Resend's IP pool by default, which provides good initial reputation from a known-good infrastructure. 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 require manual warmup (AWS, 2026). Resend offers dedicated IPs on higher Scale plans with managed warmup baked in. The cost difference matches the rest of the pricing pattern: SES is cheaper, Resend is managed.
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. Build with this in mind: starting on the cheaper, less proprietary infrastructure costs less to leave if you change your mind.
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.
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. Splitting on use case lets each service do what it's best at.
If you want SES economics without the AWS console pain - the question that pulls many developers toward Resend in the first place - a hosted SES management layer (Mailblast, Sendy, or similar) gives you SES pricing with a UI built for non-AWS workflows. See our overview of Amazon SES pricing for the underlying numbers, or our SES platform review for the platform-level take.
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?
Resend operates its own sending infrastructure and does not run as a thin wrapper over Amazon SES. The two services are distinct providers with their own MTAs, IP pools, and deliverability reputations. The choice between them is a choice between two independent email infrastructure providers, not between SES and a different UI on top of it.
Which has better developer experience: Amazon SES or Resend?
Resend is purpose-built for developer experience: clean REST API, React Email templating, modern SDKs in TypeScript and Python, a clean dashboard with per-message debugging, and onboarding designed to be productive in 15 minutes. Amazon SES is a general-purpose AWS service with the IAM and tooling that comes with that. For pure DX and time to first sent email, Resend wins decisively. For integration with existing AWS infrastructure, SES wins.
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 is more important than cost: prototypes, side projects, transactional email for sub-100,000-per-month volumes, teams without AWS experience, or projects that need the React Email template tooling. Resend's value is the time saved building and debugging email infrastructure, which can easily justify the price premium for small-to-medium volumes.
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. This comparison reflects the published pricing and feature set of both services as of June 2026.