You manage infrastructure. Maybe it's Kubernetes clusters, maybe it's a whole zoo of tools that each need their own window, their own login, their own mental model. You want things in one place, with visibility that doesn't require three browser tabs and a terminal. Here's what we've got.
KubeStudio
The Kubernetes dashboard. When you want to browse clusters, inspect pods, tail logs, and manage deployments without memorizing kubectl flags or squinting at YAML in a terminal.
- Multi-cluster support — switch between clusters without juggling kubeconfig contexts
- Browse everything — namespaces, workloads, pods, services, configmaps — the full resource tree
- Real-time logs — stream pod logs with filtering, without a separate terminal window
- Deployment controls — scale, restart, and manage deployment lifecycle from the UI
Get started with KubeStudio →
Read the docs →
StrikeHub
The unified desktop shell. The thing that holds all the other things. One window, all your connector apps side by side.
- Single window — every connector gets its own panel, but they all share one app
- Shared auth — log in once, and all connectors inherit the session
- Health monitoring — see which connectors are running, which need attention
- Connector lifecycle — StrikeHub discovers, launches, and manages connectors automatically
Get started with StrikeHub →
Read the docs →
How these fit into the platform
KubeStudio and StrikeHub connect to Prospector Studio — the AI backend. That means AI agents can query your clusters, check deployment status, and surface issues without you having to look. For the full architecture, see How It All Fits Together.