Deploy a catch-all inbox on Cloudflare Workers.
Cloudflare Inbox packages Email Routing, Email Service, R2, Queue events, and a Waku web UI into a single-tenant Worker deployment for custom-domain support mail.
Click Deploy to Cloudflare and pick resource names.
Set the required secrets and app/domain variables.
Onboard the email domain in Cloudflare Email Service.
Route catch-all or selected addresses to the deployed Worker.
Open the inbox, sign in with a magic link, and send a test reply.
Email Routing inbound
Catch-all mail lands directly in the Worker email handler.
Email Service outbound
Replies, forwards, and magic links send from the Worker binding.
R2 message archive
Raw EML, normalized messages, attachments, and settings stay in R2.
Queue and API hooks
Emit handled-inbound events and expose bearer-token APIs for automation.
What one-click does
The deploy button can clone the app, build the Worker, and provision supported Wrangler resources such as R2 and Queues from the template configuration.
What still needs domain setup
Email Service and Email Routing require domain onboarding, DNS records, destination verification, and catch-all routing to the deployed Worker.
Ready for Cloudflare-first teams.
Use it when your domain already lives on Cloudflare or when you want the inbox, storage, sending, routing, and automation events to stay in one platform.