Every real Lens alternative.

Best for: Teams that want one shared, web-based view with topology, persistent event timeline, GitOps status, and Helm management in core

Single Go binary - brew install, kubectl radar, browser opens. No Electron, no per-user fees (per-cluster on Cloud, OSS free). The trade-off vs Lens: no desktop-IDE feel, and it's the youngest project on this list (~2.4k stars vs Lens's claimed 1M users).

Best for: Teams that want exactly Lens, without the Mirantis subscription

An actively maintained fork (~5.1k stars) that restored what OpenLens lost. If your only problem with Lens is the license, this is the shortest path - same Electron architecture, same per-laptop kubeconfig model, same single-user ergonomics.

Best for: Engineers who live in the terminal and want the fastest possible workflow

~34k stars and beloved for a reason. Keyboard-first, instant, scriptable. It is not a dashboard: no topology, no sharing a view with a teammate, no web URL. Many teams run k9s and a web UI side by side.

Best for: Teams that want a vendor-neutral, plugin-extensible dashboard under Kubernetes SIG UI governance

Now the official SIG UI recommendation (the old Kubernetes Dashboard was retired in Jan 2026). ~6.6k stars, runs in-cluster or as desktop app. Its edge is governance, not features: official plugins cover Flux, cost, and metrics, but you install and version each, and some things aren't in the official catalog at all - ArgoCD is community-only, with no service-traffic view and no persistent timeline.

Best for: Individuals who want a fast, polished, native desktop client for multiple clusters

Well-crafted commercial desktop app from a solo developer. Lighter than Lens, with polished multi-cluster UX. Same structural limits as any desktop tool: per-seat license, per-laptop kubeconfig, nothing shared, closed source.

Best for: Teams managing Docker, Swarm, and Kubernetes from one place

~38k stars, much broader than a K8s viewer - it's a full container management platform with its own RBAC layer. If you're Kubernetes-only, that breadth is overhead; if you run mixed container estates, it's the point.

Why are people looking for Lens alternatives?

Three reasons come up most: commercial use requires a paid per-user subscription since Lens 6.0; Mirantis moved exec, logs, and shell into proprietary code in v6.3 (so the OSS builds lost them); and Electron's resource usage on large clusters. None of these makes Lens a bad tool - they're just trade-offs more teams are declining to make.

What's the closest free replacement to Lens?

Freelens. It's a community fork that restored the features OpenLens lost, with the same desktop IDE experience. If you want to change as little as possible, start there. If the per-laptop desktop model itself is what you're leaving, look at Radar or Headlamp instead.

What's the best open-source Lens alternative for teams?

For a shared web view, Radar - single binary, with topology, timeline, and GitOps in core. Headlamp is the alternative if vendor-neutral SIG governance matters to you more than feature depth (you assemble the rest via plugins). For individual terminal work: k9s. Many teams run a web UI and k9s together - they solve different moments.

Is OpenLens still maintained?

OpenLens builds effectively wound down after the v6.3 feature removals; the community energy moved to Freelens, which is actively maintained. If you're on an old OpenLens build, Freelens is the natural upgrade.

Can I try Radar without installing anything in my cluster?

Yes - that's the default. brew install skyhook-io/tap/radar, then kubectl radar. It reads your current kubeconfig and opens a browser. Zero cluster-side install - nothing is deployed to the cluster unless you choose the Helm chart later.