Resend Review 2026: The Best API Here, and Barely Anyone Has Reviewed It

The short version

Resend has the best developer experience in this category and almost no independent evidence behind it. Both halves of that sentence matter.

The good half is easy to demonstrate. SMTP is four values: host smtp.resend.com, any of five ports, username the literal string resend, password your API key. The API is one endpoint. There are official SDKs for nine languages, 19 webhook event types, a published OpenAPI spec and a CLI. And the MCP story is the strongest we have found anywhere on this site: a hosted remote server at mcp.resend.com/mcp with browser OAuth, plus an open-source local package, plus three separate changelog entries including support for the newest protocol specification. Mailgun’s MCP is local-only. AWS does not have one for SES at all.

The thin half is the review record. Resend has no Capterra listing. Its G2 page holds ten reviews. We read all ten, which took a few minutes, and they are warm and consistent. They are also ten reviews, nine of them from small businesses, for a company that says “more than 200,000 developers have signed up”. Everywhere else on this site we count themes across 100 to 200 rows. Here there is nothing to count.

One more thing a production team should know before committing. Resend’s own documentation states: “Currently, there’s no versioning system in place.” No version in the URL, no version header, no deprecation window published. For a dependency that sends your password resets, that is a real risk and it is stated honestly rather than hidden.

A warning about the evidence on this page

Every other review on this site rests on a counted read of 100 to 206 third-party review rows, and we publish frequencies like “named in at least 42 of 200 rows”. That method cannot run here.

Resend has no Capterra product page. We searched and the results returned unrelated products. Its G2 listing carries ten reviews and displays no category sub-scores. So on this fiche the user-sentiment evidence is one order of magnitude thinner than on any other, and two of our six scores, support and deliverability, rest on almost nothing at all. We have scored those conservatively toward the middle rather than reading a small warm sample as strong evidence, and we say so again in the ratings section.

This is not a criticism of Resend. It is what a three-year-old company looks like. It is a reason to treat a high score here differently from a high score on a platform with 753 reviews.

SMTP settings

Snapshot

What Resend does well

The best MCP implementation on this site, and it is not close

We have now checked MCP support on every platform in this project, and Resend is at the top of it. Three things put it there.

First, there is a hosted remote server at mcp.resend.com/mcp with browser-based OAuth, so there is nothing to install and no API key sitting in a config file. Mailgun’s official MCP is local stdio only, with the key in an environment variable. AWS has no SES server at all beyond a sample marked not for production. SMTP2GO has a remote server but needs an npx wrapper for Claude Desktop because of a custom header.

Second, the exposed surface is not a token gesture. It covers emails including batch and scheduling, received emails and attachments, templates with publish and duplicate, contacts, segments and subscriptions, broadcasts, automations, domains, API keys, webhooks, logs, and the visual editor.

Third, and this is the part that tells you it is maintained rather than launched: there are three separate official changelog entries for it, including one for supporting the 2026-07-28 protocol specification. That is a product line, not a demo.

Setup that people describe in a sentence

Seven of the ten reviews say some version of the same thing. “The API is straightforward, the documentation is clear, and sending emails for verification, notifications, or authentication flows takes very little setup.” “Super easy to set up and start sending emails without having to actually touch the Resend website; I just used command line interfaces.” “Simple, fast, and developer-friendly, it just works without fighting the tool.”

One reviewer describes it replacing two other products at once: “Simplifies my workflow by replacing multiple tools like Mailgun and Mailtrap, while offering a much better user experience.”

Thirty days of log retention on the free plan

This is a quiet, real differentiator and it is easiest to see against its closest competitor. Resend gives 30 days of retention on every plan including the free one. Mailgun gives one day on Free and Basic, five days on Foundation, and only reaches 30 days at Scale, which is $90 a month. SMTP2GO gives five days free and about a month paid.

When someone asks whether an email went out three weeks ago, retention is the whole answer, and Resend is the only provider in this family that gives you a month of it for nothing.

Nine official SDKs and nineteen webhook events

Node.js, PHP, Laravel, Python, Ruby, Go, Java, Rust and .NET, with an OpenAPI specification and a command-line tool on top. Mailgun publishes six SDKs. The webhook coverage is similarly wide: 19 event types where Mailgun publishes 8, including granular states like email.delivery_delayed, email.scheduled and email.suppressed that most providers collapse.

React Email, which is why some of you already know the name

