Mailgun alternatives
Four email services a developer leaving Mailgun would actually consider, weighed on inbound mail, signed webhooks, agent tooling and what an extra thousand emails costs. Every figure was read from the vendor's own page on 2026-09-16.
- Mailgun
- Mailgun is an email API from Sinch with six official SDKs, an SMTP relay, rule-based inbound routing and signed webhooks, sold on plans whose log retention grows with the tier.
- What this page is
- A list of four email services that would take the mail Mailgun sends for you today, compared on the same rows and against the same sources. Rasket is one of them, and we build it — so every claim we make about ourselves is linked to a Rasket page, and every claim about anybody else is linked to theirs.
Key takeaways
- Extra emails, per 1,000 — Rasket: $0.60. Mailgun: From $1.80 on Basic.
- Entry paid plan — Rasket: $20 a month for 50,000 emails. Mailgun: $15 a month for 10,000 emails.
- Free plan — Rasket: 3,000 emails a month, 100 a day, 3 domains. Mailgun: 100 emails a day.
- Inbound email — Rasket: Yes. Mailgun: 1 route on Free, 5 on Basic, full routing from Foundation.
- Official SDKs — Rasket: Node.js and Python. Mailgun: Ruby, PHP, Python, Java, Go and Node.js.
Why developers look for a Mailgun alternative
Three reasons that are rows of the table below rather than opinions. Each one is something Mailgun publishes about itself.
- Free and Basic keep one day of log retention, and thirty days needs the Scale plan.
- Extra email starts at $1.80 per thousand on Basic, against $0.60 on Rasket.
- The pricing page does not say whether marketing or broadcast sending is included, so it is not something you can check before you buy.
None of those is a reason on its own. They are reasons if they describe what you are doing: a product past its free tier, a support conversation longer than the history you can read, a campaign you would rather not buy twice.
Four alternatives to Mailgun
Rasket is first because we build it, and you should read the table before you take our word for the order.
1.Rasket
Yes, on retention and price in particular. Mailgun keeps one day of logs on its Free and Basic plans and thirty only at Scale; every self-serve Rasket plan keeps thirty. Extra email starts at $1.80 per thousand on Basic against $0.60 on Rasket. What Mailgun has and Rasket does not is an SMTP relay, four more SDK languages and rule-based inbound routing.
Best for: Developers who want sending, receiving and broadcasts behind one API key
2.MailerSend
MailerSend is an email API with six official libraries, an SMTP relay, signed webhooks and an MCP server, sold on small plans that start below every other entry price here. Free plan: 500 emails a month, 1 domain, 1 template. Extra emails, per 1,000: $1.30 on Starter and Professional.
Best for: Small projects that want the cheapest paid plan on this list
3.Brevo
Brevo is a marketing platform with a transactional email API attached: an SMTP relay, three official SDKs, secured webhooks, inbound parsing, idempotency keys for batch sends and an MCP server over its developer documentation. Free plan: Not published. Extra emails, per 1,000: Not published.
Best for: Teams who want marketing, CRM and transactional email from one vendor
4.Resend
Resend is an email API with a dashboard, nine official SDKs and a documentation set written for agents as well as people; its transactional plans and its marketing plans are priced apart. Free plan: 3,000 emails a month, 100 a day, 3 domains. Extra emails, per 1,000: $0.90.
Best for: Teams writing their emails as React components
The four, row by row
The same rows for all four, with the source of every cell numbered at the foot of the page.
| Criterion | Rasket | MailerSend | Brevo | Resend |
|---|---|---|---|---|
| Inbound email | Yes Rasket, source 1Receive at your own domain on every plan, delivered as a signed webhook. | On the Starter and Professional plans MailerSend, source 13 | Yes Brevo, source 18Inbound parse webhooks, documented in their developer guide. | Yes Resend, source 27The pricing page lists inbound emails under "All plans include". |
| Transactional and broadcasts on one plan | Yes Rasket, source 2A broadcast travels the same send pipeline as a password reset, on the same plan and the same key. | Not published MailerSend, source 13 | Marketing campaigns and transactional email are both in the API Brevo, source 19 | Marketing email is priced as a separate plan Resend, source 27 |
| Signed webhooks | Yes Rasket, source 3 | Yes MailerSend, source 14A Signature header holding an HMAC-SHA256 of the body, keyed by a per-webhook signing secret. | Yes Brevo, source 20Their secured webhooks guide. | Yes Resend, source 28 |
| Replay a webhook event | Yes Rasket, source 3Send the event again from the dashboard or the API; a replay carries the identical payload under the same event id. | Not published MailerSend, source 14 | Not published Brevo, source 19 | Yes Resend, source 29 |
| Idempotent sends | Yes Rasket, source 4An Idempotency-Key is remembered for 24 hours. | Not published MailerSend, source 15 | For batch transactional email Brevo, source 21 | Yes Resend, source 30 |
| Versioned templates | Yes Rasket, source 5Published versions with typed variables; every send records the version it used. | Not published MailerSend, source 15 | Not published Brevo, source 19 | Yes Resend, source 31Templates carry a version history. |
| Automations | Yes Rasket, source 6 | Not published MailerSend, source 13 | Workflows, started by events their tracker records Brevo, source 22 | Yes Resend, source 32 |
| MCP server | Yes Rasket, source 7An HTTP MCP server with seven toolsets, plus a setup skill. | Yes MailerSend, source 16 | Yes Brevo, source 23 | Yes Resend, source 33A hosted server and a self-hosted one, both listed in their index for agents. |
| Markdown docs and llms.txt | Yes Rasket, source 8Markdown at every docs URL, with llms.txt and llms-full.txt. | An llms.txt index MailerSend, source 17The index is published; a .md suffix on a help URL answered 404 on the day. | Yes Brevo, source 19A .md suffix on a developer documentation URL returns Markdown, and llms.txt indexes them. | Yes Resend, source 34Every docs URL answers to a .md suffix, and llms.txt indexes them. |
| Official SDKs | Node.js and Python Rasket, source 9 | PHP, Node.js, Go, Python, Ruby and Java MailerSend, source 15 | Node.js, Python and PHP Brevo, source 24 | Node.js, PHP, Python, Ruby, Go, Java, Rust, Elixir and .NET Resend, source 34 |
| Free plan | 3,000 emails a month, 100 a day, 3 domains Rasket, source 10 | 500 emails a month, 1 domain, 1 template MailerSend, source 13 | Not published Brevo, source 25Their pricing page builds its plan table in the browser; nothing could be read from the page itself on the day. | 3,000 emails a month, 100 a day, 3 domains Resend, source 27 |
| Entry paid plan | $20 a month for 50,000 emails Rasket, source 10 | $7 a month for 5,000 emails MailerSend, source 13The Hobby plan, paying monthly; the page opens on yearly billing, where the same plan is $5.60 a month. | Not published Brevo, source 25Same page, same reason. | $20 a month for 50,000 emails Resend, source 27 |
| Extra emails, per 1,000 | $0.60 Rasket, source 10The rate steps down to $0.25 as the Scale ladder climbs. | $1.30 on Starter and Professional MailerSend, source 13The page does not state a rate for the entry Hobby plan. | Not published Brevo, source 25Same page, same reason. | $0.90 Resend, source 27 |
| Data retention | 30 days on the self-serve plans Rasket, source 10Custom retention on a Custom plan. | 1 day on Free and Hobby, 7 on Starter, 30 on Professional MailerSend, source 13 | Not published Brevo, source 25 | 30 days on the free plan Resend, source 27The pricing page does not state a retention window for the paid plans. |
| Dedicated IP | An add-on on Scale Rasket, source 10 | An add-on above 100,000 emails a week MailerSend, source 13The page does not state its price. | Not published Brevo, source 25 | $30 a month, above 3,000 emails a day Resend, source 27 |
| SMTP relay | No Rasket, source 11Sending is the REST API, the SDKs and the MCP server. There is no relay to point a mail client at. | Yes MailerSend, source 13 | Yes Brevo, source 26 | Yes Resend, source 35 |
| DKIM key size | 2048-bit, one key per domain Rasket, source 12 | Not published MailerSend, source 15 | Not published Brevo, source 19 | Not published Resend, source 36 |
| Best for | Developers who want sending, receiving and broadcasts behind one API key | Small projects that want the cheapest paid plan on this list | Teams who want marketing, CRM and transactional email from one vendor | Teams writing their emails as React components |
Moving your domain off Mailgun
Add the domain in Rasket, publish the DKIM, SPF and DMARC records we generate, and leave Mailgun sending until verification passes. Then move the call to POST /emails with the key in an Authorization header. Inbound routes become a receiving domain and one signed webhook, with the matching you were expressing as rules written in your handler instead; your existing webhook verification is replaced by checking Rasket's signature, and you can replay an event from the dashboard while you get it right.
Nothing about a verified sending domain is exclusive, so both providers can hold it while you move. Send a small share of your mail through the new one first, watch the delivery and bounce events, and cut the rest over once the numbers look like the old ones.
Frequently asked questions
What is the best Mailgun alternative for developers?
We build Rasket, so read this as a disclosed preference and not a verdict. Yes, on retention and price in particular. Mailgun keeps one day of logs on its Free and Basic plans and thirty only at Scale; every self-serve Rasket plan keeps thirty. Extra email starts at $1.80 per thousand on Basic against $0.60 on Rasket. What Mailgun has and Rasket does not is an SMTP relay, four more SDK languages and rule-based inbound routing.
Is there a free Mailgun alternative?
Rasket: 3,000 emails a month, 100 a day, 3 domains. MailerSend: 500 emails a month, 1 domain, 1 template. Brevo: Not published. Resend: 3,000 emails a month, 100 a day, 3 domains. Each figure is from that vendor's own pricing page on 2026-09-16.
Which Mailgun alternative includes inbound email?
Rasket: Yes. MailerSend: On the Starter and Professional plans. Brevo: Yes. Resend: Yes. Inbound means receiving mail at your own domain, not just sending from it.
Which Mailgun alternative works with AI agents?
Rasket: Yes. MailerSend: Yes. Brevo: Yes. Resend: Yes. An MCP server is what lets an assistant call the API directly; Markdown docs and llms.txt is the other half, and it reads: Rasket: Yes. MailerSend: An llms.txt index. Brevo: Yes. Resend: Yes.
How do I move my domain off Mailgun?
Add the domain in Rasket, publish the DKIM, SPF and DMARC records we generate, and leave Mailgun sending until verification passes. Then move the call to POST /emails with the key in an Authorization header. Inbound routes become a receiving domain and one signed webhook, with the matching you were expressing as rules written in your handler instead; your existing webhook verification is replaced by checking Rasket's signature, and you can replay an event from the dashboard while you get it right.
Sources
- 1. Rasket — http://localhost:3000/features/receiving. Read 2026-09-16.
- 2. Rasket — http://localhost:3000/features/broadcasts. Read 2026-09-16.
- 3. Rasket — http://localhost:3000/features/webhooks. Read 2026-09-16.
- 4. Rasket — http://localhost:3000/docs/idempotency. Read 2026-09-16.
- 5. Rasket — http://localhost:3000/features/templates. Read 2026-09-16.
- 6. Rasket — http://localhost:3000/features/automations. Read 2026-09-16.
- 7. Rasket — http://localhost:3000/features/agents. Read 2026-09-16.
- 8. Rasket — http://localhost:3000/llms.txt. Read 2026-09-16.
- 9. Rasket — http://localhost:3000/about. Read 2026-09-16.
- 10. Rasket — http://localhost:3000/pricing. Read 2026-09-16.
- 11. Rasket — http://localhost:3000/features/email-api. Read 2026-09-16.
- 12. Rasket — http://localhost:3000/features/domains. Read 2026-09-16.
- 13. MailerSend — https://www.mailersend.com/pricing. Read 2026-09-16.
- 14. MailerSend — https://developers.mailersend.com/api/v1/webhooks.html. Read 2026-09-16.
- 15. MailerSend — https://developers.mailersend.com/. Read 2026-09-16.
- 16. MailerSend — https://developers.mailersend.com/mcp. Read 2026-09-16.
- 17. MailerSend — https://www.mailersend.com/llms.txt. Read 2026-09-16.
- 18. Brevo — https://developers.brevo.com/docs/inbound-parse-webhooks. Read 2026-09-16.
- 19. Brevo — https://developers.brevo.com/llms.txt. Read 2026-09-16.
- 20. Brevo — https://developers.brevo.com/docs/secured-webhooks. Read 2026-09-16.
- 21. Brevo — https://developers.brevo.com/docs/heterogenous-versions-batch-emails. Read 2026-09-16.
- 22. Brevo — https://developers.brevo.com/guides/track-website-activity. Read 2026-09-16.
- 23. Brevo — https://developers.brevo.com/docs/mcp-protocol. Read 2026-09-16.
- 24. Brevo — https://developers.brevo.com/docs/api-clients. Read 2026-09-16.
- 25. Brevo — https://www.brevo.com/pricing/. Read 2026-09-16.
- 26. Brevo — https://developers.brevo.com/docs/smtp-integration. Read 2026-09-16.
- 27. Resend — https://resend.com/pricing. Read 2026-09-16.
- 28. Resend — https://resend.com/docs/webhooks/verify-webhooks-requests. Read 2026-09-16.
- 29. Resend — https://resend.com/docs/webhooks/retries-and-replays. Read 2026-09-16.
- 30. Resend — https://resend.com/docs/dashboard/emails/idempotency-keys. Read 2026-09-16.
- 31. Resend — https://resend.com/docs/dashboard/templates/version-history. Read 2026-09-16.
- 32. Resend — https://resend.com/docs/dashboard/automations/introduction. Read 2026-09-16.
- 33. Resend — https://resend.com/llms.txt. Read 2026-09-16.
- 34. Resend — https://resend.com/docs/llms.txt. Read 2026-09-16.
- 35. Resend — https://resend.com/docs/send-with-smtp. Read 2026-09-16.
- 36. Resend — https://resend.com/docs/dashboard/domains/introduction. Read 2026-09-16.
Last checked 2026-09-16. Prices and plan contents change. Every figure above was read from the linked page on the date beside it; if one has moved since, the page it came from is the one to trust.
Try one of them against your own mail
Verify a domain, send a test, and compare the delivery events against what you get today.