Why do teams look for an alternative to Cloudflare Email?
The limits Cloudflare Email documents itself:
- Email Routing rules have two actions, send to an email address or send to a Worker; processing beyond forwarding means writing an Email Worker. source: developers.cloudflare.com
- Inbound messages larger than 25 MiB are rejected. source: developers.cloudflare.com
- On the Workers Free plan, complex email handlers may exceed CPU and memory limits and fail with EXCEEDED_CPU. source: developers.cloudflare.com
- Replies via message.reply() throw an error when the incoming email has more than 100 References entries. source: developers.cloudflare.com
What does Cloudflare Email do well?
- Forwarding to verified destination addresses is free on all plans. source: developers.cloudflare.com
- Sending through a Workers binding, a REST API or SMTP. source: developers.cloudflare.com
- agentic-inbox is an Apache-2.0 reference app you deploy yourself. source: github.com
What are the alternatives?
nofeb
- nofeb's own MX, with sender authentication and spam and virus checks before acceptance, when you would rather not route through Cloudflare.
- Approval of held sends by a person, enforced on the server for every interface.
- Rules over sender, content, the security verdict, metadata and decisions, with Sieve import and export, in place of a Worker per routing decision.
- Full-text and semantic search across inboxes, and a webmail for the humans in the loop as part of the service rather than an app to deploy.
Postmark inbound
Inbound message streams that POST each email as JSON to one webhook URL. source: postmarkapp.com
Mailgun routes
Routes that match incoming mail and forward it to a URL or an address. source: documentation.mailgun.com
How does a Cloudflare Email setup map to nofeb?
| On Cloudflare Email | On nofeb |
|---|---|
| Email Routing rule to a Worker | Keep it, and deploy nofeb's Email Worker as the target: it passes the message and envelope to nofeb and spools to R2 if nofeb is unreachable. |
| A Worker that parses mail | nofeb parses every message: reply_text, safe_body, one-time codes, links and attachment text. |
| Durable Object per mailbox | A hosted inbox per address, threads, folders and typed metadata, with no storage to run. |
| Sending from a Worker | Send, reply and forward from the inbox, with threading headers set, autonomy tiers and idempotency keys. |
How does pricing compare?
- Cloudflare Email: 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 Free: $0 a month, inboxes 10, 3,000 messages processed a month, usage past the allowance refused.
- nofeb Build: $19 a month, inboxes Unlimited, 25,000 messages processed a month, usage past the allowance billed.
- nofeb Scale: $99 a month, inboxes Unlimited, 250,000 messages processed a month, usage past the allowance billed.
- nofeb Enterprise: Custom, inboxes Unlimited, custom messages processed a month, usage past the allowance billed.
The pricing page has nofeb's unit prices.
When is Cloudflare Email the better choice?
- Your agents already run on Workers and you want email as a binding with no API keys. source: blog.cloudflare.com
- You want to build and run your own inbox app from an open-source starting point. source: github.com
Frequently asked questions
Can I use nofeb and Cloudflare Email Routing together?
Yes. Route the domain or a catch-all to nofeb's Email Worker; mail lands in nofeb inboxes with the envelope intact.
What does nofeb add on top of Email Routing?
Inboxes, threads and typed state, parsed and model-safe text, injection scoring, search, wait_for_email, signed webhooks, an MCP server, and sending policy with human approval.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| Inbound from the provider you already use | Receive through Cloudflare Email Routing with an Email Worker on your own zone, a Postmark inbound stream, a Mailgun route, SendGrid Inbound Parse, or any service that can POST a raw message. Each path is authenticated by your organization's inbound token, which you can rotate at any time, and delivers only to your own inboxes and verified domains. | Shipped |
| Inbound mail server that checks mail at the door | nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. | Shipped |
| Reply extraction | Each message carries its new text with quoted history and signature removed. | Shipped |
| safe_body for untrusted mail | The message's new text with zero-width and direction-altering characters, hidden HTML and forgeable quoted history removed, wrapped in a provenance header that tells the model whose words these are. | Shipped |
| One-time code and link extraction | Verification codes and classified links are pulled out of every message and returned as fields. | Shipped |
| Typed metadata on messages, threads and inboxes | Merge-patch keys onto a message, a thread or an inbox, and declare a key's type so every write to it is validated. | Shipped |
| Human approval of held sends | A held send waits with status awaiting_approval until a human approves or rejects it; both steps emit events. The approval queue lists every held send with its recipients (each marked if new to the conversation), the reasons it was held and who submitted it. Approving needs the separate send:approve scope, which keys from agent self-signup never hold, so an agent cannot approve its own send. | Shipped |
| Autonomy tiers enforced by the server | Every inbox carries a sending policy, from read-only to autonomous, enforced on the server for every surface that sends, so switching from the API to MCP cannot bypass it. | Shipped |
| MCP server | 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. | Shipped |
| Rules and Sieve | Declarative rules over sender, recipients, subject, body, headers, attachments, size, the security verdict, metadata and decisions, that label, move, flag, set metadata, quarantine, forward, auto-reply or reject. Test rules against a stored message with a per-rule trace, and import or export Sieve, with anything that cannot be mapped reported line by line. | Shipped |
| Search that understands | Full-text and semantic search over subjects, addresses, the new text of each message, attachment names and attachment text, across every inbox a key can see. Filter by inbox, pod, folder, thread, sender, recipient, date, attachments, keywords, authentication failures and metadata; results carry highlighted snippets and can be grouped by thread. | Shipped |
| Injection scoring and quarantine | Every inbound message gets a prompt-injection score from 0 to 1 with its reasons: hidden text, invisible and look-alike characters, instructions aimed at an AI, role and chat-template tokens, tracking beacons, data-carrying links and encoded payloads. Above the threshold you set per organization, pod or inbox, the message is quarantined (or only flagged) for a person to release or delete, and its content stays out of the delivery event. | Shipped |
| Webmail for the humans in the loop | 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. | Shipped |