Cloudflare Takes Aim at Transactional Email
Cloudflare Takes Aim at Transactional Email
- Apple’s Native Linux Container Tool Has Arrived — But Can It Really Replace Docker?
- 60% of MD5 Password Hashes Can Be Cracked in Under an Hour with a Single GPU
- Dirty Frag: Root Access on Every Major Linux Distribution — No Patch, No Warning
- Proton Mail: Data Transferred to FBI Again!
- How Close Are Quantum Computers to Breaking RSA-2048?
- What is the best alternative to Microsoft Office?
Cloudflare Takes Aim at Transactional Email
After launching its Email Sending service in private beta in September 2025, Cloudflare is expanding access to developers. Here is what the service offers — and how it stacks up against Amazon SES, SendGrid, Resend, and Postmark.
For years, developers building on Cloudflare Workers have been able to receive email through Email Routing — but sending transactional messages required wiring in a separate provider. That gap is finally closing. Cloudflare’s Email Sending service, announced in private beta in September 2025, aims to make outbound email as natural as writing a Worker function.
What Cloudflare Is Building
Announced on September 25, 2025 during Cloudflare’s Birthday Week, the Email Sending service combines with the existing Email Routing product to form a unified Cloudflare Email Service. The pitch is simple: developers should be able to send and receive transactional email — password resets, order confirmations, magic login links, onboarding flows — directly within Cloudflare Workers, using the same native binding model they already know.
The service automatically handles DNS configuration, setting up SPF, DKIM, and DMARC records for any verified sending domain. There is no separate API key to manage or risk leaking. A call to env.SEND_EMAIL.send() is all it takes. The service also integrates with popular frameworks such as React Email, supports SMTP and REST API access for external services, and includes delivery observability — bounce rates, delivery events, and per-message status — for debugging.
As of April 2026, Cloudflare Email Sending remains in private beta, available to select early-access developers who signed up via the waitlist. Cloudflare has confirmed the service will require a paid Workers subscription and will be charged based on messages sent. However, the company has not yet published official pricing or a confirmed public beta date. Any specific figures circulating online — such as “3,000 free emails/month” or “$0.35 per 1,000 emails” — are unverified and should not be treated as final until Cloudflare makes an official announcement.
Cloudflare has stated clearly that Email Routing — its existing inbound forwarding product — will remain free and unchanged. The new Email Sending capability is additive, not a replacement.
— Cloudflare Blog, September 2025
How the Competition Is Priced Today
To understand where Cloudflare Email Sending will land, it helps to survey the current landscape. The transactional email market has settled into a few distinct camps: raw infrastructure providers, developer-experience-first services, and full-featured marketing platforms. Each comes with very different pricing models and trade-offs.
| Provider | Free Tier | Entry Paid Plan | Overage Rate | Best For |
|---|---|---|---|---|
| Cloudflare Email Sending New · Beta | Workers Paid required (pricing TBC) | TBC (Workers Paid starts at $5/mo) | TBC | Cloudflare Workers developers |
| Amazon SES Infrastructure | $200 AWS Free Tier credits (new accounts after July 2025); previously 3,000/mo free for 12 months | Pay-as-you-go, no minimum | $0.10 per 1,000 emails | Scale, AWS ecosystem, cost-sensitive teams |
| SendGrid Full Platform | 60-day trial (100 emails/day); no permanent free tier | $19.95/mo — 50,000 emails | ~$0.90 per 1,000 emails | High-volume sending, marketing + transactional |
| Resend Developer-First | 3,000 emails/month, free forever | $20/mo — 50,000 emails | $0.90 per 1,000 emails | React/Next.js developers, modern DX |
| Postmark Deliverability | None (trial credits only) | ~$15/mo — 10,000 emails | $1.80 per 1,000 emails | Critical transactional email, inbox placement |
Pricing based on publicly available rates as of April 2026. Rates may vary by volume tier and plan.
Provider Profiles
Each of the major players in this space has a distinct identity and a target audience. Here is a closer look at what differentiates them.
Tightly integrated into the Workers runtime. No API keys, automatic DNS setup, supports React Email and SMTP. Native inbound + outbound in a single platform.
- No API key management
- Auto DNS configuration (SPF, DKIM, DMARC)
- Global low-latency delivery
- Unified send + receive in Workers
- Requires paid Workers plan
- Still in private beta; no confirmed pricing
- Best value if already on Cloudflare stack
The cheapest option at scale — by a wide margin. Pure infrastructure with no template editor, no analytics dashboard, and no bounce management out of the box.
- Lowest cost per email in the market
- Massively scalable
- Full AWS ecosystem integration
- Sandbox mode for new accounts (manual approval required)
- Requires significant engineering to build on top
- No built-in logs or analytics
- Best for teams comfortable with AWS infrastructure
A battle-tested platform for both transactional and marketing email. Rich dashboard, templates, A/B testing, and strong deliverability tooling — but the free tier is gone.
- Comprehensive feature set
- Handles very high volumes well
- Dedicated IP options available
- No permanent free tier since 2025
- Dashboard UX criticized as dated
- Higher overage costs (~$0.90/1K)
- Best for high-volume teams needing a full platform
The developer darling. Built by the React Email team, with a clean API and first-class JSX templating. Routes all mail through Amazon SES under the hood.
- Best developer experience in the category
- 3,000 free emails per month, no expiry
- React Email / JSX templates natively
- Built on SES — you’re paying a markup for DX
- Short message retention (1–3 days on lower plans)
- Relatively new; some maturity concerns
- Best for React/Next.js developers at startup scale
The deliverability specialist. Postmark operates separate infrastructure for transactional and broadcast email, maintains strict sender quality standards, and is obsessive about inbox placement.
- Industry-leading inbox placement rates
- Separate message streams (transactional vs. broadcast)
- 45-day message history for debugging
- No permanent free tier
- Higher per-email cost ($1.80/1K overage)
- No visual template builder or list management
- Best when inbox delivery is mission-critical
What Makes Cloudflare Different
Every provider in this space sells the concept of reliable transactional email delivery. What sets Cloudflare’s approach apart is its tight integration with the existing Workers platform — and what that integration removes from the developer’s plate.
No credentials to manage
Services like Amazon SES, Resend, and SendGrid all require generating and securely storing API keys. Cloudflare Email Sending uses the same native binding model as Workers KV, R2, and Queues. Developers add a binding to their wrangler.jsonc configuration, and the runtime handles authentication. There are no secrets to rotate, no keys to accidentally expose in a public repository.
DNS setup is automatic
Configuring SPF, DKIM, and DMARC records is one of the most error-prone parts of setting up a new email provider. Cloudflare automates this entirely for domains already managed through its DNS service, which covers a significant portion of the developer market. Amazon SES and others require manual DNS configuration steps, which are a common source of deliverability failures.
Inbound and outbound in one place
Cloudflare’s existing Email Routing product — which lets developers receive and programmatically process incoming messages — is already free and widely used. With Email Sending added to the mix, developers can close the loop entirely within one platform. A support email arrives, a Worker processes it, creates a ticket via API, and sends a confirmation back — all without leaving the Cloudflare ecosystem. No equivalent unified solution exists among the competing providers without significant glue code.
Where Cloudflare still has questions to answer
The service’s biggest unknown remains pricing. Until Cloudflare publishes official rates, it is impossible to make a definitive cost comparison. A second open question is sending reputation: new email infrastructure takes time to build a trusted reputation with inbox providers like Gmail and Outlook. Established players like Postmark and Amazon SES have years of sending history behind them. Developers relying on Cloudflare for critical transactional email will want to watch deliverability metrics closely at launch.
Cloudflare Email Sending is a genuinely interesting entrant in a crowded market — not because it will immediately be the cheapest option, but because it addresses email delivery as a native platform primitive rather than a bolt-on integration. For teams already running their infrastructure on Cloudflare Workers, the combination of zero-credential-management, automatic DNS setup, and unified send/receive capability is a compelling argument to stay in the ecosystem.
For teams at scale who need the lowest per-email cost, Amazon SES at $0.10 per 1,000 emails remains the benchmark. For developers who want the best experience building with React, Resend leads the field. For teams where inbox placement is non-negotiable, Postmark is still the safest bet. And for organizations that need a full marketing and transactional platform under one roof, SendGrid handles the volume.
Cloudflare will need to publish competitive pricing and demonstrate strong deliverability before it can claim a clear position in this comparison — but the architecture it has built is the right foundation. When final pricing lands, this table will likely change.
