Resend vs Postmark

Quick verdict

Resend is the modern developer-first email API: React Email, a clean REST surface, multi-region sending, inbound + marketing products, and a free tier that actually covers most MVPs (3,000 emails/month, 100/day). Postmark is the long-running transactional specialist: own MTAs and IP pools, Message Streams that isolate broadcast from password-resets, 45-day full message retention, public time-to-inbox stats, and human support on every plan.

Pick Resend when you want React/Next-native authoring, a usable free tier, and lower mid-volume cost. Pick Postmark when time-to-inbox, stream isolation, long activity logs, and ops-grade support matter more than the latest DX polish. Both ship transactional mail reliably for serious products — the gap is philosophy, not “does email work.”

Feature and pricing snapshot

What each product is in 2026

Resend

Resend (YC W23) sells email as a developer product: send via REST or SMTP, author with React Email, manage domains, webhooks, inbound, and — separately — marketing audiences/broadcasts and automations. Pricing is volume buckets for transactional mail plus contact-based marketing plans.

Under the hood, independent write-ups and HN discussion have long described Resend as sitting on Amazon SES for delivery — a modern control plane and UI on top of commodity MTA capacity rather than a from-scratch mail plant. That architecture is not automatically “worse,” but it shapes latency, control during ISP drama, and how you reason about reputation.

React Email is the real moat for frontend teams: components, preview server, and tight Resend integration instead of hand-rolled table HTML or vendor Mustache clones. The package is actively maintained (v5/v6 releases, changelog, GitHub issues for React 19 edge cases).

Postmark

Postmark has focused on application email since ~2009–2010 and is part of the ActiveCampaign family (AC PM LLC). The product pitch is still deliverability: carefully managed shared IPs, optional dedicated IPs, Message Streams that put bulk/broadcast traffic on separate infrastructure from transactional, and deep activity tooling.

They publish live time-to-inbox metrics for major providers — rare transparency in this category. Official SDKs (including Node postmark.js under ActiveCampaign) and long-standing docs cover send, templates, inbound, and webhooks.

Postmark’s own Resend comparison page argues for ownership of the MTA stack (no extra SES hop), richer inbound payloads, longer default retention, and support depth. Treat vendor pages as advocacy — then check Knock latency numbers and Reddit/HN for balance.

Pricing and real cost (TCO)

Numbers below are from official pricing pages as of research date; always re-check calculators before signing.

Resend transactional (official)

• Free: $0 — 3,000 emails/mo, 100/day, no overage, 1 domain, 30-day retention.
• Pro: $20 / 50,000 or $35 / 100,000; overage $0.90 per 1,000.
• Scale: $90 / 100k, $160 / 200k, $350 / 500k, $650 / 1M, $825 / 1.5M, $1,150 / 2.5M; overages step down (~$0.90 → $0.46 per 1k).
• Enterprise: custom (volume, SSO, SLA, flexible retention).
• Dedicated IP: $30/mo on Scale when sending >3,000/day; warmup/monitoring included per docs.
• Marketing: contact-based (Free 1k contacts; Pro Marketing from $40/5k contacts, not email count).
• Automations: 10k runs included; paid overage $0.0015/run.

Postmark (official)

• Free Developer: 100 emails/mo, no overages, no expiry — for tests and tiny side projects.
• Basic: $15 / 10,000; extra $1.80 / 1,000; ~4 users, 5 servers/domains, stream caps.
• Pro: $16.50 / 10,000; extra $1.30 / 1,000; inbound; more servers/domains; retention add-on eligible.
• Platform: $18 / 10,000; extra $1.20 / 1,000; unlimited users/servers/streams/domains.
• Dedicated IPs: from $50/IP/mo; typically 300k+ emails/mo; Pro+.
• Retention add-on: from $5/mo; custom 7–365 days (default 45 days full content).
• DMARC monitoring: from $14/domain/mo via DMARC Digests.

Rough TCO scenarios (illustrative)

Independent roundups commonly say: cheapest raw sends = SES; best free startup UX = Resend; premium deliverability packaging = Postmark. Postmark still offers bootstrapped credit ($75) if you qualify — check their FAQ, not third-party blogs alone.

Community sentiment (Reddit / HN)

Resend praise: Day-0 sending after domain verification; free tier that covers bootstrapped apps; UI and DX beat older ESPs; natural fit next to Next.js/Vercel. Launch HN and follow-ups framed it as the React-era answer to SendGrid/Mailgun/Postmark UX debt.

Resend complaints: Slow confirmation emails reported by some (especially free tier / geo anecdotes); “bugs and latency” vs Postmark; hard account suspensions after deliverability review with weak human escalation stories; HN skepticism that it is “SES with a UI.”

Postmark praise: Still the default recommendation when people care about features and deliverability; smooth account approval for some vs pickier ESPs; years of “just works” for SaaS transactional mail. Knock’s public benchmarks reinforce the “fast API acceptance” reputation.

Postmark complaints: Free 100 → paid $15 cliff for anything real; occasional “marked delivered but missing” reports; pickiness with certain VPS/source IP ranges; mixed HN sentiment after ActiveCampaign-era changes (“support used to be better”).

