head to head
Cloudflare Email Service vs Resend
Cheap-and-coupled-to-the-edge versus React-Email-coupled developer wrapper.
Side by side
| Feature | Cloudflare Email Service | Resend |
|---|---|---|
| Tagline | Free routing, programmable inbound via Workers, sending in beta. | Email API tightly coupled to React Email. |
| Free tier | Email Routing free; Email Workers on Workers Free plan | 3,000/mo permanent, one domain |
| Starts at | Sending: $0.35 per 1,000 messages (Workers Paid required, $5/mo) | $20/mo for 50,000 emails |
| Pricing model | pay-as-you-go | tiered |
| API | Yes | Yes |
| SMTP | No | Yes |
| SDKs | node | node, python, go, ruby, php, rust, java, elixir, cli |
| Templates | none | react-email |
| React Email | No | Yes |
| Webhooks | No | Yes |
| Inbound | Yes | No |
| Multi-tenant | Yes | No |
| Idempotency | No | Yes |
| Dedicated IP | No | Yes |
| Deliverability | Free Email Routing forwards reliably and inherits Cloudflares operational maturity. The new Sending API has no track record; treat any deliverability claim as unverified until independent tests appear. | Acceptable, but the deliverability track record is shorter than Postmark or SendGrid. Independent inbox-placement studies vary. Dedicated IPs are available on higher tiers. |
| DX score | 8/10 | 8/10 |
| 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 uncompetitive at scale; 500k/mo costs roughly six times AWS SES
- ›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
- ›No native inbound parsing
- ›Single-region historically; multi-region setup is newer
- ›Smaller support footprint than Twilio SendGrid or Sinch Mailgun