Cbox ID
Operations
Operations
Deploying and running a live identity provider. cboxid.com runs on Cbox's own
Kubernetes cluster and is released automatically from main; every page also covers
running it yourself on a VM, a PaaS or any Kubernetes cluster.
- Deployment — how production runs and how a merge to
mainreaches it, what the application expects from its environment, and, for self-hosters, from a fresh server or cluster to a running, hardened instance. - Day-2 operations — backing up the crypto key, signing-key rotation, health checks, audit/monitoring, upgrades, and the break-glass runbook.
- Queue workers — running the queue manager on Kubernetes, a VM or a PaaS, the operator-only job monitor, and the health signal that says it is running.
- Administering the platform's own environment — the root
environment's console at
/adminon the root host, who administers it, the guards that keep operators able to sign in, andcbox-id:operator:grant. - Live smoke test — a reproducible end-to-end run with the real clients (cbox CLI, an MCP client, both SDKs) against a live deployment.
- Rehearsing an upgrade — prove a release migrates your database: the seeded check on MySQL and PostgreSQL, and a rehearsal on a copy of your own data.
- Analytics storage — where authentication analytics are stored (nothing, the app's own database, or ClickHouse) and the retention each needs.
The single most important thing on this page: back up CBOX_ID_CRYPTO_KEY
separately from the database. Losing it makes sealed secrets unrecoverable. See
Day-2 operations.