Alternatives
Coming from Resend? Keep the SDK.
Keep the official Resend SDK for supported sending calls. Compare the recurring prices below, choose a sending plan and use the migration CLI to review what can move before changing traffic.
Pro is selected after signup so you can review the plan in Billing. Creating the account does not purchase a subscription; confirmation happens there.
import { Resend } from "resend";
const resend = new Resend("ms_…", {
baseUrl: "https://api.mepmail.dev",
});
await resend.emails.send({
from: "Acme <onboarding@acme.dev>",
to: "delivered@example.com",
subject: "Hello from MepMail",
});
{ "id": "a1b2c3d4-…" }Alternatives
Resend vs MepMail, volume by volume.
MepMail’s regular monthly fees and Resend’s lowest published option at each volume, including overage where needed, checked on 2026-10-16. Excludes introductory offers and annual discounts; features and terms vary.
| Emails/month | Resend | MepMail | Estimated difference |
|---|---|---|---|
| 110k | US$ 44 Pro 100K at US$ 35 + 10,000 extra at US$ 0.90/1k | US$ 29 | Difference: 34% · US$ 15/month |
| 220k | US$ 143 Pro 100K at US$ 35 + 120,000 extra at US$ 0.90/1k | US$ 55 | Difference: 62% · US$ 88/month |
| 550k | US$ 385 Scale 500K at US$ 350 + 50,000 extra at US$ 0.70/1k | US$ 129 | Difference: 66% · US$ 256/month |
| 1.1M | US$ 715 Scale 1M at US$ 650 + 100,000 extra at US$ 0.65/1k | US$ 239 | Difference: 67% · US$ 476/month |
| 1.65M | US$ 903 Scale 1.5M at US$ 825 + 150,000 extra at US$ 0.52/1k | US$ 349 | Difference: 61% · US$ 554/month |
| 2.75M | US$ 1,265 Scale 2.5M at US$ 1,150 + 250,000 extra at US$ 0.46/1k | US$ 549 | Difference: 57% · US$ 716/month |
Resend source: resend.com/pricing, checked on 2026-10-16. MepMail: the regular monthly fee shown on this page. USD before taxes; features and terms are not equivalent.
How to read this comparison
Percentages are arithmetic differences between the amounts shown, not a promise of savings or feature parity. MepMail’s introductory offer and annual option are excluded; also compare limits, overage terms and support.
What carries over
- The official Resend SDK: new Resend("ms_…", { baseUrl: "https://api.mepmail.dev" }).
- The sending endpoints you already call: /emails, /emails/batch and /emails/{id}/cancel.
- Domain, key, webhook, template and suppression management, with the same request shapes where the two overlap.
- The SMTP relay, for stacks that send over SMTP instead of HTTPS.
What does not carry over
- Inbound email, dedicated IPs and SSO are not part of the compatibility promise.
- The management surface is smaller: we cover sending, domains, keys, webhooks, templates, suppressions and contacts, but not every endpoint Resend ships.
- Free and Starter have a daily limit instead of overage billing: sends keep going up to 50% past it, then wait in a queue for the next day, never on your card; new sends are refused only when that queue reaches 3× the daily limit.
- Attachment limit per message: 1 MB on Free and Starter, 5 MB on Pro, 10 MB on Scale.
Migration
Review the move. Then switch sending.
Run this command locally with your Resend and MepMail API keys. It reads Resend with GET requests, shows a migration plan and asks for confirmation before writing to MepMail.
npx @mepmail/cli migrate --from resend- Choose a sending plan for your volume and create a MepMail API key. Free is optional; it is not a required first step.
- Run the CLI and review the proposed changes for contacts, segments, topics, properties, domains, templates, webhooks, suppressions and broadcasts. Resource and account limits still apply.
- Complete the manual checklist: verify the new domain DNS, replace API keys and review template fields. Point the SDK at https://api.mepmail.dev with the new key for supported calls.
- Check subscription preferences and finish contact enrichment before topic sends or broadcasts. Send a controlled test, check its result in the panel and then switch the traffic you have validated.
DNS verification, source rate limits and account size affect the work required. Keep the existing integration available while you validate; there is no fixed migration time or feature-parity guarantee.
Check these differences before cutover
- API key secrets, DNS/DKIM records and sent email history are not copied. Domains need new verification; template from, reply_to and variables require manual review.
- Draft and scheduled broadcasts arrive as drafts. Sent broadcasts are skipped by default. Unsupported webhook event types are omitted; check the resulting endpoints and events.
- Contacts CSV import via POST /contacts/imports is not supported. Use JSON POST /contacts/batch; PATCH /contacts/{id}/topics expects a bare array of subscriptions.
- This migration covers the sending API. Correio is a separate mailbox product; this guide does not migrate inboxes or promise inbound compatibility.
Read the migration guide and API differences · Integration quickstart
Ready to move your sending?
Choose Pro, review the full migration checklist and validate your sending flow before moving production traffic. You can compare the other plans before confirming a purchase.
Choose Pro and integrate