THE FIRST QUESTION A WORKERS DEVELOPER ASKS

Box Ox vs
Cloudflare Email Service.

Box Ox sends through Cloudflare Email Service, so this is not a choice of transport. It is whether you want an inbox for the replies, scoped keys, templates, logs, signed webhooks and agent grants on top of it, or whether the service alone, called from your own Worker, is enough.

Compare the details ↓Which fits your team?

CHOOSE BOX OX WHEN

Your inbox is part of your app.

You want the replies in a threaded inbox next to the send record.
You want per-domain keys with permissions and budgets instead of one account token in every app.
Your agents need mailbox access you can scope and revoke.

CHOOSE CLOUDFLARE EMAIL SERVICE WHEN

You only need to send, or you need SMTP.

You only need to send, and your app already handles any response.
Your application expects SMTP.
You would rather own a small Worker than install, upgrade and back up an application.

THE PRACTICAL DIFFERENCES

What changes in your day?

A closer look at features, responsibilities, and costs.

On a small screen, scroll the table sideways to compare both products.

Box Ox vs Cloudflare Email Service: features, responsibilities, and tradeoffs
What matters to you	Box Ox	Cloudflare Email Service
Where it runs	An application on Workers, D1 and R2 in your account. Email Service is its mail transport.	Cloudflare’s sending and routing service, called from your own Worker or application. There is no extra application to run. [1]
Send application mail	HTTP API, typed JavaScript SDK and CLI, with idempotency keys, versioned templates and a per-message log. Sending needs Workers Paid.	The Workers binding (`env.EMAIL.send`), the REST API, or authenticated SMTP. Templates and idempotency keys are not part of the API; your code supplies them. [2]
Keep an SMTP integration	The app exposes an HTTP API, not an SMTP submission server. Plan an integration change.	Authenticated SMTP at smtp.mx.cloudflare.net, with an API token as the password. [2]
Credentials	Domain keys act on one domain with listed permissions, optional sender and recipient allowlists, a rate limit and a daily send budget. Management keys mint them and cannot send.	A Cloudflare API token with Email Sending: Edit. It can send from any domain the account has onboarded. [2]
Read and reply to mail	Threaded browser inbox, compose, search, and sent-mail copies. Free is receiving-only.	Email Routing hands each incoming message to your Worker as raw MIME, or forwards it to a verified address. There is no inbox: storing, parsing and threading are your code. [3]
Handle incoming mail	Routes mail into addresses and conversations, stores it in R2 and D1, checks sender authentication and spam, and raises inbound webhooks.	Your Worker receives the envelope, headers and a raw stream and can forward, reply within DMARC rules, or reject. Inbound messages are limited to 25 MiB. [3]
Agent access	Built-in OAuth/MCP and a grant-limited agent API. Give agents mailbox access with revocation and sending caps.	No agent-specific access. An agent would hold the same account token, or call a Worker you write. [2]
Delivery events	Message logs with the event timeline, Standard Webhooks signatures to your endpoints, and suppressions updated from bounces and complaints.	Six lifecycle events per sending domain through Queues event subscriptions, an Activity log in the dashboard, and automatic bounce and complaint suppressions. [5] [6] [7]
Sending scope	The same terms apply: Box Ox sends through Email Service and adds no other transport.	Transactional messages tied to a customer interaction or transaction, under Cloudflare’s service terms. [8]
What you maintain	Your installation, access policies, DNS, backups, updates, and Cloudflare usage. Cloudflare handles the mail transport.	Your own Worker code for sending, receiving, storage and events, plus DNS and your Cloudflare usage. Nothing to upgrade but your code. [1]
What you pay for	No Box Ox subscription. The same Email Service rates, plus Workers, D1 and R2 usage for the app itself.	Workers Paid: 3,000 emails a month included, then $0.35 per 1,000. Receiving is unlimited on both plans; routing Workers bill as Workers. [4]

Box Ox is free. On Cloudflare Workers Free it installs as an inbox. Sending, optional AI, semantic search, and browser features need Cloudflare Workers Paid. Review requirements and testing status →

WHERE BOX OX FITS

A conversation.
An app. An agent.

Send an order update from your app, read the customer’s reply in your inbox, and let an agent read the conversation with a mailbox grant. You control the installation and the permissions. Outbound mail uses Cloudflare Email Service, which Cloudflare’s terms cover for transactional sending; confirm with Cloudflare before relying on it for everyday conversational replies.

This is where Box Ox focuses. Choose Cloudflare Email Service when you only need to send, your application expects SMTP, or you would rather own a small Worker than run an application.

Where Cloudflare Email Service is the better fit

Email Service alone is the lighter choice. There is no application to install, upgrade or back up, and its SMTP endpoint accepts integrations Box Ox cannot. Box Ox adds the layer above the transport: an inbox, scoped keys, templates, logs, signed webhooks and agent grants. If you would build those anyway, Box Ox saves that work. If you would not, it is weight you do not need.

We have not run a head-to-head delivery or throughput benchmark. This page makes no claim that Box Ox is faster, cheaper at every volume, or more likely to reach an inbox.

BEFORE YOU SWITCH

Keep the migration practical.

Your sending domain stays on Email Service. Box Ox onboards it through the same Email Sending setup and sends from it.
Replace direct binding, REST or SMTP calls with the Box Ox API or SDK, using a domain key instead of the account token. SMTP integrations need a code change.
Enabling receiving points Email Routing at the Box Ox Worker. Review your existing routing rules and Email Workers first; Box Ox previews DNS changes and asks before replacing another provider’s MX records.
Box Ox subscribes each sending domain to its own events queue and exposes the events as message logs and signed webhooks. Decide what happens to any consumer you wrote against Email Sending events.