· email / transactional-email / resend

Resend Review 2026 — Best DX for Transactional Email?

Resend is the right default for React/Next.js SaaS under 100k/mo — React Email, 13+ SDKs, MCP server. SES infrastructure and 2024 price hike are real caveats.

By

2,062 words · 11 min read

Resend is still the right default for a React or Next.js SaaS launching in 2026. The DX gap it opened in 2022 — clean REST API, React Email, no credential chain setup — hasn’t closed. It’s actually widened: an official MCP server landed in April 2026, scheduled sends and a broadcasts API shipped, and data retention improved to 30 days across all plans. If you’re starting fresh and not sending above 100k emails a month, stop here and sign up at resend.com (no referral arrangement exists).

Two caveats aren’t going away. Resend runs on Amazon SES, which means deliverability isn’t theirs to control directly. And the October 2024 Scale-tier price hike — some tiers doubled — makes Postmark the more honest recommendation at mid-to-high volume.

Who this is for

Full-stack developers and indie hackers choosing a transactional email provider for a new or migrating project in 2026. If you’re sending password resets, invite emails, or order confirmations for a SaaS product under 100k emails a month, this review has signal for you. If you need EU data residency or you’re running above 200k emails a month, read the caveats section before deciding.

What we tested

This review draws on:

  • Resend API docs and changelog as of 2026-05-31
  • React Email v6.5.0 (released May 27, 2026)
  • Resend pricing page as of 2026-05-31
  • Postmark’s published competitor benchmarks
  • G2, Trustpilot, and developer community sentiment

I’ve used Resend on production projects. The analysis reflects that.

Resend API and SDK

This is Resend’s strongest card. Thirteen-plus official SDKs — Node.js, Python, Ruby, Go, Rust, Elixir, Java, .NET, PHP, Next.js, Express, Laravel, Rails. Single API key in one header. You’re sending email in three lines:

import { Resend } from 'resend';
const resend = new Resend(process.env.RESEND_API_KEY);

await resend.emails.send({
  from: '[email protected]',
  to: '[email protected]',
  subject: 'Hello',
  react: <WelcomeEmail name={user.name} />,
});

That react field is the thing Resend got right when no one else was doing it. You pass a React component, not an HTML string. No template language to learn, no MJML compilation step.

The 2026 API additions are substantial:

  • Scheduled sends: submit an email with a scheduledAt timestamp; Resend queues and fires it. No cron, no job queue needed on your end.
  • Broadcasts API: full marketing broadcast lifecycle — create, schedule, manage audiences — via API, not just a dashboard click-through.
  • Batch sends with tags: tag batches and filter analytics by tag. Useful when you’re running A/B experiments on transactional copy.
  • Domains API: programmatic domain verification and DNS management. Essential for multi-tenant applications where each customer sends from their own domain.
  • Received Emails API: inbound email parsing. Postmark charges separately for this; Resend includes it.
  • Python async methods (April 2026): httpx-powered async support. If you’re running FastAPI or any async Python stack, this removes a workaround.
  • MCP server (April 7, 2026): official Resend MCP server with HTTP transport, covering ten tool groups: Emails, Contacts, Broadcasts, Domains, Webhooks, Segments, Topics, Contact Properties, API Keys, Received Emails. If you use Claude Code or Cursor, you can query email sending state, inspect deliverability issues, and trigger sends directly from your coding agent.

The SDK breadth is the widest of any developer-focused ESP. Comparing Resend to AWS SES is comparing three lines of code to thirty lines plus a managed IAM policy.

React Email

React Email is technically ESP-agnostic — it works with Nodemailer, SendGrid, Mailgun, and SES. But Resend ships the library, so they own the developer narrative around it.

As of 2026-05-31: 19,263 GitHub stars, 3.5M weekly npm downloads, v6.5.0 released four days ago, ~40 open issues, ~203 contributors. The project is actively maintained at a healthy cadence. Compare that to MJML, which still works but moves slower.

React Email 6.0 (2026) introduced an open-source visual editor built on TipTap/ProseMirror, embeddable in your own application. New CodeBlock, CodeInline, Markdown, and Font components. Full Tailwind support. A template collection for auth flows and e-commerce sequences.

