Reference
The operator side
For people running a CLI platform: the Operations page, the two-person rule, passkeys, break glass, tripwires and rotating the master key.
This page is for the people who run a CLI platform (operators), not for people hosting apps on one.
Operators see Operations in the dashboard sidebar. It's organised by job: Overview (how the platform is doing), People (find any account), Security, Money (payouts waiting for review), Moderation (listings and abuse reports), and Platform (servers, backups, drills and the status page). Each operator sees only the parts their role covers.
Latest failures on the Overview opens each failed deploy for support operators and admins, in any project: its error, what the health check saw, and the build and app logs (with the project's variable values already masked). It's read only, and each view is recorded in that project's activity log as operator.view_deploy, so the owner can see CLI looked. From the API: GET /v1/admin/deploys/:id. If the service's settings changed after that deploy, the page says which port and path the deploy was actually checked on.
Profit and loss on the Money tab (finance operators and admins) says whether CLI is making or losing money over the last 7, 30, 90 or 365 days. Revenue comes from CLI's books: usage billed to projects and CLI's fees on sales and bounties. Costs come from a list you keep, since CLI can't see its own invoices: add each server, hosting plan and service with what it costs a month (or once), and when it started. Monthly costs count for the share of the period they ran, and ending one stops it counting from that day. The panel shows the net, a monthly pace against running costs, how much more usage a month would break even, and, for context, credit added and credit given away (usage paid with free credit counts in usage billed). From the API: GET /v1/admin/finance?days=30, POST /v1/admin/costs {"name","category","amount","every":"monthly"|"once","startsAt"}, PATCH and DELETE /v1/admin/costs/:id (amounts in micro-USD).
The most sensitive actions need two people: one operator asks, a second approves on the Operations page. That covers adding operators, approving withdrawals and adding large amounts of credit. Operators must sign in with a passkey, and operator pages only open from the networks you allow.
In an emergency, an admin can pause builds or new sign-ups for everyone, or sign everyone out and cancel every key at once ("break glass").
Planted fake secrets ("tripwires") raise an alarm if anyone ever uses one, and CLI tokens published on GitHub by mistake are cancelled automatically.
Roles and access
Operators are listed in CLI_OPERATORS (admins) or given a role: support, finance or admin (see /docs/compliance). GET /v1/me carries operatorRole. Operator routes can be limited to networks with CLI_ADMIN_ALLOW_IPS, and CLI_REQUIRE_OPERATOR_PASSKEY=1 makes a passkey (not just an authenticator code) the way operators confirm it's them.
The Operations page reads GET /v1/admin/stats, GET /v1/admin/people?q= and GET /v1/admin/people/:principal, plus the routes for each tab (cluster, backups, abuse, listings, payouts, platform health).
The two-person rule
Adding operators, approving withdrawals and manual credit over the limit answer 403 OPERATOR_APPROVAL_REQUIRED with error.details.approvalId. A second operator who covers that area approves it:
GET /v1/admin/approvals
POST /v1/admin/approvals/:id {"decision": "approve"} // or "decline"Then the first operator sends the same request again with X-CLI-Operator-Approval: <approvalId>. It works once, within an hour, for the exact same request body. An operator can't approve their own request.
Break glass
PUT /v1/admin/emergency {"buildsPaused": true, "signupsPaused": true, "reason": "…"}
POST /v1/admin/emergency/revoke {"sessions": true, "oauth": true, "apiKeys": true, "github": true, "reason": "…", "confirm": "REVOKE"}Paused actions fail with PAUSED_BY_OPERATOR (503). Revoke ends every session, connected-app token, API key and GitHub link at once (pick any of them). The runbook is deploy/SECURITY.md.
Tripwires and leaked tokens
Honeytokens planted where an attacker would look alert every operator and open a critical security incident when used. Outside canary tokens can be added with CLI_TRIPWIRE_VALUES (NAME=value, one per line). GitHub's secret scanning partner program posts published CLI tokens to POST /v1/github/secret-scanning, and CLI revokes them and tells the owner.
Rotating the master key
CLI_SECRET_KEY can be replaced while running. Put the old key in CLI_SECRET_KEY_PREVIOUS, restart with the new one, and the leader re-seals everything onto it in the background:
GET /v1/admin/master-key
POST /v1/admin/master-key/resealCLI_DERIVATION_KEY decides whether tokens customers can see (webhook URLs, inbox tokens) change when the master key does. Remove the previous key once done is true.
For the rest of running a platform, see Running CLI yourself and Staging and launch checks.
Problem reports and usage
Everyone signed in has Report a problem in the menu. A report carries what the person wrote, the page they were on, the last few failed requests and page errors in their browser (never request bodies or secret values), their screen size, and a screenshot if they picked one. Operators get an email for each, and see them under Operations → Reports, where closing one with a note shows that note to the person.
Operations → Insights shows which dashboard pages are used most and how far new people get: signed in for the first time, made a project, started a deploy, had an app live, came back a day or more later. Page counts are counts only (a page pattern like /projects/:id, a day, a number), never who; browsers that ask not to be tracked send nothing.