Resend vs Amazon SES for Solo Developers

Amazon SES is the cheapest email sending service on the planet. Resend is one of the most pleasant to use. For solo developers, the question is whether saving a few dollars a month is worth the extra configuration and AWS complexity. This comparison breaks down exactly what you get with each.

Resend Overview

Resend is a developer-focused email API built for modern web applications. It provides a clean REST API, native React Email support for building templates with JSX, and SDKs for every major language. The focus is on making email sending as straightforward as possible.

Setup takes minutes. Verify your domain, grab your API key, and send your first email with a single API call. The dashboard shows delivery status, opens, and clicks without any additional configuration. Everything just works.

The free tier includes 3,000 emails per month with a 100-per-day cap and one verified domain. The Pro plan starts at $20/month for 50,000 emails, or $35/month for 100,000, with overage billed at $0.90 per 1,000. Pricing is predictable and easy to understand.

Amazon SES Overview

Amazon Simple Email Service is AWS's email sending platform. It is designed for high-volume transactional and marketing email at rock-bottom prices. SES handles sending, receiving, and managing email at any scale, from a few hundred to millions of emails per day.

The pricing is what draws most people in. SES charges $0.10 per 1,000 emails outbound, plus $0.12 per gigabyte of attachment data. The old free tier of 62,000 emails per month for EC2-hosted senders is gone, AWS discontinued it in August 2023. What remains is 3,000 free message charges per month for the first 12 months of a new SES account, and new AWS accounts created after July 15, 2025 get a pool of Free Tier credits instead. After that runway ends you pay the per-email rate from message one. Even so, at scale nothing else comes close on cost.

The tradeoff is the AWS experience. Setting up SES involves navigating the AWS console, requesting production access (you start in a sandbox that can only send to verified addresses), configuring IAM policies, setting up DKIM and SPF records, and potentially dealing with sending quotas. The initial setup can take hours if you are not already familiar with AWS.

SES also provides fewer guardrails. You are responsible for managing your sending reputation, handling bounces and complaints, and monitoring deliverability. AWS gives you the raw infrastructure but not the hand-holding.

Comparison Table

By the Numbers (2026)

The figures below were pulled from each vendor's own pages and from the public package registries on 2026-05-29.

A note on the star count comparison: the resend-node figure is for the dedicated Node SDK repo, while SES does not ship a standalone repo. Its client lives inside the AWS SDK for JavaScript v3 monorepo, so the 3,633 number reflects the entire SDK, not the SES client alone. Treat it as directional, not apples to apples. The download numbers are cleaner: the resend npm package out-pulls @aws-sdk/client-ses by more than two to one weekly, which tracks with how often greenfield projects reach for the simpler API.

Real Cost at Solo-Dev Scale

Numbers are easy to wave at. Here is the math on a single, concrete workload so you can see where the crossover actually sits. Assume a typical SaaS side project: signup confirmations, password resets, receipts, and a small weekly digest. Three volume points, computed from the real per-unit rates above (SES at $0.10 per 1,000, Resend Free, then Resend Pro at $20 for 50,000 with $0.90 per 1,000 overage).

Two honest caveats on those SES figures. First, they exclude the $0.12 per gigabyte attachment charge, which is zero for plain transactional mail and only bites if you send PDFs or images. Second, they assume you are past the first 12 months, so the free allowance no longer applies. Even with those caveats, the pattern is clear. At a few thousand emails a month both are effectively free. The moment you cross into tens of thousands, SES is dramatically cheaper on raw send cost.

The number SES does not bill you for is your time. Production access requests, IAM policy debugging, SNS bounce wiring, and CloudWatch dashboards are hours that do not show up in the table above. If your monthly send is under 50,000, the absolute saving is $15 or less, and most solo developers will spend more than $15 worth of their own time getting SES out of the sandbox.

When to Pick Resend

Resend is the better choice when developer experience and speed matter more than per-email cost:

• You want to be sending production emails in under 15 minutes.
• Clean API design and modern SDKs are important to your workflow.
• React Email templates appeal to you for building maintainable email designs.
• You do not want to deal with AWS IAM policies, sandbox restrictions, or CloudWatch for monitoring.
• Your email volume is moderate (under 50,000/month) and the pricing difference is negligible.
• You are not already invested in the AWS ecosystem.

For most solo developers sending a few thousand emails a month, both services land at or near $0, so the price difference is effectively nothing. The hours saved on setup and maintenance are worth far more.

When to Pick Amazon SES

Amazon SES makes sense when cost is the primary concern or you are already deep in the AWS ecosystem:

• You are sending high volumes (100K+ emails/month) and the cost savings are meaningful.
• You are already running on AWS and comfortable with IAM, SNS, and the AWS console.
• You need inbound email processing (SES can receive emails and trigger Lambda functions).
• You want maximum control over your email infrastructure and sending reputation.
• Dedicated IPs for sender reputation isolation are important to your use case.

SES is also the right choice if your project might scale to millions of emails. At that volume, the cost difference is substantial, and SES handles it without breaking a sweat.

Verdict

Resend wins for solo developers who value their time. The setup is faster, the API is cleaner, the dashboard is friendlier, and the developer experience is leagues ahead of SES. For typical solo developer volumes (hundreds to low thousands of emails per month), the cost difference is trivial.

Amazon SES wins on raw economics at scale. The math is not subtle. At 150,000 emails a month SES costs $15 against Resend's $80, and at a million it is $100 against $650. If you are sending six figures of email monthly and you are already comfortable with AWS, SES saves real money. But if you are a solo developer starting a new project and debating between the two, ask yourself honestly. At 50,000 emails a month the gap is $15, and below that both are free. Is saving $15 worth an afternoon fighting AWS IAM policies and sandbox restrictions? For most of us, the answer is no. Ship with Resend, and revisit the decision if your email volume ever makes SES pricing genuinely attractive.

Sources

• Resend pricing page (checked 2026-05-29): plan prices, 3,000/month and 100/day free limits, $20/50K and $35/100K Pro tiers, $0.90/1K overage, $30/month dedicated IP.
• Amazon SES pricing page (checked 2026-05-29): $0.10 per 1,000 outbound, $0.12/GB attachment data, inbound $0.10/1K plus $0.09 per 1,000 chunks, $24.95/month standard dedicated IP, $15/month managed, $0.07/1K Virtual Deliverability Manager.
• Amazon SES service quotas (AWS docs) (checked 2026-05-29): sandbox limits of 200 emails/24h and 1 email/sec, 50 recipients per message, 40 MB max message size via v2 API/SMTP.
• LowEndBox: Amazon dropping SES free tier (checked 2026-05-29): confirms the 62,000/month EC2 free tier was discontinued in August 2023, replaced by 3,000 message charges/month for the first 12 months.
• resend npm registry (checked 2026-05-29): latest version 6.12.4, published 2026-05-25.
• @aws-sdk/client-ses npm registry (checked 2026-05-29): latest version 3.1057.0, published 2026-05-29.
• npm downloads API, resend last week and last month (checked 2026-05-29): 6,681,192 weekly, 25,325,490 monthly.
• npm downloads API, @aws-sdk/client-ses last week and last month (checked 2026-05-29): 2,861,257 weekly, 12,550,903 monthly.
• resend/resend-node GitHub repo (checked 2026-05-29): 912 stars.
• aws/aws-sdk-js-v3 GitHub repo (checked 2026-05-29): 3,633 stars (the umbrella SDK monorepo that contains the SES client).