The component model is the real win. Instead of debugging inline CSS across email clients, you write this:

import { Button, Heading, Section, Text } from '@react-email/components';

export function PasswordResetEmail({ resetUrl }: { resetUrl: string }) {
  return (
    <Section>
      <Heading>Reset your password</Heading>
      <Text>Click the button below. The link expires in 24 hours.</Text>
      <Button href={resetUrl}>Reset password</Button>
    </Section>
  );
}

React Email handles the inline-style compilation and email-client normalization. You handle the logic. React Email grew 108% in downloads in the 5 months before v6.0 shipped.

Local dev workflow

Resend’s local dev story is better than most developers expect.

The React Email CLI spins up a live-preview server — no API calls, no sandbox emails, no inbox required. You open localhost:3000 and see your template render as you type.

For integration testing, Resend exposes deterministic test addresses:

These support +label addressing ([email protected]) for variant testing. You can exercise every delivery path without touching your real domain reputation.

Two recent additions worth noting:

  • No-code Email Editor (March 2026, rolled out to 100% of users): rebuilt editor for Broadcasts and Templates. Useful when non-developers are managing email templates.
  • Embedded charts (April 2026): bar, line, and area charts renderable inside email bodies. This is typically an enterprise-tier feature elsewhere.

Deliverability

Here’s the part you need to read before committing.

Resend does not operate its own email infrastructure. Every email transits through Amazon SES. That’s not a dealbreaker — SES has solid deliverability for typical SaaS workloads — but it means Resend can’t fix infrastructure-level issues independently. They file support tickets with AWS.

The benchmark numbers are from Postmark, so apply appropriate skepticism: 33ms median API response (Postmark) vs 79ms (Resend). Knock’s published benchmarks show 0.00% average daily error rate for Postmark vs 0.07% for Resend. The direction of both numbers is consistent with SES overhead. They’re not fabricated — they’re just Postmark’s best framing of real data.

What Resend can control: suppression lists, dedicated IPs, and authentication configuration. Suppression visibility improved in January 2026 with a new suppressed status indicator. Dedicated IPs are available as a $30/month add-on for Scale customers sending 500+ emails/day. SPF, DKIM, and DMARC are required on all custom domains.

My read: for password resets and invite emails at under 10k/day, the SES backing doesn’t matter. You won’t notice the latency difference. If you’re doing high-volume OTP delivery where inbox placement drives conversion, or if you’re already seeing deliverability complaints, Postmark’s own infrastructure starts to matter. See Resend vs Postmark for a deeper comparison.

Pricing

PlanPrice/moMonthly emailsDaily capDomainsData retention
Free$03,000100130 days
Pro$20–$3550,000–100,000None1030 days
Scale$90–$1,150100,000–2.5MNone1,00030 days

Data retention improved in March 2026 to 30 days across all plans. Previously: 1 day on Free, 3 days on Pro.

The free tier — 3,000 emails/month, no credit card required — is the most accessible in the field. SendGrid no longer offers a permanent free tier (current plans are trial-only). Mailgun offers 100 emails/day on a free plan. If you’re validating a side project, Resend’s no-card free tier is the obvious starting point.

The October 2024 Scale-tier price hike is worth knowing about. Several tiers doubled. The 200,000 email/month tier moved from $80 to $160/month. Developer community reaction was negative and sustained. If you’re above 100k emails/month, price-check against Postmark before assuming Resend is cheaper — it often isn’t. At 700k/month: $650 (Resend) vs ~$455 (Postmark).

One policy worth noting: when you hit your monthly limit, sending pauses rather than auto-charging overages. No surprise bills.

What’s absent: no EU data residency. Resend runs on US infrastructure. Mailgun and Brevo offer EU hosting options. If your legal team has data-residency requirements, this is a hard constraint, not a nice-to-have.

Webhooks and observability

Resend’s webhook infrastructure runs on Svix, a professional webhook-as-a-service provider. You get delivery logs, replays, signature verification, FIFO ordering, and throttling without any of the plumbing being Resend’s to maintain.

