skyhook-io/radar·1.3k stars·Apache 2.0

See every cluster.
Stop every fire before it spreads.

Open-source Kubernetes visibility - multi-cluster topology, event timelines, and GitOps. Self-host the Apache 2.0 engine, or use hosted Radar Cloud.

Apache 2.0 · Install with Helm · No account required · or try hosted free
$ brew install skyhook-io/tap/radar
app.radarhq.io / fleet
3 clusters
Radar dashboard showing multi-cluster topology, events, Helm releases, and traffic views
The problem

Your clusters are a black box — until something breaks.

kubectl is great for one cluster, one engineer, one moment in time. But your team runs dozens of clusters across regions and clouds. When an alert fires at 2am, nobody has time to SSH through three jump hosts and grep for pods.

kubectl

Still the on-call engineer's primary debugging tool for multi-cluster incidents

5+

Tools the typical platform team juggles to debug a Kubernetes incident

1 hour

Default event retention in a Kubernetes cluster before data is lost forever

Open source, Apache 2.0

Radar is and always will be open source.

The full engine lives at github.com/skyhook-io/radar. Install it with Helm, run it yourself, keep your data. No feature gates, no license keys, no "call us for pricing" features. Radar Cloud exists for teams that would rather not run it - not because the OSS is crippled.

1.3k+
GitHub stars
Apache 2.0
Permissive license
$0
Self-host, forever
What Radar Cloud adds on top

Don't want to run it yourself? We host it.

Everything Radar OSS does, plus the pieces you probably don't want to operate in-house - durable storage, SSO, cross-cluster roll-ups. Same binary, same features, zero infrastructure.

Multi-cluster fleet view

See every cluster across AWS, GCP, Azure, and on-prem in one pane. Topology, events, and traffic unified.

Long-term event timeline

Events persisted up to 1 year for post-mortems and audits. OSS holds events in memory — Radar holds them forever.

Enterprise auth & RBAC

SAML/OIDC SSO, SCIM provisioning, and team-to-namespace mapping. Map Okta groups to cluster scopes.

Traffic & topology graphs

Live service graphs with east-west traffic, ingress flows, and TLS cert health. Know who depends on what.

Smart alerts

Slack, PagerDuty, and MS Teams integrations. Triggered by event correlations, not just raw signals.

Team collaboration

Shareable deep-links to clusters, resources, and timeline moments. Annotations that survive context switches.

Live · Community signal·1.3k

Loved by Kubernetes operators.

Unfiltered signal from teams running Radar in their clusters. Click any card to see the original.

Redditr/devops

I got kicked out of Lens free dashboard and now I need to subscribe, after using it since like 2020. Saw this post, made the switch and holy I am in love … Lens should be free and this dashboard should be paid 😂

u/More-Lavishness-9969view →
Redditr/devops

Just opened it in under 15 seconds, the topology view is awesome.

u/shellwhaleview →
Redditr/devops

Damn, this is pretty impressive. It's already on my homelab.

u/kryptnview →
Redditr/kubernetes

Was already solid, but the updates you push every week? They are amazing. Love the new Audit Page. Love the keyboard shortcuts, so intuitive!

u/Hxtraxview →
Redditr/kubernetes

I like what I see so far! The timeline feature is a very nice touch.

u/D2W_V4N_V3Sview →
GitHubskyhook-io/radar #64

I tried `radar` for the first time (great work, btw!).

@paulrobuview →

More feedback every week on GitHub, Reddit, and the Kubernetes Slack.

How it works

One Helm chart. Self-host or point it at Radar Cloud.

The agent is the same binary either way. Install it, choose where it talks to. Run the whole stack yourself under Apache 2.0, or let Radar Cloud handle the control plane for you.

STEP 01

Install the agent

One Helm command per cluster. The agent is Apache 2.0 and under 20MB - read every line on GitHub before you run it.

STEP 02

Pick your control plane

Run the Radar backend in your own cluster (self-hosted, free) or point the agent at Radar Cloud. Same UI, same features.

STEP 03

See your fleet

Topology, events, and traffic appear within 30 seconds. No kubectl-forwarding, no jump boxes, no shared kubeconfigs.

Take a tour

Real screenshots. Real product.

Five annotated scenes - fleet, topology, timeline, resources, Helm. No mockups, no marketing renders, no signup wall.

Two ways to run Radar.

Install the OSS engine with Helm, or spin up a hosted workspace. Either way, you see your fleet in 60 seconds.

Apache 2.0 · Self-host forever · Hosted if you'd rather not run it