Cloudflare Email Service entered public beta on 2026-04-16 as part of Cloudflare's Agents Week. The product is callable from any backend via REST or via Workers bindings inside a Cloudflare Worker, configures SPF, DKIM, DMARC, and bounce MX automatically when your sending domain is on Cloudflare DNS, and ships an open-source Agentic Inbox reference app with an MCP server. For teams already on Workers Paid with their domain on Cloudflare, the integration is genuinely tight.
The product is also in public beta. Cloudflare's documentation notes that beta features and APIs may change before general availability; pricing on the Cloudflare pricing page is current as of April 2026. Email Sending requires a $5/mo Workers Paid plan as a hard prerequisite for any sending volume above the 3,000-email Workers Paid allotment.
Where Cloudflare Email Service fits well
Cloudflare Email Sending is the right default when:
- You already pay for Workers Paid and you're comfortable adding email as another usage line on that plan
- Your sending domain is already on Cloudflare DNS so SPF, DKIM, DMARC, and bounce MX records configure automatically
- You're comfortable running billing-critical infrastructure on a public-beta product whose features and APIs may change before GA
- You want Cloudflare's Agentic Inbox reference architecture, especially for an AI agent that runs on Workers
Where Bavimail fits better
The decision flips when:
- You don't already pay for Workers Paid and don't want to take on a $5/mo platform fee just to send transactional email
- Your sending domain is hosted somewhere other than Cloudflare DNS and you don't want to migrate it to use Cloudflare for email
- You need stable GA contracts today rather than running production traffic on a public-beta product whose features and APIs may change before GA
- You want a single managed service for both outbound and inbound email rather than wiring two Cloudflare products with their own configuration
- You want platform-agnostic SDKs (TypeScript, Python, .NET) callable from any backend
Pricing across canonical tiers
- 5,000/mo: Bavimail Free vs Cloudflare $5.70 (Workers Paid + 2K overage). Bavimail wins by $5.70.
- 10,000/mo: Bavimail Pro $4 vs Cloudflare $7.45. Bavimail wins by $3.45.
- 50,000/mo: Bavimail Growth $20 vs Cloudflare $21.45. Bavimail wins by $1.45.
Bavimail wins all three canonical tiers. The 5K tier carries the largest gap because Cloudflare's Workers Paid base is mandatory for any volume above the free 3,000-email allotment, even when the per-email cost would otherwise be near zero.
See the full Bavimail vs Cloudflare Email Service pricing comparison for a tier-by-tier breakdown and feature comparison.
Which to choose
Choose Cloudflare Email Service if: you already pay for Workers Paid, your sending domain is on Cloudflare DNS so SPF, DKIM, DMARC, and bounce MX configure automatically, and you're willing to run production traffic on a public-beta product whose features and APIs may change before GA. Workers binding integration is an upside if your application happens to run on Workers.
Choose Bavimail if: you want a managed email platform that any backend can call directly without taking on a Workers Paid plan or migrating DNS to Cloudflare, stable GA pricing, lower entry cost, and no upstream platform coupling.
If you're building for specific use cases: Bavimail for developers details the SDK and REST API. Bavimail for AI agents covers per-agent inbox patterns and MCP-compatible agent workflows. Bavimail pricing shows the full plan comparison.