Prompt
I don’t love Resend for our use case because I need more control over tenants and sender identities. What do people switch to?
Latest observation
If you need more control over tenants, sender identities, and routing, people usually move from Resend to one of these patterns:
1) SES + your own control layer
Most common choice if you want maximum flexibility.
- You manage:
- tenant-to-domain mapping
- sender verification rules
- per-tenant API keys or subaccounts logic
- routing, retries, bounce handling, suppression lists
- Amazon SES is cheap and reliable, but it’s fairly low-level.
- Best if you’re okay building the abstraction yourself.
Good for: SaaS apps with many tenants and custom branding.
2) Postmark
A lot of teams switch to Postmark when they want a cleaner developer experience than SES.
- Strong transactional email focus
- Good deliverability reputation
- Supports Message Streams, which can help separate traffic types
- Better UX than SES, less DIY
- Still not as flexible as “build your own over SES” for complex multi-tenant identity models
Good for: transactional email where deliverability and simplicity matter more than deep tenant customization.
3) Mailgun
Often chosen when teams need more operational control than Resend and want a mature API.
- Supports domains/sending identities well
- Has features that can fit multi-tenant setups
- More knobs than Resend
- Can get pricey/complex at scale
Good for: teams that want a flexible email platform without going fully raw on SES.
4) SendGrid
Still common, especially in larger orgs.
- Supports subusers, sender authentication, and lots of email infrastructure features
- Mature ecosystem
- Can be a bit enterprise-y and sometimes clunky
- Good if you need account structure and governance
Good for: larger SaaS teams or orgs needing admin controls and subaccounts.
5) SparkPost / Brevo / others
These come up less often, but depending on region, pricing, and feature needs, they can work.
- Brevo: often used for mixed marketing + transactional
- SparkPost: strong deliverability tooling, less top-of-mind today than it used to be
What people usually pick for multi-tenant sender control
If your main pain is:
- each tenant needs its own sender/domain
- you need clear isolation
- you want to control which identity is used per message
then the most common routes are:
Option A: SES + custom sender-management
Best if you want full control and are comfortable engineering it.
Option B: SendGrid or Mailgun with subaccounts/domains
Best if you want platform features to do some of the heavy lifting.
Option C: Postmark if the complexity is mostly UX, not infrastructure
Best if you just want a smoother transactional setup and your tenant model isn’t too exotic.
My blunt recommendation
- If sender identity routing is core to your product: go SES and build the abstraction.
- If you want less ops pain: try Mailgun or SendGrid.
- If you mainly want a nicer transactional email product: Postmark.
If you want, I can also give you a comparison specifically for multi-tenant SaaS with columns like:
- sender/domain management
- subaccounts
- API simplicity
- deliverability
- pricing
- best fit