head to head
Cloudflare Email Service vs Amazon SES
Two infrastructure giants approaching email from opposite ends: Cloudflare bundles routing and Workers, AWS bundles raw scale.
Side by side
| Feature | Cloudflare Email Service | Amazon SES |
|---|---|---|
| Tagline | Free routing, programmable inbound via Workers, sending in beta. | Cheapest at scale, most setup work. |
| Free tier | Email Routing free; Email Workers on Workers Free plan | 62,000/mo free if sent from EC2 (otherwise paid from email one) |
| Starts at | Sending: $0.35 per 1,000 messages (Workers Paid required, $5/mo) | $0.10 per 1,000 emails |
| Pricing model | pay-as-you-go | pay-as-you-go |
| API | Yes | Yes |
| SMTP | No | Yes |
| SDKs | node | node, python, go, ruby, php, java, rust, dotnet |
| Templates | none | basic |
| React Email | No | No |
| Webhooks | No | No |
| Inbound | Yes | Yes |
| Multi-tenant | Yes | No |
| Idempotency | No | No |
| 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. | Inherits AWS IP reputation. Generally good once warmed and configured, but the sender does the warming and complaint handling. |
| DX score | 8/10 | 4/10 |
| Best for | Domains already on Cloudflare that want free routing, programmable inbound, and a cheap sending API in one place. | High-volume senders with AWS infrastructure, cost-optimized workloads, and teams comfortable wiring SNS/Lambda/EventBridge for events. |
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
Amazon SES
pros
- ›Cheapest cost per email, by a large margin at scale
- ›Built for billions: handles the largest sender workloads in the world
- ›Multi-region (us-east-1, us-west-2, eu-west-1, ap-south-1, and more) with regional reputation pools
- ›Native integration with Lambda, SNS, SQS, EventBridge, and CloudWatch
- ›Dedicated IPs and managed dedicated IP pools
- ›VPC endpoints for sending from private networks
- ›Inbound receiving with S3 and Lambda for fully serverless email pipelines
- ›SDKs in every language AWS supports, from Rust to .NET
- ›IAM-based authentication; no separate API keys to manage
cons
- ›Sandbox mode requires manual approval before sending to non-verified recipients
- ›No native webhooks; events route through SNS and you write your own glue
- ›No dashboard for message-level debugging
- ›Bounce and complaint handling is the senders responsibility
- ›Templates are minimal
- ›Operational overhead is real if you are not already on AWS