Production checklist
The list of things to verify before you point real users at a CtrlApp-managed feature.
Do not skip this page. Every item exists because a real team learned it the hard way.
Environment separation
- Test build uses a Test environment key. Production build uses a Production key.
- No Test key ships in the production binary.
Keys and secrets
- Publishable keys are the only credentials in client code.
- Signing secrets live only on servers you control.
- Rotate keys after any laptop loss, contractor offboarding, or leak.
Kill-switch reachability
- The client calls /session at launch and caches the decision.
- A test block rule blocks a test device end-to-end in under 60 seconds.
Rollouts
- New flags start at 0% and ramp; changes go through a small internal segment first.
- Every change is audited — see Live sessions, activity & audit.
- Every risky control has a documented rollback path.
Rate limits & backups
- You have read the rate limits for your plan.
- You know where backups live and how to restore.
Security
- You have read Security hardening.
- You do not log full request bodies with device identifiers in your own logs.