Resend

Resend — Developer-first email API built around React Email components. Resend is a transactional email API founded by ex-Vercel engineers that treats the send call as a typed function and the template as a React component. It maintains React Email, the de facto standard for building email markup in JSX, and its Node SDK accepts a React element directly. Broadcasts adds a campaign product on top, so it now covers transactional and marketing without the split most competitors force. Built by Resend, Inc.. Founded 2023. Series A.

We track it in 1 comparison — Email APIs — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 12 other tools, and what follows is where it visibly separates from them.

Where it wins.

• Time to first send — 10 min, the best figure of the 13 here.
• DKIM/DMARC friction — 1, the best figure of the 13 here.
• React Email / MJML — react-email, mjml, tied for best across 3 of 12 tools.
• MCP server — Yes, and it is the only one of 7 here that manages it.
• Price / 1k emails — $0.4 /1k, 3rd of 11.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

• Log retention — 4320 min, 6th of 9. Postmark records 64800 min.
• Throughput ceiling — 7,200 emails/hr, the weakest of the 3 here. Amazon SES records 50,400 emails/hr.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 25 of 25 tracked fields carry a value for Resend, and 4 of those cite a document you can open. Last verified 2026-06-01. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is AhaSend. Resend is ahead on Hosted templates (code-editor against none) and Product scope (both against transactional-only). AhaSend takes Pricing model (pay-as-you-go against volume-tiers). That pattern repeats across the rest of the roster — see Resend alternatives for the other rivals, each compared the same way.

Company

Resend, Inc.

Founded

2023

Funding

Series A

Fields we track

25 of 25

Last verified

2026-06-01

The fastest path from nothing to a delivered email, and the only provider where the template layer lives in your codebase rather than a dashboard. You pay four times SES for that, and log retention is stingy.

Time to first send

10 min1st of 13

Community-reported

DKIM/DMARC friction

11st of 13

Inferred

React Email / MJML

react-emailmjml1st of 12

Vendor-claimedverified 2026-06-01source

Log retention

4320 min6th of 9

Inferred

MCP server

●Yes1st of 7

Community-reported

Price / 1k emails

$0.4 /1k3rd of 11

Vendor-claimedverified 2026-06-01source

llms.txt docs

●Yes1st of 12

Inferred

Event webhooks

deliveredopenedclickedbounced+28th of 13

Vendor-claimedverified 2026-06-01source

Resend is the right call in these situations, each one drawn from a field we actually record:

• Shipping transactional email this afternoon.
• React and Next.js codebases that want templates in the repo.
• Teams who would rather pay than run an approval gauntlet.
• Time to first send is your binding constraint. Resend records 10 min, the best figure in the Email APIs roster. We define that field as wall-clock from starting signup on a clean account to a message delivered to a Gmail inbox that is NOT a verified address on the account.
• DKIM/DMARC friction is your binding constraint. Resend records 1, the best figure in the Email APIs roster. We define that field as judgement, 1–5, of authentication setup effort.
• React Email / MJML is your binding constraint. Resend records react-email, mjml, the best figure in the Email APIs roster.
• MCP server is your binding constraint. Resend records Yes, which only 1 of the 7 tools in the Email APIs roster do.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• Log retention. Resend records 4320 min, 6th of 9 in the Email APIs roster. Postmark records 64800 min on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Throughput ceiling. Resend records 7,200 emails/hr, the weakest of the 3 tools in the Email APIs roster. Amazon SES records 50,400 emails/hr on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. Nothing, on the fields we track: all 25 of them carry a value for Resend. That is unusual and it will decay — vendors add dimensions faster than we add columns — so the verification dates beside each figure matter more than the completeness does.