Operations
A browser console for reading a deployed environment, and the service that reaches the infrastructure on its behalf.
Operations tooling comes in two pieces. The app is what an operator opens; the service is what holds every credential. The browser never talks to a cluster, a database, or Service Bus directly.
The one rule
Everything an operator can see passes through devops-service, which is deployed once per
environment. A production deployment sets ENV=prod, loads only the production branch of its
registry, and holds no development configuration at all — so no URL an operator can type will show
them the wrong environment.
Onboarding will manage property drafts and consumer handoff
The planned service will support property-scoped draft worksheets, one-way consumer handoff, and read-only onboarding records.
DevOps App
The operator console — pods, logs, terminals, Helm releases, outbox backlogs, Service Bus, read-only SQL, feature flags, and links to the consoles used to operate Flow.