I automated the hardest parts of Amazon SES, so you can send from your own AWS account in two minute

Wed, 28 Oct 2026 06:00:57 +0000

Amazon SES is the most cost-effective way to send transactional email. But a production setup
takes real work: IAM, the sandbox, bounce and complaint handling, logs, and watching your
reputation. I built SendFleet to do that work inside your own AWS account.

What it does

One-click connection. A CloudFormation template creates a scoped IAM role. Paste its ARN and
you are connected. No AWS keys are ever shared.
Finds your sending region. Production access is per region, so SendFleet checks them all and
picks the one that can send. If none can, it requests production access for you.
Tracking and webhooks. It sets up the configuration set and SNS topic in your account, keeps
them healthy, and turns events into an email log and signed webhooks.
Reputation protection. It pauses sending before your bounce or complaint rate reaches the
levels where AWS starts reviewing accounts.
Cost controls. You choose which SES events your account publishes, and set a monthly cap.
Transparency. Every change SendFleet makes in your account is listed in the dashboard.

How it is built

A Rust API for sending (POST /v1/send).
A Django dashboard.
Python Lambdas in a separate AWS account: a relay that assumes your role to send, a control
plane for setup and self-healing, and an event worker.
Postgres on Neon. Message bodies never reach the database.

Pricing

Free for 3,000 emails a month. $5 a month with 20,000 emails included, then $0.10 per 1,000. You
pay AWS for SES directly.

Try it at https://sendfleet.net. I'm keen to hear what would make you trust a tool like this with
your AWS account.

Coder Legion - Recent posts tagged byoc

I automated the hardest parts of Amazon SES, so you can send from your own AWS account in two minute

What it does

How it is built

Pricing