Resend maintains React Email as open source, reported at 300,000 weekly npm downloads and 14,000 GitHub stars. It is a genuine piece of ecosystem infrastructure that exists independently of the paid product, and it is a large part of why a three-year-old company has the mindshare it does. The measured search data agrees: react email draws 1,300 searches a month in the United States on its own.

Where Resend falls short

There is no API versioning at all

Resend’s documentation says it plainly: “Currently, there’s no versioning system in place.” No version segment in the URL, no version header, and no published deprecation policy.

Compare with what the rest of this family does. Amazon SES runs v1 and v2 side by side with different documented limits. SendGrid is on v3 with the version in the path. Mailgun’s send endpoint carries v3 in the URL. GoHighLevel dates its API version 2023-02-21. Versioning is how a provider promises not to break your integration without warning, and Resend has not made that promise yet. We would want it before routing authentication email through them at scale.

Ten reviews is not a track record

No Capterra listing exists. G2 holds ten reviews. Nine of the ten reviewers are categorised as small business and one as enterprise. There is no independent inbox placement figure, because Resend has never been in the seedlist panel and that panel has since been discontinued.

So on the two questions that most determine whether a relay is any good in practice, does the mail arrive and will someone help when it does not, the evidence available here is a handful of anecdotes. We have scored accordingly rather than generously.

No SMTP debug logs

Stated in the documentation: “We currently don’t provide SMTP server logs for debugging.” Delivered mail appears in the emails table, so you can see outcomes, but if an SMTP conversation fails you are diagnosing it from your side only. Mailgun exposes around 25 X-Mailgun headers for controlling and instrumenting SMTP behaviour. Resend exposes an idempotency key and standard headers.

Ten requests per second, shared across your whole team

The published rate limit is 10 requests per second per team, and the important word is team: it applies “across all API keys associated with your team”, so separate keys for separate services do not buy you separate headroom. It is raisable on request for trusted senders.

Ten a second is 36,000 an hour, which is enough for most applications and is not enough for a bulk send that fans out fast. Note that this is still better documented than SendGrid or Mailgun, neither of which publishes a number at all.

No published EU region

Mailgun publishes a full EU stack, smtp.eu.mailgun.org and api.eu.mailgun.net, with the commitment that “Message data never leaves the region in which it is processed.” SendGrid publishes an EU API host. Amazon SES has five European regions with SMTP endpoints. Resend documents neither an EU SMTP hostname nor a regional API base. It holds SOC 2 Type II and states GDPR compliance, which is not the same thing as data residency.

The price is not the cheap one, and reviewers say so

Three of the ten reviews raise pricing, which is a high proportion of a small sample: “Could be cheaper”, “For high-volume scenarios, pricing may not always be the most competitive option compared to older providers with bulk discounts”, and “Resends pricing is not as competitive as other similar services available.”

The arithmetic supports them at volume. Resend’s overage is $0.90 per 1,000. Amazon SES charges $0.10 per 1,000 without a plan, nine times less. Below about 100,000 a month the difference is small change; above a few million it is a budget line.

A hard cap of 100 emails a day on the free plan

The free plan is 3,000 a month, but with a 100 a day ceiling on top, so you cannot use the monthly allowance in a burst. One reviewer names it: “The free tier is good for development and small projects, but larger applications can consume the limits fairly quickly.” SendGrid’s free tier is also 100 a day, and SMTP2GO’s is 200 a day within a 1,000 a month allowance.

What real users actually say

What the search data says that the reviews cannot

With a ten-review corpus, the most reliable evidence about Resend’s trajectory is not user sentiment but demand. Measured United States volumes, comparing August 2025 with July 2026:

Every Resend query we measured is climbing steeply, and none of the incumbents in this category shows anything like it. This is the fastest-growing brand in our whole dataset. It is also why the review record is thin: the users arrived recently and have not written anything yet.

Ratings breakdown

Ease of use, 9.0. The highest on this site. Four SMTP values, one API endpoint, nine SDKs, and seven of ten reviewers naming setup speed unprompted. Held below 9.5 by DNS onboarding two reviewers found thin and a template editor that is not fully WYSIWYG.

Automation, 5.0. The highest automation score of any pure relay here, because Resend actually has contacts, segments, broadcasts and automations, billed at $0.0015 per run beyond 10,000 free. Nowhere near a marketing platform, well ahead of SES at 3.5 or SMTP2GO at 3.0.

Deliverability, 6.5. Scored on almost no evidence, and deliberately mid-range for that reason. No seedlist figure, no Capterra corpus, ten G2 reviews of which one mentions occasional delay and none complains about placement. SOC 2 Type II and a $30 dedicated IP option exist. We do not award points for an absence of complaints from ten people.

