systems, artifacts, access This page stays public for orientation, but the destinations do not all share the same access contract. The system should say that clearly instead of pretending everything works the same way.
Primary proxied workspace for internal tools, experiments, and backend-backed product flows.
The proxied app surface keeps authentication, routing, and status checks under the hub while the application itself stays independently deployed.
Open through hubExternal operations workspace for documentation, product context, and long-running system references.
This entry opens directly because the destination already owns its runtime and access pattern. The hub acts as the launch surface, not the host.
Open external appControl plane for orchestration, execution, and operational visibility across local and remote workers.
Direct-launch app for runtime control and execution visibility. The hub keeps it discoverable without forcing it behind another proxy hop.
Open external app