Operating it
The Runbook is self-hosted, in one of two editions. They run the same engine, language, API, CLI, MCP server and web app; they differ in where state lives and how you deploy and update.
| Docker/Kubernetes | Cloudflare | |
|---|---|---|
| Runs as | One container image: the server, the sign-in service, the web app and the CLI | Two Workers (api and sign-in) with Durable Objects, D1, R2 and Queues, in your account |
| State | PostgreSQL 14+ | D1 (directory and indexes), Durable Objects (runs), R2 (blobs) |
| Blobs | In PostgreSQL, or a GCS or S3 bucket | R2 |
| Configured with | Environment variables | wrangler.prod.jsonc, wrangler.auth.prod.jsonc and wrangler secret put |
| Updated with | deploy/update.sh (compose) or a new image |
npm run update in cloudflare/ |
| Backups | pg_dump or your provider’s |
D1 Time Travel, plus project exports |
| Plan needed | Any host that runs a container | Workers Paid |
Pages that differ by edition say so with Docker/Kubernetes and Cloudflare tabs or notes.
Install and configureThe settings every install needs, on each platform.
Sign-in and rolesEmail codes and Google, invitations, organization and project roles.
StoragePostgreSQL, and blobs in Postgres, GCS or S3.
Upgrades and rollbackVerified releases, automatic backups and rollback.
BackupsWhat to back up, and the secrets that go with it.
Archives and retentionDaily archives, and how long run detail is kept.
MonitoringHealth checks, logs and the doctor command.
LimitsEvery size and rate limit, and the ones you can set.
Keep runbooks in GitPublish a repository folder from CI.
Slack and emailNotifications, and approving from Slack.