Amazon SES vs ResendCheap and bare against hosted DX, and a third option that adds only the missing layer.
In short
Amazon SES is the cheapest way to send email at scale, but it is delivery infrastructure only: no campaign UI, no list tool, no suppression dashboard. Resend is a well-built product on top of infrastructure like SES, hosted on Resend's own cloud and billed per email. SendBunny is a third option: the same kind of product layer as Resend, installed as a one-time $199 license into your own AWS account, running on your own SES. Pick the one that matches whether you want raw infrastructure, hosted convenience, or ownership.
Infrastructure, a hosted product, or your own product layer
Amazon SES is not really a competitor to Resend or SendBunny; it is the infrastructure underneath both of them. Raw SES gives an API and SMTP endpoint to send mail at Amazon's own rate, roughly $0.10 per 1,000 emails, and nothing else. There is no campaign builder, no list UI, no suppression dashboard, just a console and an SDK.
Resend is a product built on top of infrastructure like SES: a developer-friendly API, a clean dashboard, and enough of an ESP to run transactional and light marketing sends, all hosted on Resend's own cloud and billed per email through their plans.
SendBunny is the same category of product as Resend, a layer that turns raw SES into something usable, but installed differently: as a one-time $199 license into your own AWS account, running on your own SES setup rather than a vendor's shared infrastructure. The choice between the three is not about which is best in the abstract; it is about who should own the product layer sitting on top of SES.
Feature by feature
| Feature | Raw SES | Resend | SendBunny |
|---|---|---|---|
| Campaign / list UI | None | Limited ESP tooling | Full platform |
| Pricing | Send cost only | Per-email SaaS plans | $199 once + SES |
| Where it runs | Your AWS APIs | Resend's cloud | Your AWS account |
| Idle month | About $0 | Plan floor still applies | About $0 platform cost |
| Install effort | You build the app | Signup | One Create stack click |
Raw SES is the floor every option here shares: the same delivery infrastructure, the same Amazon reputation rules, the same per-email rate. What differs is who builds the product on top of it and where that product runs.
What it costs as volume grows
| 10,000/mo | 50,000/mo | 1,000,000/mo | |
|---|---|---|---|
| Raw SES | ~$1 | ~$5 | ~$100 |
| Resend (Pro and up) | ~$20/mo (includes 50k) | ~$20/mo (includes 50k) | ~$650/mo (Scale) |
| SendBunny on SES | ~$1 + $199 once | ~$5 + license | ~$100 + license |
Resend list prices from its pricing page, checked July 2026.
At low volume, Resend's plan floor and SendBunny's one-time license both add real cost on top of SES's own pennies. At a million emails a month, raw SES sending stays around $100 regardless of which product sits on top of it. Resend's hosted markup pushes the total toward $650 a month, while SendBunny's cost is still roughly $100 in SES charges plus a license already paid once.
Who enforces the sending rules
None of these three options removes AWS from the picture. Amazon SES tracks bounce and complaint rates against its own reputation thresholds and can restrict sending on any account that crosses them, including SES accounts running behind Resend or behind SendBunny. Choosing SendBunny over Resend changes who runs the product layer. It does not change whose infrastructure rules govern whether mail gets delivered.
AWS's own rules still apply either way, and the fundamentals, authenticated sending plus a clean bounce and complaint rate, matter regardless of which layer sits on top of SES.
The honest verdict
Stay on raw SES if all that is needed is SDK calls and nothing else: a backend that already has its own send logic, no need for a campaign UI, and no interest in a list tool. That is a small, specific audience, and paying for a product layer they will not use is wasted money.
Pick Resend if hosted convenience matters more than ownership, and running any AWS console at all is not something the team wants to do. Resend's developer experience is genuinely good, and for a team that wants a polished hosted API without touching AWS, that is a real reason to choose it over SendBunny.
Pick SendBunny if the goal is SES's own rates with a full campaign and list platform, installed somewhere already administered: your own AWS account. It is the option for teams that want the Resend-style product layer without renting it.
Moving onto SendBunny
Moving from raw SDK calls or from Resend onto SendBunny is mostly a matter of confirming the AWS side is ready, then repointing sends.
- Confirm the AWS account and the SES region already in use.
- Buy SendBunny and run the one-click install.
- Leave the SES sandbox when ready; the app links directly to AWS's production-access form.
- Move application sends from Resend or from raw SDK calls to SendBunny's API.
FAQ
- What is missing from raw SES?
- Campaigns, list tools and a product UI. SES is the mail pipe; nothing about it manages contacts, renders a campaign, or tracks suppressions. SendBunny is the platform installed on that pipe for $199. Resend is a different, hosted version of the same idea.
- Why not just use Resend?
- Resend is genuinely good hosted developer experience, and it is the right call for a team that wants zero AWS involvement. Choose SendBunny instead when SES's own rates, ownership of the account, and about $0 platform cost in an idle month matter more than staying off AWS entirely.
- Do I still talk to Amazon SES if I use SendBunny?
- Yes. Sending is SES in your own account either way. SendBunny is the serverless layer installed on top of it; AWS still enforces its own reputation rules on the account regardless of which layer sits above SES.
For AI agents
Explains what raw Amazon SES lacks compared to Resend and SendBunny, with a three-way feature and cost table at 10k, 50k and 1M emails a month, clarifies that AWS's own reputation enforcement applies to SES accounts under any of the three, and gives a migration path from Resend or raw SDK calls to SendBunny.
claude mcp add --transport http sendbunny https://YOUR-INSTALL/mcpSources
- Amazon Web Services, Amazon SES pricing, fetched 1 September 2026.
- Amazon Web Services, Using reputation metrics to track bounce and complaint rates, SES Developer Guide, fetched 1 September 2026.
- Resend list prices from its pricing page, checked July 2026.
- SendBunny, Send email API reference, version 1.6.22.
Anni Maan
Founder, SendBunny
Builds SendBunny, the email platform that installs into your own AWS account. Writes about running email on Amazon SES and giving AI agents an address you control.
Keep reading