Cloudflare Inbox

DocsLoginSign in to the inbox

Single-tenant support workspace

One calm web surface for the mailbox already living inside your Cloudflare Worker.

Receive inbound support mail, reply from the browser, and keep the message trail in R2 without dragging in a broader auth or back-office system.

Sign in to the inboxRead the docs

Operator loop

  1. 1. Receive routed support mail inside the Worker.
  2. 2. Persist raw and normalized message records in R2.
  3. 3. Open `/app`, read the thread, and reply from the web UI.
  4. 4. Keep access bounded with a shared cookie-backed sign-in.

Cloudflare-native mail flow

Inbound mail lands through Email Routing, outbound replies go through Email Service, and the inbox stays in one Worker deploy.

R2-backed message history

Raw source, normalized payloads, and attachments stay in object storage so the current app can remain simple.

Shared web access

A single token or password can unlock the inbox with a cookie session when you need a fast operator surface.

Why this shape

Lightweight enough for one shared mailbox, solid enough to operate from the browser.

Public landing, locked app

`/` explains the product, `/login` handles sign-in, and `/app` keeps the mailbox workflow isolated behind the shared session cookie.

No extra auth service

Configure a token or password in the Worker environment and the app can protect itself without adding accounts, callbacks, or session storage.

Existing inbox preserved

The current inbox UI and reply flow remain intact, just moved to `/app` so the public and private surfaces are clearly separated.

Cloudflare-first deployment

The inbox still relies on the Worker bindings already in place, so the auth and route split stays operationally simple.