Skyhook (Radar)

Platform teams running Kubernetes at scale rely on kubectl, a tool built for one cluster, one engineer, one moment in time. When an alert fires at 2am, engineers juggle 5+ tools, SSH through jump hosts, and grep logs across dozens of clusters spanning regions and clouds. Kubernetes events are deleted after a default 1-hour retention window, so by the time someone investigates, the evidence of what happened is often already gone. There is no single place to see topology, GitOps drift, Helm history, and audit state together, forcing tab-switching marathons and kubeconfig hunting during incidents.

Radar is a single ~30MB Apache 2.0 binary that can run locally against a kubeconfig (like k9s) or in-cluster via Helm, serving the same UI either way. It presents a live, force-directed topology graph of resources with SSE updates, an event timeline that persists past Kubernetes' default TTL, native ArgoCD and Flux visibility, Helm release history with one-click rollback, and 44 best-practice audit checks. It also exposes an MCP server so AI agents (Claude Code, Codex, Cursor, etc.) can read the same cluster context as the UI for root-cause investigations. Radar Cloud, the hosted companion, adds grouped alerts, AI investigations without a local agent, shared RBAC-scoped views across a fleet of clusters, and up to 30 days of history, while the open-source core remains fully functional and unrestricted.