Resend review: email for developers who have tried everything else

Filed under Review

By Gerald · 18 June 2026

I have used SendGrid, Mailgun, AWS SES, and a few smaller services I would rather forget.

Each one taught me the same lesson: sending email at scale is easy on paper and annoying in practice. The APIs are cluttered. The dashboards are built for marketing teams. The documentation assumes you have already done this a hundred times. And every time you need to debug a failed delivery, you descend into a maze of logs, status codes, and support tickets that treat you like a small fish.

I switched Flow to Resend after a friend who builds SaaS products refused to stop talking about it. I was skeptical. Most developer tools that get hyped on Twitter collapse under real load or hide their limitations behind a beautiful landing page.

Resend did not collapse. It is not perfect, but it is the first email service I have used that feels like it was built by people who actually send code to production.

Resend is the email platform I wish existed five years ago. It is not an enterprise suite, and that is the point.

What Resend actually does

Resend is a transactional email API. It sends password resets, welcome emails, notifications and invoices, plus any other message triggered by your application. It also handles broadcast email for newsletters and marketing, though its real strength is the developer path into transactional mail.

The company was founded by the team behind React Email, a library for building email templates with React components. That lineage matters, because Resend is not a generic email provider that added an API later. It is an API-first product that happens to deliver email.

Developer experience: the API that does not fight you

Resend's API is RESTful and clean. You can send an email with a single POST request and a JSON body that looks exactly like you would expect.

The official SDKs cover Node.js, Python, Ruby, Go, and PHP among others. The Node.js client is small and typed. It does not pull in dependencies that create their own problems. In Flow's backend, the code that sends a password reset or an admin invite is about ten lines, including error handling.

Authentication is a simple API key. There is no OAuth dance, no separate secret management layer, and no legacy SOAP endpoint hiding in the documentation. You generate a key, copy it, and start sending.

The dashboard is sparse in a good way. You see sends, deliveries, bounces, and clicks. You can drill into a single email and see the full timeline: sent, delivered, opened, clicked, or bounced. That timeline has saved me hours compared to digging through SendGrid's event webhook logs.

Webhooks are also straightforward. You point Resend at a URL, choose the events you care about, and it POSTs clean JSON. Parsing SendGrid's webhook payload used to require its own utility function. Resend's payload is flat and obvious.

Deliverability: does it actually reach the inbox?

This is the question that matters more than API design. A beautiful request is worthless if the email lands in spam.

Resend uses dedicated IP pools and enforces domain authentication from day one. You cannot send from an unverified domain, which sounds like a small restriction but actually protects the shared pool from abuse. That discipline keeps the overall reputation high.

In my experience running Flow, deliverability has been excellent. Password reset emails and newsletter confirmations reach Gmail and Outlook inboxes consistently. Bounce rates stay low. I have not had to open a support ticket to ask why a provider is throttling us.

Resend also handles the infrastructure details that used to be my job: SPF, DKIM, DMARC alignment, and feedback loop monitoring. You add the DNS records it gives you, and it verifies them automatically. If something is misaligned, the dashboard tells you plainly.

Is it better than SendGrid's deliverability? For a small to mid-sized application, I think it is at least as good, and the setup is faster. For massive enterprise senders with dedicated account managers and custom IP warm-up programs, SendGrid still has deeper tooling. Most startups do not need that depth.

Resend pricing

Resend's pricing is simple, which already puts it ahead of most competitors.

These prices were shown on the official pricing page in June 2026.

The free tier is genuinely useful. Three thousand emails a month covers most early-stage products, including password resets and notifications, plus a small newsletter. You are not trapped into a paid plan the moment you verify your domain.

Pro scales to fifty thousand emails for twenty dollars. After that, overages are billed at a per-email rate. There are no hidden charges for dedicated IPs, webhook calls, or contact storage. The number on the pricing page is close to the number on your bill.

Compare that to SendGrid, where the free tier is limited to one hundred emails per day, and the first paid plan starts around twenty dollars for similar volume but with a dashboard cluttered by features you may not need. Or AWS SES, which is technically cheaper per email but requires you to build your own monitoring and templating, plus bounce handling.

React Email integration

This is where Resend separates itself from every other provider.

React Email lets you write email templates as React components. You get layout and styling, plus conditional logic, using code you already know. The templates render to HTML that works across clients, and you can preview them in a local dev server before they ever touch a real inbox.

Resend owns React Email, so the integration is native. You build a template, render it to HTML, and pass that HTML string directly into the Resend API. There is no separate template language to learn, no drag-and-drop editor that generates bloated markup, and no need to store templates inside the email platform.

