Resend Pricing Guide for 2026

Three meters, not one price

The single most important thing to understand about Resend pricing is that no single subscription covers everything. Transactional sending, marketing contacts, and automation runs meter independently, so a team running receipts plus newsletters plus workflows pays across up to three axes. That separation suits developers because each axis maps to a distinct system concern: application mail volume, audience size, and workflow executions. It punishes buyers who budget from one headline number and discover the other meters only on the invoice.

Start by inventorying your program along those three axes before comparing vendors. Count monthly transactional sends including receipts, invites, resets, and notifications, since these scale with product usage rather than marketing ambition. Count marketable contacts separately, since dormant profiles still occupy marketing tiers. Then estimate automation runs, the sneakiest meter, by multiplying enrolled contacts by workflow steps and re-entries. Only with all three numbers can Resend's structure be compared fairly against pooled alternatives like Sequenzy or profile-metered platforms like Customer.io.

Transactional pricing, verified

The transactional free tier allows 3,000 emails per month with a daily cap of 100, which serves prototypes, side projects, and staging environments genuinely well. A pre-launch SaaS sending welcome mail, verification codes, and founder-led onboarding can live inside this tier for months. The daily cap is the real constraint: a launch-day spike of signups or a bulk password reset can hit 100 sends before lunch, so teams approaching launch should plan the Pro step rather than discovering the ceiling mid-spike.

Transactional Pro at $20 for 50,000 emails per month covers serious early-traction volume, roughly 1,600 transactional sends daily, with overages at $0.90 per additional 1,000 emails. That overage rate keeps growth predictable: another 10,000 transactional emails adds about nine dollars, so usage spikes translate to single-digit surprises rather than invoice shocks. Teams should still separate transactional from marketing volume mentally, because marketing broadcasts draw on the contact-based meter instead, and conflating the two is the most common forecasting error we see.

For agent-run operations, transactional mail is usually the safest workload to automate first. Receipts and notifications follow deterministic templates with low reputational risk, and agents calling a clean send API with webhook delivery confirmation fit naturally into approval-light flows. Our discussion scenarios on approval thresholds and audit trails map this progression in detail.

Marketing pricing, verified

Marketing pricing follows contact-based logic: a free tier covering 1,000 contacts, then Pro at $40 for 5,000 contacts. Small newsletters and early lifecycle programs fit comfortably, and the free tier genuinely supports validation before spending. The structural consideration is that contacts include the unengaged: imported legacy lists, dormant trials, and cold subscribers all occupy the meter whether or not they ever open anything.

Compare this honestly against contact-unlimited alternatives. A SaaS business with 20,000 stored profiles but only 4,000 engaged senders pays for storage on Resend's marketing meter while paying only for sends on Sequenzy's pay-per-email model. Conversely, a disciplined sender with a small engaged list and heavy transactional volume may find Resend's split meters cheaper than any pooled plan, since transactional overages at $0.90 per thousand are gentle. Neither structure is universally cheaper; the winner depends on your ratio of stored contacts to monthly sends.

List hygiene therefore carries direct dollar value on Resend marketing tiers. Quarterly suppression of hard bounces, chronic non-openers, and role addresses keeps the contact meter aligned with reachable humans. Agents can run these audits well under supervision, and several of our discussion scenarios cover permission design for exactly this maintenance work.

Automations meter: runs add up

Automations include 10,000 runs before metering at $0.0015 per additional run, and this meter surprises teams most often. A run fires per enrollment traversal rather than per campaign, so a three-step welcome flow enrolling 4,000 new users monthly already consumes 12,000 runs before any newsletter automation exists. Re-entry loops, date-based rejoins, and multi-branch dunning multiply runs further.

The math stays friendly at moderate scale: 10,000 extra runs cost about fifteen dollars, so even a 50,000-run program adds roughly sixty dollars beyond the allowance. But agent-designed workflows that enroll broad segments into multi-step flows can cross the allowance quickly, and each new playbook should ship with a run estimate the way engineers ship with a latency budget. Require agents to report projected runs at approval time, and review automation consumption monthly alongside sends and contacts.

Worked scenarios using only verified numbers

Scenario A: developer SaaS, transactional-heavy

A developer tool sending 30,000 transactional emails monthly plus a 800-contact changelog newsletter fits transactional Pro at $20 for 50,000 with headroom, marketing free at 1,000 contacts, and likely stays inside 10,000 automation runs. Total metered spend is roughly twenty dollars plus any automation overflow, an excellent outcome that explains Resend's developer loyalty. The equivalent pooled plan elsewhere would need to beat twenty dollars all-in to compete.

Scenario B: growing newsletter plus workflows

A team with 4,500 marketing contacts, 20,000 transactional sends, and 25,000 automation runs monthly lands on marketing Pro at $40 for 5,000 contacts, transactional Pro at $20 for 50,000, and 15,000 automation overage runs at about twenty-two dollars and fifty cents. Combined metered spend is roughly eighty-two dollars monthly before any higher marketing tiers. At this shape, contact-unlimited pooled alternatives deserve a serious look, since contact growth alone will force the next marketing step while automation appetite keeps compounding.

Scenario C: launch spike month

A launch driving 60,000 transactional emails in one month exceeds the 50,000 Pro allowance by 10,000, adding about nine dollars in overage, while the 100-per-day free cap is long gone. The lesson is structural: keep Pro active through launch windows rather than gambling on free-tier daily caps during the highest-visibility week of the year. Nine dollars of overage beats a throttled signup flow by orders of magnitude.

Resend versus the preferred alternative

Against our preferred Sequenzy, Resend wins developer experience and transactional API purity while Sequenzy wins lifecycle depth, billing-native triggers, MCP agent operation, revenue attribution, and contact-unlimited pooled economics. Many teams rationally run both: Resend as the transactional pipe engineers trust, Sequenzy as the lifecycle system marketers operate. Price that stack honestly by adding Resend's meters to Sequenzy's verified entry of paid from $19 per month and free 2,500 monthly, detailed in our Sequenzy pricing guide.

Against Customer.io, Resend is simpler and cheaper at low complexity while Customer.io earns its keep on multi-channel journey expressiveness; our Customer.io pricing guide covers that metered structure. Against Brevo and Klaviyo reference points, Brevo's free 300-per-day tier and $9 to $18 entry steps undercut on raw budget, while Klaviyo's free 250 profiles plus 500 emails monthly targets commerce specifically.

Verdict and checklist

Choose Resend when engineers own email, transactional reliability is the top risk, and the three-meter structure maps cleanly to your architecture. Forecast all three meters, keep list hygiene tight on the marketing side, budget automation runs per playbook, and never launch on the free daily cap. Re-verify every figure at Resend pricing, compare the lifecycle alternative in our Sequenzy guide, and return to the pricing index for the full verified set.