Resend Review

Resend sells email sending as a developer product: a REST API and SMTP relay, templates written as React components instead of drag-and-drop builders, and webhooks for tracking delivery events inside your own app. It's aimed at engineers shipping transactional mail — receipts, magic links, password resets, onboarding sequences — who want that workflow to look like the rest of their codebase rather than a separate marketing tool. This review covers what's verifiable from Resend's own site: current pricing, what each tier actually includes, and where the real costs sit.

Verdict at a glance

What kind of tool is Resend?

Resend is an email-sending platform built for engineering teams rather than marketing teams. Instead of a WYSIWYG campaign builder, the core interface is an API: you call it from your backend, or you write templates as React components using Resend's own React Email library, and Resend handles delivery, domain authentication, and event tracking. It covers two overlapping use cases — transactional email (billed by emails sent) and marketing/broadcast email to opted-in lists (billed by contacts stored) — through one dashboard.

How it works

Setup is API-key-first: create an account, verify a sending domain (Resend automates the SPF, DKIM, and DMARC records), and start sending through the REST API, SMTP, or one of the official SDKs for Node.js, Python, PHP, Ruby, Go, Java, Laravel, Rust, and .NET. A CLI and MCP integration let the API be driven from a terminal or from AI coding assistants like Cursor and Claude. Webhooks push delivery, bounce, open, and click events back to your application in real time, which is the piece that replaces a chunk of what teams used to build themselves on top of raw SMTP providers.

For marketing sends, Resend layers "Audiences" (contact lists) and broadcast sending on top of the same account — useful if you want one vendor for both product and marketing mail, but worth noting it's priced and limited separately from transactional volume.

Resend pricing (2026)

A few things the pricing page doesn't lead with:

• Marketing contacts are a separate meter. The Free tier includes 1,000 contacts for broadcasts; paid marketing tiers run from $40/month (5,000 contacts) up to $650/month (150,000 contacts). A team sending both transactional and marketing email is buying two capacity pools, not one — budget for both if you need Audiences.
• Dedicated IPs cost extra and have a floor. The $30/month add-on is only available on Scale plans, and only makes sense once you're sending more than 3,000 emails a day; below that, Resend's shared-IP pool is the only option.
• Domain limits scale with plan tier — 1 domain on Free, 10 on Pro, 1,000 on Scale — which matters for agencies or platforms sending on behalf of multiple client domains.

What we could and couldn't verify

We were not able to load independent review data for this pass — G2's review page and Trustpilot both blocked automated access, and no third-party review aggregator returned usable rating or review-count data. We're not citing a star rating or review theme here because we don't have one we can attribute honestly; treat any rating you see elsewhere as something to check directly on G2, Trustpilot, or Reddit (r/webdev, r/SaaS) before relying on it. What we did verify directly from Resend's own site: current pricing tiers, plan-by-plan feature limits, and the core feature set (API, React Email, SDKs, webhooks, domain authentication).

Pros and cons

Pros

• Clean, well-documented API and broad official SDK coverage across major backend languages
• React Email lets templates live in version control alongside application code
• Domain authentication (SPF/DKIM/DMARC) is automated rather than manual
• Free tier is usable for real low-volume projects, not just a demo
• Webhooks cover the delivery events most apps actually need to track

Cons

• Transactional and marketing volume are billed separately, which can surprise teams that assumed one price covered both
• Dedicated IPs are locked behind the Scale plan and a minimum daily volume
• No independently verifiable review data found in this research pass, so real-world deliverability and support experiences are unconfirmed here
• Overage pricing on lower tiers ($0.90/1,000) is steeper than the top Scale tiers, so costs don't scale smoothly for teams growing past their plan

Resend alternatives

Resend competes in the developer-first transactional and marketing email API space, alongside:

• Postmark — long-standing reputation for transactional deliverability, similar developer-first positioning.
• SendGrid (Twilio) — larger, more enterprise-oriented, broader marketing feature set.
• Mailgun — API-first sending with a longer track record at high volume.
• Brevo — combines transactional API with a more marketing-team-friendly UI and cheaper contact-based plans.
• Amazon SES — the low-cost, low-frills option for teams willing to build their own tooling on top.
• Customer.io — worth considering if the actual need is behavior-triggered lifecycle marketing rather than raw sending.

Who should use Resend — and who shouldn't

Good fit: engineering teams shipping transactional email (auth, receipts, notifications) who want an API and SDKs that feel native to their stack; teams already using React who want templates as code; startups that have outgrown a legacy provider's dashboard-first workflow but don't need enterprise deliverability consulting yet.

Poor fit: marketing teams whose primary need is a visual campaign builder and audience segmentation rather than an API; anyone needing dedicated IPs at low volume (the add-on requires Scale-plan spend and a 3,000/day minimum); teams that want transactional and marketing email under one flat price rather than two separately metered products.