Compare / Cloudflare Email Service
nofeb and Cloudflare Email Service
Email sending and routing on the Cloudflare developer platform. Facts checked .
Cloudflare Email Service adds email sending, in public beta since April 16, 2026, to Email Routing, so Workers and agents built on Cloudflare can send and receive mail. source: blog.cloudflare.com
Side by side
Each statement about Cloudflare Email Service comes from its own public documentation or pricing, linked on the line. The nofeb column shows the matching capability and its status.
| Cloudflare Email Service | nofeb |
|---|---|
| Sending through a Workers binding, a REST API or SMTP. source: developers.cloudflare.com | Send, reply, reply-all and forwardShipped Threading headers are set for you, replies default to the original sender, and forwards carry the original attachments. Related: SMTP submission Shipped |
| Inbound mail through Email Routing to Workers, with an onEmail handler for agents built on Cloudflare. source: developers.cloudflare.com | Inbound routed by envelope recipientShipped Mail is delivered to the inbox named in the SMTP envelope, not the To: header, whichever way it arrives, and redelivery is idempotent. Related: Inbound from the provider you already use ShippedInbound mail server that checks mail at the door Shipped |
| Automatic SPF, DKIM and DMARC for sending domains. source: blog.cloudflare.com | Custom domainsShipped Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. Related: DNS setup made easy Shipped |
| agentic-inbox: an Apache-2.0 reference app you deploy yourself, with a mailbox per Durable Object, attachments in R2 and an /mcp endpoint. source: github.com | Webmail for the humans in the loopShipped A full webmail and calendar on the same mailboxes the agents use, with an agent-activity timeline, the approval queue, a per-thread driver lock and a metadata panel, signed in through the same accounts as the console. It opens with hosted access. Related: Self-hosting Not offered |
| An Email MCP server as part of Cloudflare MCP, plus Wrangler email commands. source: blog.cloudflare.com | MCP serverShipped A remote MCP server over streamable HTTP whose tools are generated from the same operation table as the REST API and dispatched through the same router, so a tool cannot behave differently from its endpoint. |
Choose Cloudflare Email Service if
- Your agents already run on Workers and you want email as a binding with no API keys. source: blog.cloudflare.com
- You send high volume and per-message price is the deciding factor, or you mostly receive mail. source: developers.cloudflare.com
- You want to build and run your own inbox app from an open-source starting point. Not offered source: github.com
Where nofeb differs
- A hosted mailbox layer rather than building blocks: inboxes, threads, metadata, approvals and events without writing and operating the storage yourself.
- Autonomy tiers and held-send approval enforced by the server.
- Pods and keys scoped to a pod or an inbox, for products that serve many customers.
- Custom domains with records generated and verified for you, and per-tenant reputation isolation.
- safe_body, one-time code extraction and wait_for_email on every inbox.
- Full-text and semantic search across inboxes, and a webmail for the humans in the loop as part of the service rather than a reference app to deploy.
- Declarative rules with Sieve import and export, and WebAssembly hooks that run your code inside the pipeline without a Worker of your own.
Pricing
- Sending requires the Workers Paid plan, which includes 3,000 emails a month, then $0.35 per 1,000. Inbound is unlimited on the Free and Paid plans. source: developers.cloudflare.com
nofeb's plans are on the pricing page.
How this page is kept honest
Statements about Cloudflare Email Service are taken from its public pages, each linked, as they read on 2026-09-30. Products change; if a line here is out of date, tell us and we will correct it. Statements about nofeb carry the status of the capability they describe, checked against the engine on every build.