Email · Written evaluation

Resend

Developer email infrastructure for transactional sending, receiving and delivery event handling.

Plan at a glance

Plans & sources ↓
Starting plan
Free · Free /month
Includes
See the plan limits below.
Limits & source scope

Transactional sending and receiving share the allowance; marketing contacts and optional add-ons are separate, and Free has a daily cap.

Selected source read 2026-10-09

Official sources read 9 October 2026. The evaluation below is editorial judgement based on documentation; no hands-on product test was performed.

Browse & compare tools →

Shared inboxes: a separate limit to check

Resend’s self-serve plans include three inboxes. Their incoming and outgoing mail uses the transactional quota; marketing contacts remain separate. Free cannot add a fourth inbox. Read the announcement and allowance boundaries.

Selected documentation checked 30 October 2026. No live email or agent test; earlier prices below keep their original dates.

Research scope & testing evidence

Our evaluation

Resend is a focused choice for application email when a developer wants sending and event handling in the same workflow. The useful unit of evaluation is a complete notification lifecycle, not a successful API response: the application needs to react when an address bounces or its webhook endpoint misses an event. Transactional and marketing pricing are separate, so an attractive sending allowance should not be used to estimate a newsletter business. The free daily limit also matters more than the monthly total for a burst of new signups. Receiving email consumes the transactional allowance too. For a small product, good domain authentication, webhook verification and recoverable processing will matter more than buying a larger quota. Documentation alone cannot establish inbox placement for your audience.

Fit and limits

Fit and limits

Consider it for

Developers building product notifications, receipts and account emails with delivery events handled in code.

Check before committing

Transactional sending and receiving share the allowance; marketing contacts and optional add-ons are separate, and Free has a daily cap.

What the documentation confirms

What the documentation confirms

  • Send transactional messages through an API or SMTP.
  • Receive delivery, bounce and other email events through webhooks.
  • Observe and replay webhooks through the dashboard or API.

Selected official documents read 9 October 2026. Access can depend on plan, region and account.

Price and billing scope

Pricing checked

Official pricing ↗

USD · Source read

Transactional sending and receiving email plans; marketing email prices are separate.

  1. FreeFree /month

    3,000 emails/month, 100/day and 3 domains.

  2. Pro$20 /month

    50,000 emails/month and 10 domains; extra emails $0.90/1,000.

  3. Scale$90 /month

    100,000 emails/month and 1,000 domains; extra emails $0.90/1,000.

  4. EnterpriseContact sales

    Custom volume and contract.

Automation runs, dedicated IPs, domains and other add-ons can cost extra.

Recorded editorial criteria

Recorded editorial criteria

These are the previously recorded editorial opinions used in the directory. They have no individually recorded assessment date and were not rescored during this documentation refresh. They are not product-test results.

Historical recorded opinion · equal five-criterion rubric
Functionality9/10
Pricing value9/10
Ease of use9/10
Reliability8/10
Founder fit9/10
How criteria are presented →

Try one complete task

Send a staging signup confirmation to controlled addresses, verify the webhook signature, record delivery and bounce events, then replay an event without creating a duplicate notification.

Create a trial worksheet →

Compare requirements

Edited by Clinton Feyisitan · Evidence policy · Suggest a correction