Flow uses React Email for every transactional message. The password reset email, the admin invite, and the newsletter confirmation all live in the codebase as components. That means version control, type checking, and code review apply to email the same way they apply to everything else.

If you do not use React, this feature is irrelevant. You can send plain HTML or text through Resend just fine. But if you are already in the React ecosystem, the combination is hard to give up once you have used it.

The honest limitations

Resend is newer than its competitors, and that shows in a few places.

The template library inside the dashboard is small. Resend assumes you are bringing your own templates, ideally through React Email. If you want a large gallery of pre-built marketing templates you can customize in a browser, SendGrid and Mailgun offer more.

Enterprise features are thinner. There is no dedicated account manager included in standard plans. Advanced segmentation, A/B testing, and deep marketing automation are not the focus. Resend is an API for developers, not a full CRM with email attached.

The broadcast feature, which handles newsletters and bulk sends, works well but is younger than the transactional side. If your entire business is email marketing, you may outgrow it faster than the transactional API.

Support is responsive but text-based. I have received useful answers within hours, but there is no phone line for emergencies. For a mission-critical system where an hour of downtime costs thousands, that may be a factor.

Finally, platform risk exists with any newer vendor. Resend is well-funded and growing fast, but it has not been around as long as Twilio-owned SendGrid or Amazon's SES. The API is stable, but the company's long-term pricing and feature path are still being written.

Who should use Resend

Resend fits a specific profile.

You should try it if:

• You are a developer or a technical team building a product that sends transactional email.
• You want a clean API and typed SDKs rather than a dashboard-heavy platform.
• You use React and want to own your email templates in code.
• You value simple, predictable pricing without surprise add-ons.
• You need good deliverability without hiring an email operations specialist.

You should probably skip it if:

• You need a full marketing automation suite with drag-and-drop journeys and deep segmentation.
• You require a dedicated account manager, SLA guarantees, or phone support by default.
• You send millions of emails a month and need custom IP warm-up programs managed for you.
• You are not technical and want a WYSIWYG email builder as the primary interface.

Flow uses Resend. Here is why I switched.

Flow sends password resets, admin invites, newsletter confirmations, and reminder emails. That is not a huge volume, but every message matters. A password reset that hits spam is a support ticket. A newsletter confirmation that bounces is a lost subscriber.

I moved Flow from SendGrid to Resend because the API reduced friction, React Email let me own the templates, and the dashboard gave me enough visibility without demanding my attention. The free tier covered early usage, and the first paid tier is cheap enough that I do not think about it.

It is one of those tools that does its job and then gets out of the way. That is rarer than it sounds.

Frequently asked questions

Is Resend free? Yes. As of June 2026, the free plan includes 3,000 emails per month. That covers most small applications, including transactional messages and a modest newsletter.

Is Resend reliable? In production use for Flow, Resend has been reliable. Deliverability is strong, the API has not had unexpected downtime, and the status page is transparent about incidents. It is a newer platform than SendGrid or AWS SES, so long-term track record is still building.

How does Resend compare to SendGrid? Resend has a cleaner API, simpler pricing, and native React Email support. SendGrid has more enterprise features, a larger template library, and deeper marketing automation. Most developers prefer Resend for transactional email. Marketing teams often prefer SendGrid for its broader campaign tools.

What is React Email? React Email is an open-source library for building email templates with React components. It renders to cross-client HTML and includes a local preview server. Resend's founders created React Email, and the two tools integrate directly.

Does Resend handle newsletters? Yes. Resend supports broadcast email for newsletters and marketing. The feature works well for moderate lists. Heavy email marketers may eventually want a dedicated newsletter platform or marketing automation tool.

Can I use Resend without React? Absolutely. Resend accepts plain text and HTML strings. React Email is an optional integration for teams already using React.

Related reading

• Resend vs SendGrid: developer email, compared
• Best transactional email API for startups in 2026
• How Resend works for entrepreneurs and small teams
• Why I built Flow

My verdict

Resend is not the only email platform that works. SendGrid and Mailgun send email reliably. So do Postmark and AWS SES.

What Resend offers is a better experience for the developer who has to build and maintain the integration. The API is clean, the pricing is honest, the deliverability is good, and the React Email integration removes one of the worst parts of the job: wrestling with table-based HTML templates in a separate system.

If you are tired of email platforms that feel like legacy software with a modern skin, Resend is worth the switch. Start on the free tier, send real traffic, and see if it stays out of your way the way it has for me.