Radar
The open-source Kubernetes UI for humans and AI agents
Radar is the open-source Kubernetes UI to beat for AI-native debugging. The free OSS version is genuinely full-featured, and the MCP integration is ahead of anything in Lens or k9s. If you're managing clusters day-to-day, this is worth switching to.
Verified 4d ago · liveness 81/100 · cite: rightaichoice.com/tools/radar
- Platform engineers managing multiple Kubernetes clusters
- On-call teams needing fast incident debugging with AI assistance
- DevOps teams adopting GitOps (Argo CD/Flux) and Helm workflows
- Organizations requiring SSO and scoped RBAC for Kubernetes access
- Users who prefer a CLI-only workflow like k9s
- Teams that need deep application performance monitoring (APM)
- Organizations without Kubernetes infrastructure
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Radar if you prefer a CLI-only workflow like k9s, or if you need deep APM capabilities that Radar doesn't offer.
Past 3 clusters, you need the Team plan at $149/cluster/month, which can add up with many clusters.
Radar's per-cluster pricing is fair for small to mid-size teams. OSS is free forever, and Cloud Free is great for up to 3 clusters. At $149/cluster/month, Team is competitive with Lens Enterprise, but if you have many clusters, it adds up. Compared to Datadog's per-host pricing, Radar is cheaper for Kubernetes visibility, but for heavy monitoring needs, Datadog is more comprehensive.
In short
Radar — The open-source Kubernetes UI for humans and AI agents. Best for Platform engineers managing multiple Kubernetes clusters, On-call teams needing fast incident debugging with AI assistance, DevOps teams adopting GitOps (Argo CD/Flux) and Helm workflows. Free to start; paid plans from $149/mo.
What's new in Radar
Checked 2 days agoAcross the latest 10 updates: 3 feature updates, 1 changelog entry, 2 community discussions and 4 news mentions.
Radar v1.12.2 released
Radar v1.12.2 released on August 31, 2026. Details in the full changelog.
Kubernetes 1.37 Breaking Changes: What to Check Before You Upgrade
Deep dive on Kubernetes 1.37 breaking changes: 25 removed feature gates, alpha scheduling API removal, 18 kubelet flags, and the start of the nftables transition.
Radar OSS v1.12.0 adds Kubernetes 1.37 upgrade impact checks
OSS v1.12.0 includes nine evidence-backed checks for the Kubernetes 1.36 to 1.37 boundary, covering removed feature gates, kubelet flags, API and metric removals.
Radar OSS v1.11.0 adds network visibility for Calico and Beyla
First-class network visibility: shows Calico policy intent and Grafana Beyla observed traffic through Prometheus, with purpose-built list and detail views.
Radar OSS v1.11.0 operates Argo Rollouts
Radar now understands canary and blue-green progression end to end, enabling promote, abort, and retry actions from the Rollout page, gated by permissions.
Everything Is Green and Nothing Works: Network Reachability in Radar
Radar's Reachability tab traces the declared network path and live-probes it, naming the first hop that breaks when ready shows green but curl times out.
Kubernetes Events Expire in an Hour. Your Incidents Don't.
Explores how Kubernetes events expire after one hour and many changes never become events; how to keep history that survives.
Read-Only Is Not a Safety Boundary
Argues that 'read-only' and 'just use the service account' are not safety boundaries when wiring AI agents into a cluster.
We Build a Kubernetes Dashboard. AI Agents Might Make It Obsolete.
Honest bear case: if agents operate the cluster, who needs the UI? Discusses what actually dies and the job that gets bigger.
Radar MCP vs kubectl: A Kubernetes Agent Benchmark on 54 Faults
Radar MCP reached correct diagnosis in 41 seconds vs 154 seconds for raw kubectl across 54 live faults.
What people actually say about Radar — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
66 mentions across 4 sources (Hacker News, App Store, GitHub, Lemmy) · researched Jul 2, 2026.
- +Live topology graph with SSE updates for real-time cluster visibility.
- +Container image filesystem browser eliminates kubectl exec for debugging.
- +Built-in Helm release tracking, comparison, and rollback capabilities.
- +GitOps visibility for ArgoCD and Flux in one dashboard.
- +MCP server enables AI agents like Claude to interact with the cluster.
- −Almost no real user reviews exist for the Kubernetes tool.
- −Free tier event retention is only 1 hour, limiting debugging scope.
- −Self-hosted version lacks multi-cluster fleet management features.
- −Cloud layer needed for SSO, persistent retention, and alerts.
- −No community benchmarks or uptime data for reliability validation.
- • Cloud tier pricing undisclosed — may scale with cluster count
- • Self-hosted requires infrastructure for running the tool in-cluster
Viability Score
How well maintained and how widely used is Radar? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: September 2026
How we score →Key Features
- Live resource topology graph with ELK.js layout and SSE updates
- Persistent event timeline with per-resource timelines and full-history backfill
- Helm release tracking with revision comparison and rollback
- GitOps visibility for Argo CD and Flux with drift diagnosis
- Container image filesystem browser
- Cluster audit with 36 best-practice checks, framework-labeled
- MCP server for AI agents (Claude, Cursor, Copilot)
- Read-only AI investigations with BYO agent CLI (Claude Code, Codex, Cursor)
- Exec, attach, cp, and port-forward from browser
- Multi-cluster fleet view and global search (Cloud)
- SSO and scoped RBAC per cluster or namespace
- Slack, PagerDuty, MS Teams alert routing
- Cost visibility and rightsizing guidance per workload
- Reachability checks: traces declared network path and live-probes it (DNS, TCP, TLS, HTTP)
- Browser-based, no client installation
About Radar
Radar is an open-source Kubernetes interface that gives platform engineers and on-call teams a live, interactive view of cluster topology, events, Helm releases, and GitOps state. Built as a modern alternative to Lens and k9s, it runs as a standalone binary or in-cluster, with no account or cloud dependency. The UI pairs a real-time resource graph with a persistent event timeline that captures every Kubernetes event and delta past the default one-hour TTL, so you can rewind what happened before an incident. It also includes a cluster audit with 36 best-practice checks, a container image filesystem browser, and native Argo CD and Flux visibility with drift diagnosis. What sets Radar apart is its MCP server, which lets AI agents like Claude, Cursor, and Copilot investigate issues directly — read-only, keyless, and token-optimized. You can bring your own agent CLI (Claude Code, Codex, Cursor) or use the built-in Radar AI agent on Cloud plans. Radar Cloud adds fleet aggregation, SSO, persistent retention, routed alerts, and cost visibility for multi-cluster teams. Recent releases have added live network reachability checks that trace the declared path for Services and Ingresses and probe it (DNS, TCP, TLS, HTTP) to pinpoint the first broken hop. The OSS version is Apache 2.0 and free forever, with Cloud plans starting at $149 per cluster per month. Radar positions itself as the missing interface for both humans and agents, aiming to replace the kubectl roulette of SSHing through jump hosts and grepping for pods during incidents.
Behind the Verdict
Pick Radar when you're tired of juggling kubectl, Lens, and a dozen tabs to debug a single incident. The persistent event timeline alone justifies the switch — Kubernetes events vanish after an hour by default, but Radar stores them centrally for 31 days on Cloud plans, so you can rewind what actually happened before a crash. The MCP integration is the real differentiator: your AI agent (Claude, Cursor, Copilot) can query the cluster read-only, keyless, and token-optimized, which is something neither Lens nor k9s offers. Pass on Radar if you prefer a CLI-only workflow like k9s or need deep application performance monitoring — Radar is about cluster topology and debugging, not APM. It's also not a Grafana or Datadog replacement for metrics and tracing; it focuses on Kubernetes-native visibility. Compared to Lens, Radar wins on being open source with no feature gates — Lens has pushed users to paid plans, while Radar's OSS is free forever. k9s is faster for keyboard-driven CLI use, but Radar's UI is more approachable for teams that need shared context. In practice, the browser-based UI means no client installation, which lowers the barrier for on-call engineers. The recent Reachability tab is a nice addition — it traces the declared network path and live-probes it (DNS, TCP, TLS, HTTP) to name the first broken hop, saving you from manual netcat and dig. Watch out for the Cloud pricing model: it's per cluster, not per seat, so it gets expensive as your fleet grows, though the Free tier covers up to three clusters. Also, the OSS version doesn't include SSO or long-term retention — those are Cloud-only. If you're a platform team running multiple clusters and adopting GitOps, Radar is a strong pick. For small teams or homelabs, the OSS version is a no-brainer to try
Researching Radar? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Radar actually fits — and what changes day-one when you adopt it.
You get paged at 2am for a pod crash. You open Radar, search for the pod name across all clusters, jump to logs, rewind the event timeline to see the last 5 events, and share a link with the team.
Outcome: Root cause identified in under 5 minutes, without hunting through kubectl contexts.
A service is unreachable. You use the new Reachability tab to trace the network path from the client, API-server relay, and an in-cluster pod, and see the exact hop that fails.
Outcome: You identify whether it's a DNS, TCP, TLS, or HTTP issue and where, without needing to kubectl port-forward.
You need to roll back a Helm release. You open Radar, find the release, compare revisions, and click rollback.
Outcome: The rollout is reverted in one click, with the event timeline recording the change for audit.
Use Cases
- Debug a crashing pod by searching across clusters and rewinding the event timeline.
- Roll back a Helm release to a previous revision with one click.
- View the sync state of Argo CD applications alongside the resources they produce.
- Audit cluster compliance against 36 best-practice checks inspired by NSA/CISA guidelines.
- Probe a service's HTTP endpoint from inside the cluster when port-forward is unavailable.
- Use an AI agent (Claude, Cursor) to query your cluster via MCP without kubectl.
- Trace network path and identify the first broken hop for a service during an outage.
- Check cost and rightsizing recommendations for a workload before scaling.
Models Under the Hood
as of 2026-08-27
Limitations
- Radar OSS is free and unlimited, but the Cloud tier adds fleet views and persistent retention.
- The Cloud Free tier supports up to three connected clusters with 24-hour timeline retention.
- AI investigations are read-only and may require your own agent CLI.
- No APM features; it's a visibility tool, not a monitoring replacement.
as of 2026-08-23
Verification history
We have re-verified Radar 6 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Radar tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Self-host OSS
$0
Ideal for
Single teams or individuals who want full features with no cloud dependency and are comfortable running the binary themselves.
What this tier adds
Free forever, runs in your cluster, no account or cloud; includes all core product features.
Cloud Free
$0
Ideal for
Small teams exploring Radar's hosted fleet view with up to 3 clusters and basic alerting.
What this tier adds
Hosted with 24-hour timeline retention, unlimited users, Google/GitHub login, Slack notifications, MCP access.
Team
$149/cluster/mo
Ideal for
Engineering teams with multiple clusters needing scoped RBAC, extended retention, and advanced alert routing.
What this tier adds
Adds unlimited clusters, scoped RBAC roles, 3-day timeline, 30-day audit retention, PagerDuty/MS Teams, advanced alert rules, fleet-wide cost rollup.
Enterprise
$299/cluster/mo
Ideal for
Organizations requiring SSO/SAML, SCIM provisioning, long audit retention, and self-hosting options.
What this tier adds
Adds SAML/OIDC SSO + SCIM 2.0, 8x Radar AI usage, 30-day timeline, 1-year audit retention and SIEM export, BYOC/self-hosted.
Custom
Annual contract
Ideal for
Regulated, air-gapped, or custom deployments that need volume pricing and dedicated support.
What this tier adds
Adds volume pricing, custom IdP, custom AI usage and model config, air-gapped deployment, 99.9% SLA and dedicated CSM.
Where the pricing makes sense
The company stage and team size where Radar's pricing actually pencils out — and where peers do it cheaper.
Radar's per-cluster pricing is fair for small to mid-size teams. OSS is free forever, and Cloud Free is great for up to 3 clusters. At $149/cluster/month, Team is competitive with Lens Enterprise, but if you have many clusters, it adds up. Compared to Datadog's per-host pricing, Radar is cheaper for Kubernetes visibility, but for heavy monitoring needs, Datadog is more comprehensive.
Setup time & first value
How long it actually takes to get something useful out of Radar — broken out by persona, not the marketing-page minute.
For OSS, install via Homebrew or curl and run against your kubeconfig in under 30 seconds. For Cloud, sign up, install the Helm chart, and connect a cluster in about 5 minutes. Time to first value is immediate, with topology and events populated in seconds.
Switching to or from Radar
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From Lens: Install Radar CLI, run 'kubectl radar' to connect to your cluster; switch your workflow to Radar's UI for topology and events.
- ↗To Lens: Export your Radar resources? Not supported, but you can run both in parallel; kubectl is always available as a fallback.
Integrations
Resources & Guides
Tutorials & Learning
Official links
Featured Head-to-Head Comparisons
Radar vs Spider Cloud
Spider Cloud and Radar serve completely different needs. Spider Cloud is the right choice if you need fast, cost-effective web data extraction for AI agents and RAG pipelines—its new Browser AI commands and 1,000+ scraper catalog make it powerful. Radar is essential if you manage Kubernetes clusters and need a modern UI with live topology, Helm tracking, GitOps visibility, and an MCP server for AI-assisted debugging. Choose based on your problem: web data or K8s operations.
Radar vs Voyage Ai
Voyage AI is the clear choice for teams needing high-accuracy, domain-specific embeddings for enterprise RAG, especially in finance or legal. Radar serves a completely different need: open-source Kubernetes debugging and observability. Your decision depends entirely on whether you're optimizing search retrieval or managing clusters.
Radar vs Temporal Ai
Choose Temporal if you need a battle-tested durable execution platform for AI agents, microservices, or long-running workflows that survive failures. Choose Radar if you're a platform engineer or on-call team that needs a fast, open-source Kubernetes UI with live topology, Helm/GitOps insights, and AI-assisted debugging. They solve orthogonal problems — the right choice depends on whether your primary pain is workflow reliability or cluster visibility.
Popular in Developer Infrastructure
Temporal AI
Durable execution platform keeping AI agents and workflows running through failures with automatic state capture and retries.
Frequently Asked Questions
Used Radar? Help shape our editorial sentiment research.