Last verified
Visualize Kubernetes clusters as live topology, Helm, GitOps, and traffic maps with a built-in MCP server for AI agents.
Search across every cluster from one bar, rewind the event timeline to the moment before an incident, and share a direct link to the relevant view. The topology view shows cross-namespace dependencies and live traffic without kubectl roulette across multiple contexts.
Your team manages a single small cluster and already has a working kubectl debugging workflow. Radar's value compounds with cluster count and team size.
Every Helm release history and ArgoCD or Flux sync state in one view alongside cluster resources. Roll back with a click. No separate ArgoCD UI or Helm diff tooling needed for standard release management and change auditing.
Your team uses a dedicated ArgoCD UI and Helm release management is not a pain point. Radar adds the most value when GitOps visibility is fragmented across separate tools.
The built-in MCP server gives AI agents like Claude direct access to live cluster state, workload details, and event history. The Radar website cites a benchmark where AI investigations diagnosed faults three times faster on average with Radar than with plain kubectl.
Your team is not yet using AI agents in engineering workflows. The MCP server adds no value if you are not using MCP-compatible AI tools.
Radar is a direct alternative to Lens, K8Studio, and Aptakube, with topology, resource browser, Helm, GitOps, and audit views all included at no cost. The project reached 73,000+ downloads in 2026 and 3,866 GitHub stars, reflecting broad adoption among teams managing production clusters.
You rely on Lens IDE's extension marketplace or have Lens Pro integrations that Radar does not replicate. Radar does not have a plugin extension ecosystem.
Kubernetes is designed to be queried, not understood. kubectl gives you point-in-time answers for a single engineer at a single moment, but your team manages dozens of clusters across regions, and when an alert fires at 2am nobody has time to SSH through three jump hosts and grep for pods. The typical platform team juggles five or more tools to debug a single incident: kubectl for resources, a separate dashboard for topology, another for Helm releases, yet another for GitOps state.
Kubernetes also deletes events after one hour by default, so by the time you notice something went wrong, the timeline is already gone. As AI agents become part of incident-response workflows, there is still no structured way to give them cluster context without building custom tooling on top of an already fragmented stack.
Every Deployment, Service, and Ingress rendered as a live graph with real-time traffic flows, TLS health, and cross-namespace dependencies. Two modes show the full resource hierarchy or the network traffic path. Click any node to drill into logs, events, and manifests. Auto-layout updates as the cluster changes, with filtering by namespace, resource kind, or app label.
An embedded Model Context Protocol server lets AI agents query live cluster state, topology, and workload details through any MCP-compatible client. The same data the UI shows is queryable by agents, so investigation workflows can read real cluster context without custom tooling or separate APIs. Pass --no-mcp to disable it or --mcp-read-only to restrict agents to read-only tools.
A unified timeline of Kubernetes events and resource changes retained beyond the default one-hour cluster window. Storage backends include memory, SQLite, and Postgres. Rewind to any moment before an incident to see what changed, including resource diffs showing exact replica counts and image tags.
Every Helm release in the cluster shows full revision history, value file diffs between revisions, and one-click rollback. The audit trail shows exactly what changed and when, making upgrades reversible without kubectl commands or separate Helm tooling.
ArgoCD and FluxCD integration surfaces the sync state of every Application alongside the resources it produced. Drift and sync failures appear in the same view as the rest of the cluster, with no separate ArgoCD UI required for standard GitOps visibility.
A built-in audit view runs 44 checks against your cluster configuration, covering resource hygiene, security posture, and common misconfigurations. Results surface alongside topology and resource views, so audit failures appear in context rather than in a separate security tool.
Both are Kubernetes UIs with topology visualization and resource browsing, but they diverged on licensing and deployment model. Lens moved core features behind a paid Lens Pro subscription, while Radar is Apache 2.0 with the full feature set in the OSS binary.
| Feature | Radar | Lens |
|---|---|---|
| License | Apache 2.0 | Proprietary (paid Pro tier) |
| MCP server for AI agents | Yes | No |
| Price for individuals | Free forever | Free tier + paid subscription |
| In-cluster Helm deployment | Yes | No |
Radar is the better choice for teams that need in-cluster shared deployment under an open source license, native GitOps visibility, or an MCP server for AI agent workflows. Lens still has an advantage for engineers who rely on its extension marketplace or have existing Lens Pro integrations.
K8Studio and Aptakube are commercial Kubernetes desktop UIs with polished interfaces and paid license models. Radar's primary advantages are Apache 2.0 licensing with no per-seat cost, Helm-based in-cluster deployment for team access, and the built-in MCP server. Neither K8Studio nor Aptakube offer an open source tier or an MCP endpoint.
K8Studio or Aptakube may fit better when a team wants a commercial support contract, a native desktop experience with dedicated vendor support, and does not need open source licensing or AI agent integration.
Install Radar with the quick-install script or Homebrew, then run kubectl radar.
```bash
curl -fsSL https://get.radarhq.io | sh && kubectl radar
```
For shared in-cluster deployment, Helm handles the setup.
```bash
helm repo add skyhook https://skyhook-io.github.io/helm-charts
helm install radar skyhook/radar -n radar --create-namespace
```Yes. The OSS binary is Apache 2.0 licensed and free to run on your laptop or in-cluster via Helm forever, with no feature gates. Radar Cloud (alerts, AI investigations, shared multi-user views) has a free tier for up to three clusters and paid plans above that.
No. Local mode runs on your laptop and talks to the Kubernetes API using your existing kubeconfig without installing anything on the cluster. In-cluster mode, which provides shared team access and persistent event history, deploys as a Helm chart.
Yes. Radar includes a built-in MCP server (Model Context Protocol) that any compatible AI client, including Claude, can use to query topology, workloads, events, and audit results. The same data the browser UI shows is available to agents over the MCP endpoint. Pass --no-mcp to disable it or --mcp-read-only to restrict agents to read-only tools.
Lens moved core features behind a paid Lens Pro subscription after years as a free tool. Radar covers the same categories (topology, resource browser, Helm, GitOps) under Apache 2.0 with no paid tier required for individual engineers, plus adds a built-in MCP server and native ArgoCD/Flux support. Lens still has an advantage for engineers who rely on its extension marketplace.
Yes. The OSS binary is self-contained and connects directly to the Kubernetes API with no outbound internet access required. Usage reporting is off by default. In-cluster Helm deployment also works in air-gapped environments if you mirror the container image to a private registry.
Alternative to
Unraid
Browser desktop for your self-hosted home server
Alternative to
Kedify
Event-driven Kubernetes autoscaling with 70+ scalers and scale to zero
Alternative to
Aqua Security
Scan cloud-native workloads for security issues
Alternative to
Fly.io
Zero-downtime Docker deploys to any server, no managed platform.
Alternative to
Heroku
Self-hosted PaaS: deploys any language, automatic HTTPS, zero fees.
Alternative toHeroku
Self-hosted PaaS to deploy apps and databases across multiple servers
Run Radar on your own server
Self-host Radar on a Hostinger VPS.
Deploy on HostingerFeatured
Alternative toClaude Managed Agents
Open-source agent deployment API. Self-host or use Omnara Cloud.
Alternative to
Superhuman
AI email assistant that drafts replies and clears your inbox
Alternative to
Grok Bot
AI teammates you own: your keys, your model, your machine.
The projects we add and every new guide. Free, unsubscribe any time.
Claude Code to 
OpenCode
Jira to 
Windshift
Notion to 
AppFlowy
Slack to 
Mattermost
Linear to 
GitLab
Wispr Flow to 
Handy
CapCut to 
Concat
Grok Bot to 
rakazo
Superhuman to 
Inbox Zero
Airtable to 
AITable
Muse to 
OpenClaw
GitHub Copilot to 
Cline
Datadog to 
Netdata
Microsoft Teams to 
Rocket.Chat
Pinecone to 
Qdrant
Zapier to 
n8n
Devin AI to 
OpenHands
Firebase to 
Supabase
1Password to 
KeePassXCConfluence to 
Docmost
Contentful to 
Strapi
Adobe Premiere Pro to 
Shotcut
ChatGPT to 
AnythingLLM
LangSmith to 
Langfuse
