Decentralized Studio
There is no hosted studio. The operator console is served by your own cluster.
The nearest real thing is the operator console served by every control-plane member: 14 screens, no third-party requests, and a truth basis on every value. There is no hosted 'studio'.
What the console is
Every dh-control member serves the same console (plain ES modules, no build step, no framework, no third-party requests). `dh console` prints a URL whose session capability travels in the URL fragment, which browsers never send to servers; add --read-only for a session that cannot change anything.
Its 14 screens are Overview, Runtime, Hosts, Workloads, Storage, Mesh, Edge, Policy, Audit, Diagnostics, Capabilities, Federation, Conformance and Settings. Desired, admitted and observed state are separate counters, never one health score, and every value carries a truth basis: OBSERVED, DERIVED, CONFIGURED, PLANNED or UNKNOWN.
Limits
The console is checked manually in a live browser; there is no automated browser test suite yet (P0-7). Over TLS, browsers must trust the cluster root CA, or you front the console with your own TLS terminator.
There is no hosted studio. The operator console is served by your own cluster. The nearest real thing is the operator console served by every control-plane member: 14 screens, no third-party requests, and a truth basis on every value. There is no hosted 'studio'.