// the take
MillionSend is a self-hostable transactional email platform with a Resend-compatible API, built for teams who like Resend's developer experience but want an exit from vendor lock-in — you point it at your own AWS SES account, or use their hosted version instead. It's aimed at people already on AWS who want API-level portability as a hedge, not at anyone who just wants the easiest possible 'send an email' setup.
The Resend compatibility isn't just a tagline: there's a dedicated migration CLI (`@millionsend/cli migrate --from resend`) that pulls contacts, segments, templates, webhooks, domains and suppressions, and it's read-only against Resend so you can dry-run it before cutting over. Webhooks follow the actual Standard Webhooks spec (svix-* headers, bring-your-own whsec_ secret) instead of a bespoke signing scheme, so existing webhook tooling just works. Self-hosting goes further than handing you a docker-compose file — the setup wizard can provision the AWS side too (IAM user, SNS topic, SES configuration set), which is usually the part that eats a whole Saturday. There are separate *.contract.test.ts files per resource (emails, webhooks, domains, templates, etc.), which suggests they're actually testing the Resend-compatibility claim rather than just basic CRUD.
It's AGPL-3.0, so running it as a service for anyone outside your own org — even as an internal shared platform — likely triggers the network-use source disclosure clause, which is a real legal-review item for companies before they'll put email infrastructure on it. Receiving inbound mail is beta and requires running your own MX server, meaning you're now responsible for inbound SMTP exposure and deliverability, not just outbound sends — a different operational commitment than most people signing up for an 'email API' expect. The abuse/content monitoring is an external dependency (TypeSafe's Jev) that holds new-team and new-destination sends for about half a second on a third-party verdict; fine on their hosted cloud, but worth understanding before self-hosters flip on `ABUSE_JUDGE=typesafe` for compliance-sensitive mail. At 252 stars and self-hosting tied specifically to AWS SES, it hasn't had the kind of real-world deliverability battle-testing (bounce/complaint edge cases, SES quota handling under load) that older mail platforms have accumulated.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →