Every Kubernetes UI we tried does the same thing: it shows you what's running. Pods, namespaces, nodes, workloads. kubectl does this in text. Lens and Headlamp do it in a GUI. k9s does it in a terminal. All of them answer "what's there."
None of them answer "what's actually wrong, and what should I fix first."
That's the gap we built ROZOOM to close.
The problem: state isn't the same as health
You can stare at a dashboard full of green pods and still be one misconfigured resource limit away from an incident. Visibility tools show you the cluster. They don't tell you which of the 40 things you're looking at actually matters right now.
We kept ending up back in kubectl, cross-referencing symptoms manually, because nothing we used would just tell us: here's what's broken, here's what's risky, here's what to fix first.
What we built
ROZOOM is a desktop app (Tauri + SvelteKit, macOS/Linux/Windows) that connects to a cluster and runs two scores against it:
• Runtime Health Score: what's failing right now across control plane, nodes, workloads, observability, and platform hygiene.
• Config Reliability & Security Score: configuration risks that are likely to cause an incident before they do.
Issues are ranked by impact, with remediation guidance attached. You're not scrolling through every resource looking for the one that matters. It's surfaced.
How it connects
30-second version: download the installer, launch, click "Connect a cluster."
• Local cluster (minikube, kind, k3d, Docker Desktop), auto-detected, one-click read-only scan, connect.
• Remote cluster: paste the API server URL and a service-account token. No OIDC setup required for this path.
• Existing kubeconfig also works, including OIDC, cloud import, exec plugins, and Vault.
There's no agent, no operator, no DaemonSet. Nothing gets installed on the cluster. ROZOOM talks to the API server directly from your machine, the same way kubectl does. Disconnect, and nothing is left behind.
Where this sits next to what you already use
• vs Lens: both are desktop apps, so that's not the difference. The difference: no sign-in, no cloud account, Apache 2.0 license, and scoring instead of just a tree view.
• vs k9s: k9s is faster if you already live in a terminal. ROZOOM is for the moment you need to hand a cluster to someone who doesn't, and still get a ranked answer instead of a wall of resources.
• vs Headlamp: closest in spirit (open source, GUI). The scoring and ranked remediation is the part we haven't seen elsewhere.
Open source
ROZOOM is Apache 2.0: github.com/ceh13-community/rozoom | https://rozoom.app. If you're building health signals or config risk checks for Kubernetes, that's exactly the kind of contribution we want.
Top comments (0)