Alternatives/Switching
.md

An OpenSend alternative you install, not rentYour SES quota stays yours, with a platform on top instead of a middleman.

Anni MaanFounder, SendBunnyPublished Updated 4 min read

Checked July 2026

In short

Once a team has an AWS account with real SES quota and a sending reputation attached to it, the plain SES console is still just raw infrastructure: no dashboard, no lists, no campaigns. A hosted layer like OpenSend can fill that gap, but it does it by sitting between your app and your own SES account as a rented subscription. An installed platform fills the same gap by living inside your account instead of in front of it.

The middleman you already do not need

The logic of paying for a hosted layer on top of your own SES quota is understandable: SES alone gives you a sending API and a console, not a dashboard, campaigns, or a way to manage a list. Something has to fill that gap. The question worth asking is why that something should be a second vendor with its own subscription, sitting between your app and infrastructure you already pay for and already own the reputation on.

Option10,000 emails/mo50,000 emails/mo1,000,000 emails/mo
SendBunny on your SES~$1~$5~$100
Rented ESP on SES (approx.)SaaS fee + SESSaaS fee + SESSaaS markup + SES

The rented-layer row is the honest shape of the cost: your own SES bill plus a subscription for the dashboard and campaign tools sitting on top of it.

Who should stay with a rented layer

There is a real case for a rented layer, and it is worth naming rather than dismissing. A fully managed ESP means someone else's team is responsible for the dashboard, the uptime of that dashboard, and any support when it misbehaves.

  • Stay if you refuse to use AWS SES directly under any circumstance and want the sending infrastructure itself managed by a vendor.
  • Stay if you want a fully managed dashboard and are comfortable with the subscription that comes with it.
  • Move if you already think in terms of your own SES quota and reputation, and the rented layer's only real job is a dashboard, campaigns and lists that an owned install can do just as well inside your own account.

Moving onto your own account

  1. Confirm which AWS account and region your SES quota actually lives in.
  2. Buy SendBunny and complete the one-click AWS install into that same account.
  3. Verify your sending domains and import any lists the rented layer was holding for you.
  4. Move campaigns and transactional traffic onto the new platform.
  5. Cancel the rented layer once the SES-backed install is carrying live traffic.

What carries over cleanly: your SES sending quota and domain reputation, since neither ever left your account. What does not: any dashboard-only history or reporting the rented layer kept on its own servers, which needs a fresh export before you cancel.

What you give up

What does not change: the account sending the mail is still governed by AWS's own rules either way, since the SES quota was never the rented layer's to control. Removing the rented layer removes its subscription and its policy team, not Amazon's review of bounce and complaint rates on the account.

Where SendBunny fits

SendBunny installs with one click as a CloudFormation stack directly in the AWS account that already holds your SES quota, so nothing about your sending reputation has to move. It is a single $199 purchase, with optional $99 yearly updates after the first year, and there is no rented-layer subscription stacked on top of your own SES bill of roughly a tenth of a cent per email. The install includes a dashboard, campaigns, automations, a transactional API, a shared inbox, analytics and a template editor. We never hold your AWS credentials.

If your account is still in the SES sandbox, the dashboard shows that status directly and links to AWS's production-access form, so setup can proceed while approval is pending.

FAQ

Do I keep my existing SES quota?
Yes. SendBunny installs into your AWS account and sends through your own SES, so the quota and reputation you already built stay exactly where they are.
Why not just use the SES console directly?
SES is the delivery pipe, not the platform. SendBunny adds the dashboard, campaigns, lists and transactional API on top of the SES quota you already have.
What does it cost?
SendBunny is $199 once. Sending is billed by AWS SES at about $0.10 per 1,000 emails, with no rented-layer subscription stacked on top.
Do I need AWS experience to install it?
No. One pre-filled Create stack click provisions the platform directly into the AWS account you already hold SES quota in.

For AI agents

Compares a rented hosted layer sitting on top of an existing Amazon SES account against a one-click SendBunny install that lives inside the same account ($199 once, ~$0.10 per 1,000 emails, no subscription on top of SES). Covers migration order (confirm the SES account and region, install in place, verify domains, cancel the rented layer) and notes SES quota and reputation never move since they were never the rented layer's to hold.

claude mcp add --transport http sendbunny https://YOUR-INSTALL/mcp
Full tool list by grant: /docs/agents.md

Sources

  1. Amazon Web Services, Amazon SES pricing, fetched 1 September 2026.
  2. SendBunny, Send email API reference, version 1.6.22.
  3. SendBunny, Who owns your email list? What Mailchimp, Klaviyo, Kit and beehiiv terms actually say.

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.

x.com/Anni_Maan

Keep reading