Comparison

Radar vs FreeLens

FreeLens carries the Lens desktop experience forward, free and community-run. Radar rethinks the K8s UI as a single Go binary with the operations stack in core. Here's where each one wins.

TL;DR
  • Both free, both open. FreeLens is MIT, community-run, no account - the continuation of Open Lens. Radar OSS is Apache 2.0 with a public no-relicense pledge.
  • Different architecture. FreeLens = Electron desktop app per laptop, against your local kubeconfig. Radar = single Go binary, browser-native, runs local or in-cluster with a URL teammates can open.
  • Different surface. FreeLens covers the Lens IDE feature set well. Radar adds live topology, persistent event timeline, workload-to-workload traffic with mTLS, cluster audit, and ArgoCD + Flux + OpenCost + Trivy detection in core.
  • Pick FreeLens if you want exactly the Lens desktop experience, free and account-less. Pick Radar if you want a team-shareable, history-aware operations view rather than a per-laptop IDE.
Feature by feature

The full comparison.

Unmarked Radar checks ship in OSS (Apache 2.0) and Cloud. 'Cloud' tags are hosted-only.

Feature
Radar
OSS (Apache 2.0) + Cloud
FreeLens
Community fork of Open Lens · MIT
Project & licensing
License
Apache 2.0 (no-relicense pledge)
MIT
Governance
FreeLens is a community fork of Open Lens (the core of Lens Desktop), run by an independent core team. Radar is built and maintained by Skyhook (commercial OSS) under a public no-relicense pledge.
Skyhook (commercial OSS)
Independent community team
Account required
Mirantis Lens requires a Lens ID login. Neither FreeLens nor Radar OSS asks for an account.
None
None
Pricing
OSS free, Cloud per cluster
Free
Architecture
Binary
FreeLens is an Electron desktop app (Chromium + Node), installed per OS via Homebrew/Flatpak/Snap/WinGet. Radar is a single Go binary that serves the UI from one process.
Single Go binary, embedded UI
Electron desktop app
Where the engine runs
In-cluster (ServiceAccount) or local
Local kubeconfig, per laptop
Web URL teammates can open
Bundled kubectl + helm
Uses yours
Bundled
Hosted SaaS option
Cloud
Multi-cluster
Clusters in one view
FreeLens keeps the Lens catalog model: all your kubeconfig clusters listed, one open at a time. Radar OSS shows multiple clusters per install; Cloud folds them into one fleet view.
Cloud (fleet) · OSS (per install)
Catalog, one at a time
Cross-cluster resource search
Cloud
Drift detection (staging vs prod)
Cloud
History & incidents
Event timeline retention
Kubernetes API holds events for ~1 hour by default. FreeLens shows what's there. Radar persists past that.
Configurable, persisted
None (live state only)
Post-mortem replay
Audit log retention
Cloud · 7 days to 1 year
GitOps correlation
Radar detects ArgoCD and Flux and ties sync state into resources and the timeline, in core. FreeLens inherits the Open Lens extension ecosystem; coverage varies by extension.
ArgoCD + Flux, in core
Via community extensions
Auth
OIDC SSO
Whatever your kubeconfig does
SAML SSO
Cloud
SCIM provisioning
Enterprise
Inherits Kubernetes RBAC
Feature surface
Resource browsing
Logs, exec, terminal
Live workload-to-workload traffic + mTLS
Topology graph
Live workload graph
Image filesystem viewer
Cluster security audit (Trivy / Kyverno)
AI integration
Radar exposes the cluster as an MCP endpoint your existing Claude/Cursor/Copilot can query. FreeLens ships freelens-ai, an in-app AI extension.
MCP endpoint (use any client)
freelens-ai extension
Karpenter / KEDA / cert-manager / Kyverno / OpenCost / Trivy
Radar detects each operator and renders integrated views, no install step. FreeLens leans on extensions converted from the Open Lens ecosystem, installed one by one.
Auto-detected, no plugin install
Extension per integration
Collaboration
Slack / PagerDuty / MS Teams alerts
Cloud
Resource annotations visible to teammates
Cloud
Shareable deep-links
Free for unlimited teammates
Yes - it's the whole tool
Compliance
SOC 2 Type 2 (hosted)
Cloud
N/A - runs local
Self-host / on-prem
OSS · Cloud Enterprise
Desktop app, local only