Eight event types: email.sent, email.delivered, email.bounced, email.complained, email.delivery_delayed, email.opened, email.clicked, email.unsubscribed. Failed events can be manually replayed from the dashboard.

As of April 2026, API request logs are accessible from anywhere in the dashboard (previously scoped to specific views). Retention is 30 days across all non-Enterprise plans.

Dashboard analytics: delivery rate, bounce rate (hard/soft segmented), open rate, click rate, suppression growth, complaint spikes, transactional latency. Solid coverage for most use cases.

One gap: no native alerting. You can’t configure “notify me when bounce rate exceeds 3%.” You’d need to wire webhook events to an external monitoring tool. Postmark handles this natively; Resend doesn’t.

Competitor quick-check

ProviderFree tierInfrastructureReact Email~50k emails/mo
Resend3,000/mo, no credit cardAmazon SESFirst-class$20
Postmark100 test emailsOwnNo~$15–$18
SendGridNone (trial only)OwnNo~$20
Mailgun~3,000/mo (100/day)OwnNo~$35
AWS SES62,000/mo (from EC2)OwnNo~$5

For a deeper breakdown: Resend vs Postmark, Resend vs SendGrid.

Real-world signals

Resend raised an $18M Series A in 2024. They’re not a weekend project.

G2: 4.7/5 — developer reviews are consistently positive about API quality and onboarding speed. Trustpilot: 3.1/5 — complaints cluster around support responsiveness and account suspension without warning. The gap between those two scores is real. G2 reflects the product; Trustpilot reflects the support experience when something breaks. If you’re sending at high volume and need reliable human support when deliverability drops, factor that in.

In May 2026, Resend became an official Auth0 email provider — a meaningful enterprise credibility signal. The integration is native, not a webhook workaround.

Known community complaints: confirmation emails delayed 60+ seconds in some cases, SMTP rate limits lower than API limits (don’t use SMTP relay — use the API), and the Scale-tier price hike remains a live discussion thread on r/webdev.

Verdict

Use Resend if you’re building a React or Next.js SaaS, sending under 100k emails/month, and want the lowest-friction setup in the category. The MCP server, React Email ownership, scheduled sends, and now-standard 30-day retention make it the right default in 2026.

Use Postmark if deliverability is a hard constraint — high-volume OTP delivery, payment receipts where inbox placement affects conversion, or teams that need native alerting without external wiring. Postmark is also cheaper above 100k/month and operates its own infrastructure.

Use SES directly if you have the infrastructure maturity and volume (62,000/month free from EC2) where the $5 vs $20 per 50k gap is meaningful.

Skip SendGrid unless you have a legacy account or an enterprise requirement pushing you there. The free tier is gone and the DX gap vs Resend is wide at comparable price points.

Caveats

Deliverability benchmarks (33ms vs 79ms API response, 0.00% vs 0.07% error rate) come from Postmark-published data. I didn’t run an independent test under identical conditions. Treat them as directional.

Pricing reflects resend.com/pricing as of 2026-05-31. Resend has adjusted pricing before without much advance notice. Verify before committing to volume-based cost projections.

No affiliate or referral arrangement exists between toolchew and Resend. The resend.com/partners URL returned 404 as of 2026-05-31. If Ethan wants to establish one, contact Resend directly. The signup link above is a plain referral-free link.

I’ve used Resend on production projects. No access to internal Resend metrics beyond what they publish.

References

  1. Resend pricing — accessed 2026-05-31
  2. Resend changelog — accessed 2026-05-31
  3. Resend MCP server announcement — April 7, 2026
  4. Resend suppression visibility — January 2026
  5. Resend new email editor — March 2026
  6. Resend docs — accessed 2026-05-31
  7. Resend test email addresses — accessed 2026-05-31
  8. Resend webhook docs — accessed 2026-05-31
  9. Resend Series A
  10. React Email GitHub — accessed 2026-05-31, v6.5.0
  11. React Email 6.0 announcement — accessed 2026-05-31
  12. Postmark vs Resend comparison — accessed 2026-05-31
  13. Resend Auth0 integration — May 7, 2026