# Default The CP9 UI To An Isolated Dev Profile

The upstream production line contains compile-time Sentry, analytics, reCAPTCHA, Stripe, observability, and feature settings in addition to its main API and Auth0 values. A CP9 UI therefore defaults to an isolated dev runtime profile that enables only the current-session API and `tidb-dev` Auth0; absent external-integration values disable those integrations and never fall back to staging or production. This sacrifices immediate fidelity for screens that require shared external systems in exchange for preventing accidental dev-data egress and hidden availability dependencies. External o11y is an imminent follow-up, so typed optional o11y runtime fields remain in the contract and can be enabled with explicit origin, authentication, status, and browser acceptance without rebuilding the image.