SendGrid and Mailgun won a generation of “just add email” defaults. They’re still fine if you already live in their ecosystems. They’re the wrong shape when you only needed:
- Password resets
- Verify / magic-link emails
- Receipts
…and somehow inherited a marketing cloud, confusing tiers, and a dashboard that feels like airport security.
This is a transactional-only shortlist. Side-by-sides: Notify vs SendGrid · Notify vs Mailgun.
Why people leave
| Pain | What they wanted |
|---|---|
| Feature sprawl | A send API |
| Tier confusion | Flat, explainable pricing |
| Marketing gravity | Transactional reputation isolation |
| Onboarding weight | Minutes to first email |
| Free tier churn | A permanent starter allowance |
If you need campaigns, contacts, and a drag-and-drop studio, stay (or pick Brevo-class tools). This article is the other fork.
Shortlist
1. Notify — simplest paid step-up
Best for: Indies and startups who want send + logs + webhooks without a suite.
Pricing: Free 1,000/mo · Pro $10 / 10,000 · Scale $50 / 100,000. Full table: notify.cx/pricing.
API: POST https://notify.cx/api/email/send with x-api-key and message (HTML or text).
await fetch('https://notify.cx/api/email/send', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'x-api-key': process.env.NOTIFY_API_KEY
},
body: JSON.stringify({
from: 'noreply@your-verified-domain.com',
to: 'user@example.com',
subject: 'Reset your password',
message: '<p><a href="https://app.example.com/reset?token=…">Reset</a></p>'
})
});
Choose Notify if you already own HTML and want flat Pro pricing.
Skip if you need SendGrid’s marketing product or Postmark’s deliverability premium brand.
Compare / migrate: vs SendGrid · vs Mailgun · Migrate from SendGrid · Migrate from Mailgun
2. Resend — modern DX alternative
Best for: Teams leaving SendGrid for a cleaner developer experience and React Email workflows.
Tradeoff: Broader surface than Notify; paid tiers typically sit above Notify’s $10 Pro at early volume for similar monthly caps.
Choose Resend if ecosystem/docs defaults matter more than minimal API + price.
Compare: Notify vs Resend
3. Postmark — transactional specialist
Best for: Escaping SendGrid because deliverability and message streams matter more than price.
Tradeoff: Premium cost; thin free tier for active building.
Choose Postmark if a missed OTP is expensive. Don’t choose it to “save money” vs SendGrid Essentials. Compare: Notify vs Postmark.
4. Amazon SES — infrastructure alternative
Best for: High volume + AWS comfort after you’ve left the sandbox.
Tradeoff: You assemble dashboards, bounce handling, and webhooks. Production access waits are real.
Choose SES if unit cost dominates and you have ops. Otherwise use a thin managed layer first: Notify vs SES.
5. Stay on SendGrid / Mailgun (honest option)
Choose stay if:
- Migration cost > 12 months of fee delta
- You actually use marketing + transactional in one bill
- Critical integrations only exist there
Leaving for vibes is expensive. Leaving for a smaller job is rational.
Migration checklist (2-hour framing)
- Create account + API key on the new provider
- Verify domain (SPF/DKIM) — often the longest step
- Swap endpoint + auth header; map
html/text→ provider fields (messageon Notify) - Point webhooks; keep old provider draining a week
- Replay reset + receipt flows in sandbox, then production
- Watch bounce rates before deleting the old account
Step-by-step for Notify: Migrate from SendGrid · Migrate from Mailgun · Quick start
Decision table
| Job | Pick |
|---|---|
| Smallest API + $10 Pro | Notify |
| Modern DX / React Email culture | Resend |
| Deliverability premium | Postmark |
| AWS scale economics | SES |
| Need marketing suite still | SendGrid / Mailgun / Brevo |
Bottom line
Lightweight alternatives exist because transactional email is a small job. Notify, Resend, Postmark, and SES each win a different axis. SendGrid and Mailgun remain reasonable defaults only when you need their sprawl — or when migration costs more than peace of mind.
Resources
Further Reading
Discover more articles on similar topics across our network
Comments
Loading comments…