Support, 7.0. One enterprise reviewer calls it exceptional and nobody criticises it. That is a warm signal from a sample too small to carry a high score, so this sits above the middle rather than near the top.

Pricing value, 7.5. A genuinely useful free plan with 30 days of retention, $20 for 50,000, and a $30 dedicated IP. Held down by a $0.90 per 1,000 overage that is nine times Amazon SES’s rate, the 100 a day free cap, and three of ten reviewers raising cost.

API and MCP, 9.5. Joint highest on this site with Klaviyo. A hosted remote MCP server with OAuth plus an open source local one, nine SDKs, 19 webhook events, an OpenAPI spec, a CLI, a published rate limit and an idempotency header. Held below 10 by the complete absence of API versioning and by no SMTP debug logs.

Who should use Resend, and who should not

Third-party validation

This is the emptiest validation table on the site, and the emptiness is the point. Compare it with SMTP2GO, doing a similar job with a 4.9 average across 178 Capterra reviews and 226 on G2, from a twenty-year-old company. Or SendGrid, with 753 Capterra reviews across fifteen years including seven describing account suspensions. Resend has a 4.8 from ten people.

A 4.8 from ten is not evidence that Resend is worse than those platforms. It is evidence that we do not know yet, and a buyer should price that uncertainty rather than reading a high average as a high confidence.

Top 3 alternatives

Continue reading

• Resend SMTP settings, host, ports and the literal username
• Resend API, endpoints, rate limits and the MCP servers
• Resend pricing, tiers, overage and add-ons
• Resend integrations
• Mailgun review
• Postmark review

Frequently asked questions

What is Resend email?

Resend is a transactional and marketing email platform aimed at developers, founded in 2022 and launched as a product in 2023. It came out of Y Combinator’s Winter 2023 batch and raised an $18 million Series A led by Andreessen Horowitz in December 2024. Its homepage describes it as “Email for developers”, and it also maintains React Email as an open source project.

What are the Resend SMTP settings?

Host smtp.resend.com. Use port 465 or 2465 for implicit SSL, or 25, 587 or 2587 for STARTTLS. The username is the literal string resend and the password is your API key, the one starting with re_. You need a verified domain first. Note that Resend does not provide SMTP server logs for debugging, and does not publish an EU regional SMTP hostname.

How does the Resend API work?

Send with POST to https://api.resend.com/emails using a Bearer token. Two details catch people out: every request must carry a User-Agent header or it is rejected with a 403, and the default rate limit is 10 requests per second per team, shared across all your API keys rather than allocated per key. Messages are capped at 40 MB including base64-encoded attachments. There is currently no API versioning system.

How much does Resend cost?

Free is 3,000 emails a month with a 100 a day cap and three domains. Pro is $20 a month for 50,000 emails and ten domains. Scale is $90 a month for 100,000 emails and a thousand domains. Overage on paid plans is $0.90 per 1,000, and a dedicated IP is $30 a month on Scale and above. Every plan, including Free, gets 30 days of log retention.

Resend vs SendGrid: which should I use?

Resend if developer experience and MCP support matter and you are building something new; it scores 7.4 with us against SendGrid’s 5.7. SendGrid if you need an EU API region, more than 50 recipients per message, or the reassurance of fifteen years of operation. The counterweight is that seven of the 200 SendGrid reviews we read describe accounts cut off without notice, and SendGrid’s customer service sub-score is 3.7.

Does Resend have an MCP server?

Yes, and it is the best implementation we have found on this site. There is a hosted remote server at mcp.resend.com/mcp authenticated with browser OAuth, requiring no installation, plus an open source local package published on npm. It exposes emails, received mail, templates, contacts, segments, broadcasts, automations, domains, webhooks, API keys and logs, and it is documented for Claude, Cursor, Codex, GitHub Copilot, Windsurf and Warp.

What is React Email?

An open source library maintained by Resend for building email templates as React components, reported at 300,000 weekly npm downloads and 14,000 GitHub stars. It works with any sending provider, not only Resend, and it draws 1,300 US searches a month in its own right. For React teams it is the most natural reason to end up on Resend.

Is Resend reliable enough for production?

The honest answer is that there is not much evidence either way yet. Resend holds SOC 2 Type II, offers a 99.99 percent uptime SLA on Enterprise, and states more than 200,000 developer signups. Against that: no Capterra listing, ten G2 reviews, no independent inbox placement measurement, and no API versioning. For a new project that is a fine risk. For migrating a critical pipeline, weigh it deliberately.

Changelog