Cloudflare Inbox

Cloudflare Inbox is the Cloudflare-native Simple Inbox implementation. It runs as a Waku app on Cloudflare Workers and uses Cloudflare services for the mail path and archive.

Runtime stack

• Waku app deployed to Cloudflare Workers
• Cloudflare Email Routing inbound email() handler
• Cloudflare Email Service send_email binding
• R2 bucket for raw EML, message JSON, attachments, reply aliases, and settings
• Optional Cloudflare Queue producer for handled-inbound events
• Bearer-token /api/* machine routes

Best fit

Use Cloudflare Inbox when:

• the domain is already on Cloudflare DNS,
• you want a Worker-first deployment,
• you want R2 and Queue bindings instead of external object storage,
• you want to connect downstream Cloudflare Workers or support automation later.

Launch caveat

The deploy button can create the Worker and supported Wrangler resources, but email domain onboarding still requires Cloudflare account/domain setup. You must finish Email Service and Email Routing setup after the Worker deploys.