# Radar

> Radar is open-source Kubernetes visibility for platform engineering teams. One Helm chart for self-host (Apache 2.0), or Radar Cloud for fleet aggregation, persistent retention, SSO, and routed alerts.

Radar gives engineers a unified view of every Kubernetes cluster they run - topology, event timeline (past the 1-hour TTL), Helm releases, image filesystem inspection, cluster audits, and an MCP server for AI agents. The full engine is Apache 2.0 and runs from a single binary or Helm chart. Radar Cloud is the hosted control plane that adds multi-cluster fleet view, retention up to 1 year, SAML/OIDC SSO, scoped RBAC, and routed alerts.

## Product

- [Product Overview](https://radarhq.io/product): Everything Radar OSS and Radar Cloud ship together
- [Topology](https://radarhq.io/product/topology): Live Kubernetes resource graph - SSE-updated, ELK.js-laid-out, group by namespace or label
- [Event timeline](https://radarhq.io/product/timeline): Every K8s event and resource delta, persisted past the kube-apiserver 1-hour TTL
- [Image filesystem viewer](https://radarhq.io/product/image-filesystem): Browse any container image's filesystem - tree, sizes, symlinks - without kubectl exec
- [Cluster audit](https://radarhq.io/product/cluster-audit): 30 best-practice checks across security, reliability, and efficiency
- [AI via MCP](https://radarhq.io/product/mcp): Model Context Protocol server for Claude, Cursor, Copilot, and other agent clients

## Use cases

- [Solutions](https://radarhq.io/solutions): What Radar is for - troubleshooting, multi-cluster ops, GitOps, Helm, compliance
- [For SREs](https://radarhq.io/for/sre): Cut incident MTTR without adding another dashboard
- [For Platform Engineering](https://radarhq.io/for/platform-engineering): Self-serve Kubernetes visibility, org-wide
- [For DevOps Leaders](https://radarhq.io/for/devops-leaders): Kubernetes as a business function

## Compare

- [All comparisons](https://radarhq.io/vs): How Radar stacks up against the tools platform teams already use
- [Radar vs Lens](https://radarhq.io/vs/lens): Open-source, native, and a fraction of the size
- [Radar vs k9s](https://radarhq.io/vs/k9s): Team-native Kubernetes visibility, keyboard-friendly

## Open source and pricing

- [Open Source](https://radarhq.io/open-source): Radar OSS comparison - local binary, self-hosted, and Cloud
- [Migrate from OSS to Cloud](https://radarhq.io/migrate): 10 minutes, one Helm flag
- [Pricing](https://radarhq.io/pricing): Per-cluster pricing, never per seat - Free tier, $99/cluster/mo Team, custom Enterprise
- [GitHub repo](https://github.com/skyhook-io/radar): Apache 2.0, the full engine
- [Documentation](https://radarhq.io/docs): Install, configuration, and reference

## Company

- [About Radar](https://radarhq.io/about): The team behind Radar and our OSS commitments
- [Community](https://radarhq.io/community): GitHub, Discussions, Discord, and the maintainers
- [Changelog](https://radarhq.io/changelog): Every tagged Radar release
- [Support](https://radarhq.io/support): Support channels, response-time matrix by tier, SLA definitions
- [Demo](https://radarhq.io/demo): Book a 30-minute walkthrough

## Blog

- [Introducing Radar: Multi-Cluster Kubernetes Visibility for Teams](https://radarhq.io/blog/introducing-radar-cloud): Radar Cloud is the hosted multi-cluster extension of Radar OSS. Fleet view, 30-day timeline, SSO, scoped RBAC, alerts. Credentials never leave your cluster.
- [Why We Priced Radar Per Cluster, Not Per Seat](https://radarhq.io/blog/why-per-cluster-pricing): Per-seat pricing punishes the thing a visibility tool is for: more eyes. Here's the five pricing models we compared, why we picked per-cluster, and where it's a worse deal.
- [Radar OSS or Radar Cloud? An Honest Take on When to Use Each](https://radarhq.io/blog/radar-oss-or-radar-cloud-an-honest-take): The most common question in our GitHub issues: do I need Radar, or is OSS enough? Here's the honest answer, with the five questions that actually decide it.
- [Multi-Cluster Topology: Cross-Cluster Service Maps That Don't Hairball](https://radarhq.io/blog/multi-cluster-topology-cross-cluster-service-maps): Cross-cluster service topology is hard because Kubernetes itself has no multi-cluster graph. Here's how Radar builds one without turning it into a hairball.
- [Your Cluster Events Are Mostly Noise. Here's How We Filter Them.](https://radarhq.io/blog/your-cluster-events-are-mostly-noise): Every team has a #k8s-alerts Slack channel no one reads. Here's why naive event alerting fails and how Radar correlates, suppresses, and routes the 2% that matters.
- [SSO, SCIM, and Scoped RBAC: Team Access Without YAML Wrestling](https://radarhq.io/blog/sso-scim-and-scoped-rbac-in-radar-cloud): A contractor needs read-only access to two staging namespaces by Monday. Without Radar, that ticket bounces for a week. Here's how scoped RBAC fixes it.
- [Persistent Event Timeline: Debugging What Happened Last Tuesday](https://radarhq.io/blog/persistent-event-timeline-debugging-last-tuesday): Kubernetes events vanish after an hour. Radar keeps them for 30 days. Here is how a persistent event timeline changes incident response.
- [Fleet-Scale Informers: Watching Thousands of Watch Streams Without Melting](https://radarhq.io/blog/fleet-scale-informers-watching-thousands-of-clusters): SharedInformer is great until you need a thousand of them. How Radar's backend keeps a live server-side replica of every connected cluster without melting.
- [Radar's In-Cluster Architecture: Outbound-Only, Scoped, 32MB](https://radarhq.io/blog/the-radar-cloud-agent-architecture): How Radar's in-cluster install works: outbound-only TLS, read-only RBAC by default, ~32MB RSS. The five questions every platform team asks, answered.
- [What We're Building in 2026: Radar OSS and Radar Cloud](https://radarhq.io/blog/what-were-building-in-2026-radar-oss-and-cloud): Two shipping dates, one product line. Radar open source ships January 2026, Radar follows in February. Here's the scope, the split, and what won't make it into v1.
- [The Fleet Visibility Gap: Why Teams With 5+ Clusters Hit a Wall](https://radarhq.io/blog/the-fleet-visibility-gap): Every tool that worked at 2 clusters breaks at 8. kubectl, Lens, k9s, Headlamp are all single-cluster-at-a-time. Here's where the wall is and what it looks like.