Both send email over a REST API. Every row below was read from Rasket's own pages and MailerSend'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.
MailerSend is an email API with seven official libraries, an SMTP relay, signed webhooks, inbound routing and an MCP server, sold on small plans that start below every other entry price here.
| Criterion | Rasket | MailerSend |
|---|---|---|
| Sending and receiving | ||
| Inbound email | ||
| 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 | 7 languages · incl. Node.js, Python, Go |
| Plans and pricing | ||
| Free plan | 3,000 / mo · 100 a day | 500 / mo · 1 domain |
| Entry paid plan | $20 / mo · 50,000 emails | $7 / mo · 5,000 emails |
| Extra emails, per 1,000 | $0.60 · down to $0.25 on Scale | $0.90 · plan cards; FAQ says $1.30 |
| Data retention | 30 days | 1 day · up to 30 on Professional |
| Dedicated IP | $30 / mo · on Scale | Enterprise · over 100,000 a week |
| Best for | Products that send campaigns and receive replies as well as sending receipts | Small projects that want the cheapest paid plan on this list |
Facts checked on against each company’s public pricing and documentation.
MailerSend's entry plan is the cheapest on this page: $7 a month for 5,000 emails, against $20 a month for 50,000 emails on Rasket, so a side project sending a few thousand messages pays less there than here. They publish seven official libraries while ours are still coming, and their Starter plan and above carry a 99.5% uptime SLA where we publish none. If your volume is small and steady, the arithmetic favours them and it would be dishonest to dress that up.
MailerSend is best for: Small projects that want the cheapest paid plan on this list
Which way this goes depends almost entirely on volume. Under about five thousand emails a month MailerSend is cheaper. Above that the comparison inverts: Rasket's entry plan is $20 a month for 50,000 emails where Starter costs $35 at 50,000, and history is thirty days on every self-serve Rasket plan against one day on Free and Hobby. Both receive inbound mail on every plan, both sign webhooks and both publish an MCP server and Markdown docs, so the developer-experience rows are close; Rasket adds replay, idempotency keys and versioned templates, which MailerSend's documentation does not describe.
Rasket is best for: Products that send campaigns and receive replies as well as sending receipts
Yes, once you are past a few thousand emails a month. Rasket's entry plan is $20 a month for 50,000 emails where MailerSend's Starter is $35 at that volume, and history is thirty days against one on their Free and Hobby plans. Below that volume MailerSend is genuinely cheaper, it publishes seven client libraries where Rasket's are not out yet, and it publishes an uptime SLA from Starter up.
MailerSend: Yes. The plan table marks inbound routing on every plan, Free included. 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.
At 50,000 emails a month Rasket is $20 a month for 50,000 emails. MailerSend's Starter plan is $35 at that volume, paying monthly, and their entry Hobby plan covers 5,000 emails for $7, so it does not reach this figure. MailerSend takes 10% off for yearly billing, so check which way the page's billing toggle is set before comparing.
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.
Verify the domain in Rasket with the DKIM, SPF and DMARC records we generate, then point your sends at POST /emails — or, over SMTP, point the mailer at smtp.rasket.com with the username rasket and a Rasket key. Templates are rewritten once and published as a version with typed variables; contacts come across as a CSV import. Your webhook endpoint is recreated in Rasket with its own signing secret — the verification is the same idea, an HMAC over the body — and you can replay an event from the dashboard rather than waiting for the next real one.
Both publish for them, and neither is far ahead. MailerSend runs an MCP server and serves Markdown at its developer documentation URLs with an llms.txt index; Rasket runs an MCP server with seven toolsets, a setup skill, Markdown at every docs URL, llms.txt and llms-full.txt. The difference is scope: a Rasket agent can also run a campaign on the same key, which MailerSend's pages do not describe.
Create a key, verify a domain, and send your first email the same morning. The free plan does not expire.