head to head
Cloudflare Email Service vs Resend
Sending at $0.35 per 1,000 from the edge, still in beta, against a settled API at $20/mo for 50,000.
What matters for early-stage startups
At an early stage the deciding factors are what the free tier actually covers, what the first paid invoice looks like, and how much of a founding engineer's week the setup costs. Feature depth that only matters at a million sends a month is noise until it is not.
| Priority | Cloudflare Email Service | Resend |
|---|---|---|
| Free tier | Email Routing free; Email Workers on Workers Free plan | 3,000/mo permanent, capped at 100/day, one domain |
| Best published rate per 1,000 | Tiers not published in comparable form | $0.35 |
| Starts at | Sending: $0.35 per 1,000 messages (Workers Paid required, $5/mo) | $20/mo for 50,000 emails |
| DX score | 8/10 | 8/10 |
| Deliverability | Free Email Routing forwards reliably and inherits Cloudflare's operational maturity. The new Sending API has no track record; treat any deliverability claim as unverified until public history appears. | Acceptable, but the deliverability track record is shorter than Postmark or SendGrid. Independent inbox-placement studies vary. Dedicated IPs are available on higher tiers. |
| Operating since | Not published | 2023 |
| Scheduling | No | Yes |
| SDKs | node | node, python, go, ruby, php, rust, java, elixir, cli |
| Webhooks | No | Yes |
For a pre-revenue or early-revenue team running a waitlist, a launch announcement, onboarding email, and the first transactional sends, Resend takes every priority that separates them here (scheduling, SDK breadth, and webhook coverage), while Cloudflare Email Service matches it on the rest. On free tier, Cloudflare Email Service offers Email Routing free; Email Workers on Workers Free plan against 3,000/mo permanent, capped at 100/day, one domain from Resend. That ordering reflects this audience. Weigh the same table differently and the answer changes.
Side by side
| Feature | Cloudflare Email Service | Resend |
|---|---|---|
| Free tier | Email Routing free; Email Workers on Workers Free plan | 3,000/mo permanent, capped at 100/day, one domain |
| Starts at | Sending: $0.35 per 1,000 messages (Workers Paid required, $5/mo) | $20/mo for 50,000 emails |
| DX score | 8/10 | 8/10 |
| Deliverability | Free Email Routing forwards reliably and inherits Cloudflare's operational maturity. The new Sending API has no track record; treat any deliverability claim as unverified until public history appears. | Acceptable, but the deliverability track record is shorter than Postmark or SendGrid. Independent inbox-placement studies vary. Dedicated IPs are available on higher tiers. |
| SDKs | node | node, python, go, ruby, php, rust, java, elixir, cli |
| Webhooks | No | Yes |
| Tagline | Free routing, programmable inbound via Workers, sending in beta. | Email API tightly coupled to React Email. |
| Pricing model | pay-as-you-go | tiered |
| API | Yes | Yes |
| SMTP | No | Yes |
| Templates | none | react-email |
| React Email | No | Yes |
| Inbound | Yes | Yes |
| Multi-tenant | Yes | No |
| Idempotency | No | Yes |
| Dedicated IP | No | Yes |
| Best for | Domains already on Cloudflare that want free routing, programmable inbound, and a cheap sending API in one place. | Early-stage React or Next.js product teams sending under 50k/mo. |
Cloudflare Email Service
pros
- ›Email Routing is free, including catch-all addresses and forwarding to any inbox
- ›Email Workers let you process inbound email in TypeScript with no extra infrastructure
- ›Sending priced at $0.35 per 1,000 (about a third of most managed providers)
- ›Native fit when DNS, Workers, and KV/D1 already live on Cloudflare
- ›No separate API keys; auth is via Cloudflare API tokens
cons
- ›Email Sending is in public beta; no deliverability history yet
- ›No SMTP relay; everything routes through Workers or the REST API
- ›Templates and event-log debugging are minimal compared to Postmark or Mailgun
- ›Tightly coupled to the Cloudflare ecosystem; not portable
- ›Best-of-breed providers will outpace it on pure sending features for some time
Resend
pros
- ›Idiomatic SDKs across major languages
- ›React Email integration is the smoothest of any provider
- ›Idempotency keys supported
- ›Clean dashboard and event log
cons
- ›Volume pricing is significantly higher than AWS SES at large volumes
- ›Founded 2023, so deliverability track record and incident history are still building
- ›No drag-and-drop template editor; non-React stacks get a thinner experience
- ›Free tier is capped at 100 sends a day, so a 3,000/mo allowance cannot absorb a launch spike
- ›January 2024 breach exposed email metadata, contacts, and encrypted API tokens for all users; message bodies were not reached
- ›Status page logged roughly ten incidents in the three weeks to 2026-08-01, mostly outside the sending path: dashboard, webhooks, domain verification, and automations
- ›Single-region historically; multi-region setup is newer
- ›Smaller support footprint than Twilio SendGrid or Sinch Mailgun