Postmark is my top choice for features AND deliverability. Resend is only good at UI… but it is so slow and has so many bugs that I could not use it anymore. — paraphrased from r/SideProject thread

Neither community is unanimous. Treat threads as risk surface, not scoreboards: test with your domains, ISPs (Gmail/Microsoft), and content types.

When Resend wins

• React/Next email as code — React Email + first-party integration beats Mustachio for TS monorepos.
• MVP / indie volume under 3k/mo — Free tier is genuinely useful; Postmark free is a sandbox.
• 50k-class volume on a budget — Pro $20 for 50k is hard for Postmark overages to beat.
• You want SOC 2 Type II as a product checkbox — Resend publishes Type II clearly.
• Marketing + transactional under one modern dashboard — audiences/broadcasts/automations on the same account model.
• Scheduled sends and “modern API surface” — vendor and third-party comparisons call out scheduling and DX polish.

When Postmark wins

• Password resets / OTPs as product-critical path — public TTI stats + own MTA narrative + streams isolation.
• You mix newsletters and app mail — Broadcast Message Streams keep reputation separated by design.
• Support tickets that need humans quickly — Postmark markets chat/phone culture on all plans; Resend Slack is Scale+.
• Debugging last month’s missing email — 45-day full content retention vs Resend’s 30-day window (and older vendor claims of even shorter Resend retention are outdated — use 30 vs 45 as of current docs).
• Inbound as a single webhook payload — body + attachments in one POST simplifies some backends vs multi-fetch inbound designs.
• API acceptance latency under load — Knock: ~4 ms p50 vs ~98 ms for Resend (not the same as mailbox TTI, but real).
• ~10k emails/mo steady state — Basic $15 often undercuts Resend’s Pro bucket jump.

Risks and failure modes

• Shared IP reputation: Both use shared pools by default. Bad neighbors or your own spam complaints hurt. Dedicated IPs have volume gates and cost.
• Warmup and sudden volume: Blasting 200k–300k from a cold domain/IP invites filters regardless of vendor.
• Architecture dependency (Resend): If delivery rides SES, SES incidents and pool dynamics matter; you gain DX, not full MTA control.
• Account review / bans (Resend anecdotes): Deliverability audits can kill sending — keep domains clean, authenticate, and avoid “test spam.”
• Pricing cliffs: Postmark free is tiny; Resend free has a hard daily cap. Mis-model spikes and you ship broken auth email.
• Compliance gaps: Resend’s SOC 2 Type II is a clear enterprise story; Postmark’s posture is GDPR/DPA + DC-level SOC — fine for many teams, painful if procurement demands a product SOC 2 report only.
• Template lock-in: React Email components vs Postmark server templates — migrations are code work either way.
• Measuring the wrong metric: Fast API accept ≠ inbox placement. Use seed tests, ISP postmasters, and production bounce/complaint rates.

Recommendation by profile

FAQ

Is Resend just Amazon SES with a UI?
Resend provides the API, dashboard, React Email, inbound, marketing features, and support layer; delivery infrastructure discussions (including Postmark’s comparison and HN comments) commonly point to SES under the hood. You still pay for product surface, not raw SES pricing.

Who has better deliverability?
Postmark’s brand and public TTI page center on deliverability; many Reddit threads still recommend Postmark when that is the only priority. Resend deliverability is “good enough” for huge numbers of apps but has more mixed anecdotes. Measure with your domains.

Which is cheaper at 10k emails/month?
Often Postmark Basic at $15. Resend Free stops at 3k/100-day; above that you typically land on Pro $20 for a 50k bucket — fine if you will grow into it, odd if you sit at 10k forever.

Which is cheaper at 50k?
Usually Resend Pro $20, because Postmark overages after 10k add up quickly at Basic/Pro rates.

Does Postmark do marketing email?
Yes via Broadcast Message Streams on separate infrastructure — not the old “transactional only” story.

Can I use React Email with Postmark?
You can render HTML anywhere and send via any API. First-class DX and docs skew toward Resend.

How long are messages stored?
Resend: 30 days standard (Enterprise flexible). Postmark: 45 days full content by default, extendable with add-on.

SOC 2?
Resend: Type II. Postmark: strong GDPR/DPA story; SOC reports historically at infrastructure/data-center level — confirm current status with sales if enterprise procurement is strict.

Sources

Research file: research_cache/resend-vs-postmark_sources.json — 145 unique URLs (official sites, pricing, docs, GitHub, Reddit, HN, independent reviews, benchmarks, security pages). Citations in this article map to source ids in that file. No invented pricing: figures tracked to vendor pages and dated reviews.

Bottom line

Resend is the default for 2026 React/Next builders who want to ship auth and product email this afternoon without a $15 minimum or Mustache-era templates — and who will stay under free limits or live happily on Pro $20–$35.

Postmark remains the specialist when email is infrastructure, not a weekend integration: streams, retention, public TTI, inbound payloads, and a support culture built around “why didn’t this hit the inbox.”

If you are unsure: put both behind a thin mailer interface, send 1–2 weeks of real password-reset and receipt traffic to seed addresses at Gmail/Microsoft/Apple, and keep the vendor with better placement and fewer support fires — not the prettier dashboard alone.