·How it works

From sign-up to a running app.

Four stops. Nothing asked for just in case.

The path an app takes: connect Cloudflare, pick an app, grant only what it needs, deploy into your account. Connect CloudflareCloudflare’s own consent screen. Pick an appEvery permission, up front. Grant onlywhat it needsExtra scopes only when asked. DeployLive log, then a health check.The path an app takes, from connecting Cloudflare to a deployed app. Connect CloudflareCloudflare’s own consent screen. Pick an appEvery permission, up front. Grant only what it needsExtra scopes only when asked. DeployLive log, then a health check.

Live

Mailroom

mailroom.yourdomain.com

  1. Connect Cloudflare: Cloudflare’s own consent screen.
  2. Pick an app: Every permission, up front.
  3. Grant only what it needs: Extra scopes only when asked.
  4. Deploy: Live log, then a health check.

·Rebuilt, not ported

Twelve parts. Twelve primitives.

Hover a pair.

  1. CPU and app processWorkers
  2. Postgres / MySQLD1
  3. Disk and filesR2
  4. Redis and RAMKV
  5. Long-lived processDurable Objects
  6. Job queueQueues
  7. Cron jobsWorkflows
  8. Mail serverEmail
  9. GPU and modelsWorkers AI
  10. Vector DBVectorize
  11. Headless browserBrowser Rendering
  12. nginx, TLS, firewallEdge

·After day one

Shape. Update. Flow back.

The part nobody else does.

1

Shape

Ask your agent. It edits your copy and opens a pull request.

  • git diff
  • npm test
2

Update

New versions arrive as pull requests. Your changes stay put.

  • v1.4.0
  • rollback
3

Flow back

Good changes return as recipes anyone can apply.

  • recipe.json
Connect Cloudflare Read the security model