Overview

Cloudflare Email Service and Amazon SES both occupy the same shape - a developer-facing transactional sending pipe with no marketing features layered on top. The differences are about ecosystem, maturity, and price.

Cloudflare Email entered public beta on April 16, 2026 after seven months of private beta. It's positioned heavily for two use cases: developers already on Cloudflare Workers (via the no-API-key send_email binding) and builders working with Cloudflare's Agents SDK who need bidirectional email for AI agents. Amazon SES has been GA since 2011 and powers some of the world's largest email senders at billions of messages monthly.

The Fundamental Trade-off

SES is roughly 3.5x cheaper per email - $0.10 per 1,000 vs Cloudflare's $0.35 per 1,000. At 100,000 emails/month, SES costs about $10; Cloudflare costs about $39 (including the required $5/mo Workers Paid plan). At 1 million emails, SES is ~$100 vs Cloudflare's ~$355. The cost difference compounds heavily at scale.

In exchange for that price, Cloudflare gives you a meaningfully better DX inside Workers: no API keys, in-process binding calls, edge co-location with the rest of your code, and SPF/DKIM/DMARC auto-configured if your domain is on Cloudflare DNS. For non-Workers users, the gap narrows - both expose REST APIs and SDKs - but SES has rougher edges around IAM, SNS, and sandbox mode.

Setup Reality

On Workers: Cloudflare Email is minutes. Enable Email Service on your account, bind it in your Worker, call await env.SEB.send(...) and you're done.

On SES: AWS account, IAM user/role with sending permissions, domain verification with DKIM tokens in DNS, sandbox-mode lift via a support ticket (Cloudflare has no sandbox to escape), and SNS topics for bounce/complaint handling. Reasonable to budget a day or two of engineering for a clean SES setup vs minutes for Cloudflare.

Deliverability Approaches

SES gives you full control. You can run on shared IP pools or buy dedicated IPs at $24.95/mo each. You manage warm-up, bounce/complaint thresholds, and reputation - SES will suspend your account if rates exceed thresholds, and getting unsuspended requires a support ticket with a remediation plan.

Cloudflare runs a shared sending pool with daily account-based limits that adjust with sending behavior. SPF, DKIM, and DMARC are auto-configured on Cloudflare-managed domains. There's no documented dedicated IP option as of public beta. For most transactional volumes this is fine, but if you need granular reputation control, SES is the answer.

When Cloudflare Email Makes Sense

If your code already runs on Cloudflare Workers, Cloudflare Email is the path of least resistance. The binding is genuinely nice DX, and the cost only matters at scale. For small/medium volume where the included 3,000/mo covers most sending, Cloudflare may even be cheaper in practice. Building an AI agent on Cloudflare's stack? It's the natural fit.

When SES Makes Sense

For high-volume sending where every cent matters, SES is unmatched. For AWS-native applications, SES integrates seamlessly with Lambda, S3, CloudWatch, and SNS. For mission-critical email (auth codes, billing notifications) where GA stability and dedicated IPs matter, SES is the safer choice. And for compliance-driven enterprises that need region-pinned data residency, SES has 28+ regions vs Cloudflare's single global footprint.

The Marketing Gap

Neither product solves marketing. Both cap at 50 recipients per message, expose no subscriber management, no list-unsubscribe handling, no campaign analytics, no automation. If you start on either expecting to grow into a complete email stack, you'll be building a marketing platform on top of a sending pipe. Sequenzy is purpose-built for that case - unified marketing and transactional with native Stripe integration - and avoids the build entirely.

Making the Choice

Choose Cloudflare Email if you're on Workers, want the cleanest DX, and aren't moved by per-email cost at your volume. Choose Amazon SES for cost-sensitive scale, AWS-native infrastructure, and GA stability. Choose Sequenzy if you also need marketing and don't want to glue tools together.