Based on FreeLens v1.10 (June 2026) and the freelensapp/freelens repo. Something wrong? email us.

Concrete scenarios

What each tool does for the jobs that fill your week.

Coming from Lens, want the same IDE, free

FreeLens
FreeLens

That's the mission. Install FreeLens, point it at your kubeconfig, keep your muscle memory. No Lens ID.

Radar

Radar is a different shape - browser tab, not desktop IDE. Muscle memory doesn't transfer.

2am production incident

Radar
FreeLens

Open FreeLens, pick the cluster, browse to the workload, see current state. If the trigger event rolled off K8s' ~1h retention, reconstruct from logs.

Radar

Click the Radar link in the PagerDuty alert (Cloud). Rewind the timeline to before the page fired. Paste URL into the incident channel.

Show a teammate what you're seeing

Radar
FreeLens

Screenshot or screen-share. They'd need their own install + kubeconfig + extensions to reproduce it.

Radar

Paste the URL. Same topology, same filtered timeline, same resource state.

Auditor asks what changed last quarter

Radar
FreeLens

No persisted history. Reconstruct from git, kubectl history, external SIEM if you ship there.

Radar

Filter audit log by namespace + date range. Export CSV.

Why did ArgoCD just sync?

Radar
FreeLens

Open the ArgoCD UI separately, or hunt for a community extension.

Radar

Sync status, source revision, and diff inline on the resource - same for ArgoCD or Flux.

Solo engineer, laptop only, wants a desktop app

FreeLens
FreeLens

brew install freelens - a real windowed app with bundled kubectl and helm.

Radar

brew install radar, kubectl radar, browser opens. Lighter, but it's a browser tab, not a desktop window.

Fleet of 10+ clusters across environments

Radar
FreeLens

Ten catalog entries, one open at a time, per laptop.

Radar

One fleet view across all of them (Cloud), with cross-cluster search and drift detection.

Zero-vendor-risk procurement

FreeLens
FreeLens

MIT, community-run, no company behind it to change the terms.

Radar

Apache 2.0 OSS with a public no-relicense pledge - solid, but a single vendor underneath.

FAQ

Questions we get about FreeLens.

What is FreeLens, exactly?
FreeLens is a community fork of Open Lens - the open-source core of Lens Desktop - created to carry the project forward after Mirantis moved Lens to a proprietary, account-gated model. It's MIT licensed, maintained by an independent core team, and keeps the Lens IDE experience: an Electron desktop app pointed at your kubeconfig, with extension support and bundled kubectl and helm.
I loved Lens and just want it without the account. Should I use FreeLens?
Probably, yes. If what you want is exactly the Lens desktop experience - free, no Lens ID, actively maintained - FreeLens is the most direct answer, and it's good at it. Radar is a different shape of tool: browser-native, in-cluster or local, with topology, persistent timeline, traffic, GitOps, and audit built into core. Try both; they coexist fine.
Why would I pick Radar over FreeLens?
When the job goes past browsing one cluster from one laptop. Radar gives you a web URL your whole team can open, event history that survives Kubernetes' ~1-hour TTL, live traffic with mTLS state, ArgoCD/Flux correlation, cost, and a cluster audit - in core, no extensions to hunt down. FreeLens is per-laptop by design: state, kubeconfigs, and extensions live on each machine.
Is FreeLens actively maintained?
Yes. Regular releases (v1.10 in mid-2026), thousands of GitHub stars, an active core team, and many Open Lens extensions converted to its ecosystem. It's the most active of the Lens forks.
Does Radar have a desktop app like FreeLens?
Radar is a single Go binary with the UI embedded. brew install, run kubectl radar, and a browser tab opens against your current kubeconfig in under 15 seconds. No Electron, no per-OS installer. If you strongly prefer a windowed desktop app, FreeLens delivers that.
Can I share what I'm seeing in FreeLens with a teammate?
Not as a link - FreeLens renders locally against your kubeconfig, so a teammate needs their own install, kubeconfig, and extensions to see the same thing. Radar serves a web UI (in-cluster OSS or Cloud), so 'look at this' is a URL paste, with annotations and shared views on Cloud.

Try Radar OSS in 30 seconds.

Single Go binary, Apache 2.0. Or use hosted Radar Cloud free for 3 clusters.

Apache 2.0 · Self-host forever · Cloud for fleet, alerts, SSO