Both send email over a REST API. Every row below was read from Rasket's own pages and Mailgun's own pages, and the day they were read is printed under the table.
Rasket is an email API for developers: one REST API and a dashboard for transactional email and campaigns, with inbound mail, signed webhooks and an MCP server in the same product and on the same key.
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.
| Criterion | Rasket | Mailgun |
|---|---|---|
| Sending and receiving | ||
| Inbound email | 1 route on Free · full routing from Foundation | |
| Transactional and campaigns on one plan | Not published | |
| Idempotent sends | Not published | |
| Versioned templates | Not published | |
| Automations | Not published | |
| SMTP relay | ||
| DKIM key size | 2048-bit | Not published |
| Webhooks and developer tools | ||
| Signed webhooks | ||
| Replay a webhook event | Not published | |
| MCP server | ||
| Markdown docs and llms.txt | ||
| Official SDKs | Coming soon | 6 languages · incl. Node.js, Python, Go |
| Plans and pricing | ||
| Free plan | 3,000 / mo · 100 a day | 100 / day |
| Entry paid plan | $20 / mo · 50,000 emails | $15 / mo · 10,000 emails |
| Extra emails, per 1,000 | $0.60 · down to $0.25 on Scale | $1.80 · on Basic, from $1.10 on Scale |
| Data retention | 30 days | 1 day · up to 30 on Scale |
| Dedicated IP | $30 / mo · on Scale | One on Scale · extra $59 / mo |
| Best for | Developers who want sending, receiving and campaigns behind one API key | Teams who route inbound mail with rules and want a relay in front of it |
Facts checked on against each company’s public pricing and documentation.
Mailgun publishes six official SDKs while ours are still coming, so a service in a language we do not cover has a maintained client from them today. Their inbound routing is rule-based rather than a single webhook, which is a genuinely different model: if you want mail matching one pattern stored and mail matching another forwarded, they express that as routes and we express it as code in your handler. They also start dedicated IPs at a lower volume than a Custom plan with us.
Mailgun is best for: Teams who route inbound mail with rules and want a relay in front of it
The rows to read here are retention and the cost of extra mail. Mailgun keeps one day of logs on Free and Basic, five on Foundation and thirty only at Scale, where every self-serve Rasket plan keeps thirty; extra email starts at $1.80 a thousand on Basic against $0.60. Both sign their webhooks, and both publish Markdown documentation and an MCP server, so the agent rows are a tie. Mailgun is the better choice when you want routing rules; Rasket when a day of logs is not long enough and campaigns belong on the same plan as the rest of your mail.
Rasket is best for: Developers who want sending, receiving and campaigns behind one API key
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 four more SDK languages and rule-based inbound routing.
Mailgun: 1 route on Free, 5 on Basic, full routing from Foundation. Rasket receives mail at your own domain on every plan, including the free one, and delivers each message to a signed webhook with its headers, text, HTML and attachments.
Mailgun's published Basic plan is $15 a month for 10,000 emails, so 50,000 means 40,000 extra emails at from $1.80 per thousand on top — the pricing page prices the tier with a slider rather than printing every step. Rasket is $20 a month for 50,000 emails with extra mail at $0.60 per thousand. Read both price lists for your own volume before deciding; these are the figures each page showed on the date checked.
Yes. Point any app that sends over SMTP at smtp.rasket.com on port 465 or 587, with the username rasket and an API key as the password, and each message becomes an ordinary API send: the same verified domains, suppressions, quota and webhooks. Moving an SMTP integration is a change of host and credentials, not of code.
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, or, for an app on their SMTP service, swap the postmaster login for the username rasket and a Rasket key and point it at smtp.rasket.com. 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.
It is close. Mailgun publishes an MCP server, Markdown at its documentation URLs and an llms.txt index; so does Rasket, with a setup skill and llms-full.txt as well. Neither of us is the one to avoid here. The difference is what the agent can reach in one place: a Rasket key covers sending, receiving, templates, contacts and campaigns, so an assistant does not need a second product to run a campaign.
Create a key, verify a domain, and send your first email the same morning. The free plan does not expire.