I kept building the same email infrastructure over and over - so I productized it
Every side project I've shipped needed transactional email.
Every time: same rabbit hole. Set up SES, handle bounces and complaints, build a queue, wire up webhooks, pray nothing breaks at 2am. Or pay a platform that stores your email content on their servers and charges more as you scale.
Neither felt right. So I built the thing I kept wishing existed.
SendFleet is a transactional email API with Bring-Your-Own-SES support. Connect your own AWS account, send through your own infrastructure, keep your sending reputation. Your email content never touches our database.
One clean API endpoint. Works for password resets, magic links, notifications, order confirmations — anything your app sends.
We also have a Shared SES path (Growth/Pro) for people who don't want to manage their own AWS account, with per-customer isolation so one bad sender doesn't affect your deliverability.
It's still early, still building — but it's live and working.
Free BYOC for the first year with code BYOC100 (expires August 15)
Would love feedback from this community specifically:
Does owning your sending reputation matter to you, or do you just want email to work?
What would actually make you switch away from Resend / Postmark / SendGrid?
Anything missing before you'd consider it production-ready?
