Disclosure up front: I work on MepMail, a transactional email API. Read the numbers below with that bias attached. They are not mine to invent — every price was read first-hand off each provider's own public pricing page on 2026-09-28, and I flag every row where the covering plan includes more volume than the volume being compared.
The question "what's a cheaper Resend alternative?" keeps coming up, and most answers are either affiliate listicles or a screenshot of a pricing page with no stated method. This is the boring version, with the method written down.
The real problem: email bills scale faster than the app that sends them
Threads like "Why is sending email more expensive than hosting?" (r/webdev, 90+ comments) or "Thought Resend's pricing was simple until my bill randomly shot up for no clear reason" (r/SaaS) aren't really about a few dollars. They're about the shape of the cost curve. Transactional email is priced as a step ladder, and each step is roughly 2–3x the one below it. A product that grows 10x in volume can grow its email line item by more than 10x, and the jump is invisible until the invoice lands.
Then there's "Is this a real problem or am I being cheap?" (r/nextjs, 60+ comments), where people do the same math and feel silly for caring. It isn't silly. At 100K emails/month the spread between the cheapest and the most expensive mainstream provider is already about $80/month. At 1M it's about $480/month. For a solo developer or a two-person SaaS, that is real money — and it's a line item that grows precisely when your product is working.
The comparison (same volumes, verified 2026-09-28)
Method: cheapest advertised monthly plan whose included quota covers the volume. Some providers don't have a tier that lands exactly on the volume, so the covering tier includes more than the column asks for. Those rows are flagged; you pay for the bigger tier.
100K emails/month
| Provider | Plan | USD/month | Included quota |
|---|---|---|---|
| MepMail | Pro 100K | $20 | 100K |
| SendGrid | Essentials 100k | $34.95 | 100K |
| Resend | Pro | $35 | 100K |
| Mailgun | Foundation | $75 | 100K |
| Postmark | Basic | $115 | 125K (tier covers more than 100K) |
500K emails/month
| Provider | Plan | USD/month | Included quota |
|---|---|---|---|
| MepMail | Scale 500K | $199 | 500K |
| Resend | Scale | $350 | 500K |
| Mailgun | Scale | $400 | 500K |
| Postmark | Basic | $455 | 700K (tier covers more than 500K) |
| SendGrid | Pro 700k | $499 | 700K (SendGrid has no 500K tier) |
1M emails/month
| Provider | Plan | USD/month | Included quota |
|---|---|---|---|
| MepMail | Scale 1M | $319 | 1M |
| Resend | Scale | $650 | 1M |
| Mailgun | Scale | $700 | 1M |
| Postmark | Basic | $775 | 1.5M (tier covers more than 1M) |
| SendGrid | Pro 1.5M | $799 | 1.5M (SendGrid has no 1M tier) |
At 100K/month, MepMail is $20 against $34.95–$115 — roughly 43% below the cheapest competitor (SendGrid) and 82.6% below the most expensive (Postmark). At 500K/month it's $199 against $350–$499, about 43% below Resend. At 1M/month it's $319 against $650–$799, about 51% below Resend.
All figures are USD, monthly billing, list price. None of the four established providers advertises an annual discount on the pricing pages I read. Overage rates differ per provider and sit outside these row prices. SendGrid and Postmark are stepped (SendGrid has no 500K/1M tier; Postmark's ladder jumps 125K → 700K → 1.5M), which is why their covering tiers buy more volume than the row.
Why MepMail is cheaper (the honest version)
Two structural reasons, and you should weigh both.
First, the sending infrastructure underneath is Amazon SES. MepMail is a transactional email API and SMTP relay built on SES. That is the same class of infrastructure a lot of providers build on; the difference is how much margin sits on top. MepMail is early and small and isn't paying for a large team or a large brand, so the markup is thin.
Second, the API accepts the official Resend SDK. If you're already on Resend, migration is typically a base-URL and API-key change rather than a rewrite. Keeping a small compatibility surface is cheaper to support, which is part of why the price is lower.
What that also means, plainly:
- API compatibility is not feature parity. The SDK accepts the Resend shape. It does not mean every Resend feature, dashboard convenience or edge-case behavior exists here yet.
- MepMail is early. Assisted onboarding (DKIM, MAIL FROM) exists because a small product should help you configure sending DNS correctly rather than let you guess. There is an official MCP server so tools like Claude, Cursor and Codex can send through it.
- On Amazon SES. Deliverability depends on your domain reputation, your list hygiene and SES itself — not on promises from me. No provider can guarantee inbox placement, and a vendor who claims otherwise is selling, not describing.
- No unlimited anything. There are quotas and caps, on purpose, and they're written down.
Who should NOT switch
This part is more useful than a longer pitch.
- You depend on features MepMail doesn't have. Marketing campaigns, audience segmentation, a large template system, a mature dashboard: if that's your workflow, Resend / SendGrid / Postmark are the right call today. SDK compatibility is not the product.
- You're on an enterprise contract. Volume discounts, SLAs, dedicated IPs and compliance paperwork are a different purchase from a $20/month plan. We are not competing there.
- You send very little. Under roughly 10K emails/month the absolute savings are small, and switching cost can exceed them.
- You need a support SLA now. MepMail is small. If downtime costs you more than the price difference, pay the incumbent.
- You want years of operational track record. MepMail doesn't have the operating history the established providers do. Negative features are the honest trade you're making.
If it's still worth trying
The beta is open right now: no cap on how many accounts, around 100 emails/day per account, no card needed — https://mepmail.je4ndev.com. Point your existing Resend client at it, send real mail, watch your DKIM and MAIL FROM setup, and see whether your actual use case is covered. If it isn't, you've spent an afternoon and no money.
Paid plans, if you outgrow the beta: $20/month (100K), $199/month (500K), $319/month (1M).
I'm not going to tell you to move production sending this week. Run it on one low-stakes stream first and keep your current provider as the fallback until you've seen it under your own load.
Top comments (1)
Useful comparison, and thanks for writing the method down. One lever outside the price table: sends to addresses on mistyped or throwaway domains still count towards the tier, so a DNS check on the domain at signup trims volume that was never going to land.