Comparison

Radar vs Lens

Q: Is there anything Lens does that Radar doesn't?

A couple of things. A bundled first-party chatbot (Lens Prism) - Radar deliberately doesn't ship one. Diagnose instead drives the agent CLI you already have, Claude Code, Codex, or Cursor, with no API key or account, against a read-only tool surface. A third-party extension marketplace - Lens has years of community extensions for niche tools; Radar's integrations are curated and compiled into the binary, so common ecosystems work out of the box but there's no plugin system for arbitrary add-ons.

Lens K8S IDE helped define the polished desktop Kubernetes IDE. Radar carries that experience into a newer operational model: the same integrated engine runs on desktop, locally, in-cluster, and through Cloud, with operational context and MCP built across the product.

Reviewed by Nadav Erell, Skyhook CEO and former Google engineer with a decade of experience across GKE and cloud infrastructure. Checked against Lens Desktop 2026.6, Teamwork, MCP, current pricing, and the lensapp/lens MIT repository on August 4, 2026. We build Radar, so treat this as a sourced vendor comparison, not an independent review. Found a mistake? Email us and we'll fix it.

TL;DR

Radar is a desktop product too - at under a third the size of Lens. It ships for macOS, Linux, and Windows, or the even smaller single native binary - about one-seventh of a Lens install - can open the same full UI locally in a browser. The same Go engine also runs as a shared in-cluster service or connects a fleet through Cloud.
The OSS story is asymmetric. Radar is Apache 2.0 with a public no-relicense pledge. The lensapp/lens repo is MIT, but Mirantis moved exec, logs, and shell proprietary in v6.3, so OpenLens shipped without them.
The deeper difference is integration. Radar connects Issues, topology, retained change evidence, GitOps, Helm, traffic, audit, and MCP through one model. Lens centers the desktop IDE, extensions, and additional Teamwork and Agents surfaces.
Pick Radar when you want one integrated operational product. Pick Lens when your team is already committed to a Lens-specific extension, Teamwork deployment, commercial workflow, or established desktop environment that you do not want to change.

The architectural split

A desktop-centered product family versus one engine in four forms.

Lens extends its desktop IDE through Teamwork, Agents, and extensions. Radar keeps the same interface and operational model as the deployment shape changes.

Lens · Desktop model

Your laptop · Lens Electron app

↓ reads ~/.kube/config (local)

Local, cloud-discovered, or Teamwork clusters

↓ direct or Cluster Connect access

Your active cluster

A mature desktop workflow with a large extension ecosystem. Teamwork adds shared discovery and access, while the Kubernetes UI remains in each engineer's desktop app.

Radar · One engine, four delivery modes

Desktop · macOS, Linux, Windows

Local · CLI or kubectl plugin + browser

In-cluster · shared URL + Kubernetes RBAC

Cloud · SSO + fleet workflows

Local and desktop modes read kubeconfig like Lens. In-cluster and Cloud modes add shared access without changing the product or operational model.

Feature by feature

How do Radar and Lens compare?

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

Radar and Lens K8S IDE feature comparison
Feature	Radar OSS (Apache 2.0) + Cloud	Lens K8S IDE Desktop · extensions · Teamwork
Project & licensing
Open-source license lensapp/lens (the OSS repo) is MIT. Lens Desktop (the product Mirantis ships) is proprietary. Mirantis kept exec/log/shell proprietary in v6.3+, so OpenLens lost those features.	Apache 2.0 (no-relicense pledge)	Proprietary Lens Desktop
Commercial use Lens Personal is free for individuals at organizations below Lens's published $10M annual revenue-or-funding threshold. Larger organizations need Plus, Pro, or Enterprise subscriptions. Lens pricing	Yes	Partial: Free with eligibility limits · otherwise paid
Pricing axis	Per cluster	Per user
Architecture
Desktop app Both provide a polished desktop Kubernetes UI. Radar combines a compiled Go core, Kubernetes informer/watch primitives, and Go's lightweight concurrency with the operating system webview; Lens bundles Electron, Chromium, and Node. Radar install docs	Strong: macOS · Linux · Windows	Strong: macOS · Linux · Windows
Current macOS footprint Approximate installed size on Apple Silicon. Radar delivers the same engine and full UI as either a single native binary that opens in your browser or a packaged desktop app. Checked August 4, 2026 against Radar v1.8.7 and Lens 2026.6. Radar v1.8.7 Lens downloads	Strong: ~100 MB native binary · ~200 MB desktop	~750 MB desktop
Local browser mode The same Radar engine can run as a CLI or kubectl plugin and serve the full UI on localhost. Radar install docs	Strong: CLI · kubectl plugin · browser UI	No
Shared in-cluster URL Radar can serve its full interface from inside a cluster. Lens Teamwork can share cluster access, but the Kubernetes UI still runs in each engineer's Lens Desktop app. Lens Cluster Connect	Strong: Radar in-cluster	No
Hosted browser workspace	Strong: Cloud	No
Multi-cluster
Clusters in one view Lens Desktop catalogs and connects to multiple clusters, including clusters shared through Teamwork. Radar Cloud adds cross-cluster aggregate views rather than only switching the active cluster. Lens Navigator	Strong: Cloud scoped fleet views	Partial: Desktop catalog + Teamwork
Cross-cluster resource search	Strong: Cloud	No
Package and application version skew Radar Cloud compares installed package versions and application versions across selected clusters. It does not provide an arbitrary field-by-field diff of whole environments. Radar fleet views	Strong: Cloud	No
History & incidents
Retained event and resource-change history Cluster events and resource changes the product itself retains for look-back - not live API state, not your monitoring stack's storage, and not a log of user actions in the product. Radar timeline	Strong: Memory · SQLite · Cloud up to 1 year	None (live state only)
Resource-change diffs	Strong: Timeline + manifest history	No
Audit log retention A record of who did what in the product, distinct from the cluster event timeline. Radar Cloud retention is 7 days on Free, 30 days on Team, and 365 days on Enterprise. Radar audit log	Strong: Cloud · 7 / 30 / 365 days	No
GitOps correlation (Argo CD + Flux) Generic CRD access is useful; typed sync status, drift, ownership, activity, and actions wired into the rest of the product is a deeper integration. Radar GitOps Lens Flux CD	Strong: Argo CD + Flux, in core	Partial: Flux only, paid tiers
Auth
Organization SSO	Strong: In-cluster OIDC · Cloud SAML/OIDC	Partial: Google/GitHub on Pro · SAML/OIDC on Enterprise
SCIM provisioning	Partial: Enterprise	Partial: Enterprise tier only
Inherits Kubernetes RBAC	Yes	Yes
Works without distributing kubeconfigs Radar's shared modes use an in-cluster ServiceAccount and per-user RBAC. Lens Teamwork Cluster Connect creates local access configuration for authorized users instead of requiring operators to distribute static kubeconfigs manually. Lens Cluster Connect	Strong: In-cluster or Cloud	Partial: Teamwork Cluster Connect
Feature surface
Resource browsing + RBAC viewer	Yes	Yes
Logs, exec, terminal Lens Desktop includes real-time logs and its Smart Terminal. OpenLens builds lost exec, logs, and shell when those features moved into proprietary Lens code.	Yes	Yes
Topology graph Radar topology	Strong: Live workload graph	Partial: Extension-dependent
Live workload-to-workload traffic + mTLS Radar traffic	Yes	No
Image filesystem viewer	Yes	No
Cost insights (OpenCost) Both require OpenCost installed in the cluster. Radar auto-detects it. Lens needs an extension.	Strong: Auto-detected	Partial: Via extension
Cluster security audit (Trivy / Kyverno) Configuration, reliability, and security findings surfaced on the affected resources - and whether that ships with the product or arrives as a separately installed, separately licensed scanner. Lens Security Center installs Trivy Operator and reports image and resource vulnerabilities, including an air-gapped vulnerability database, on premium plans. It does not cover Kyverno policy findings. Radar's checks ship in core with typed Trivy and Kyverno context. Radar cluster audit Lens Security Center	Yes	Partial: Security Center · Trivy only · premium
MCP for external AI agents What an external agent actually gets from the endpoint: a wrapper over the raw Kubernetes API, or operational context already correlated for agent use. Benchmarked against raw kubectl on 54 live-cluster faults, Radar's MCP server was more accurate and reached a correct diagnosis about four times sooner. Lens Desktop provides read-only kubectl and PromQL tools on paid tiers, across clusters connected to the desktop app while it is running. Radar provides typed diagnostic, topology, resource, GitOps, log, and RBAC-enforced operational tools, including writes where the user is authorized. Radar MCP MCP vs kubectl benchmark Lens MCP	Strong: Correlated read + write tools · 4x sooner to a correct diagnosis than kubectl	Partial: Read-only kubectl + PromQL · premium · needs the app running
Karpenter / KEDA / cert-manager / Kyverno / OpenCost / Trivy Cluster operators you install yourself. Radar detects each and renders integrated views. Lens uses extensions per integration, except Trivy, which feeds its premium Security Center rather than an extension.	Strong: Auto-detected, no extension install	Partial: Via extensions
Collaboration
Slack and webhook alerts	Strong: Cloud	No
Resource annotations visible to teammates	Strong: Cloud	No
Webhooks	Strong: Cloud	No
Invite unlimited teammates Radar prices per cluster - teammates are free. Paid Lens organization plans are per user, so each additional licensed engineer is another seat.	Yes	Partial: Paid per user
Pricing
Free tier	Strong: OSS unlimited · Cloud 3 clusters	Partial: Lens Personal · eligibility limits
Paid entry point	$149/cluster/mo (Cloud Team)	$25/user/mo Plus or Pro · $50 Enterprise
Compliance
SOC 2 attestation Radar Cloud is SOC 2 Type 2. Lens currently documents a SOC 2 Type 1 attestation. Lens compliance	Strong: Type 2 · Cloud	Partial: Type 1
Self-host / on-prem	Strong: OSS · Cloud Enterprise	Strong: Desktop is local

Project & licensing

Open-source license

lensapp/lens (the OSS repo) is MIT. Lens Desktop (the product Mirantis ships) is proprietary. Mirantis kept exec/log/shell proprietary in v6.3+, so OpenLens lost those features.

Radar: Apache 2.0 (no-relicense pledge)
Lens K8S IDE: Proprietary Lens Desktop

Commercial use

Lens Personal is free for individuals at organizations below Lens's published $10M annual revenue-or-funding threshold. Larger organizations need Plus, Pro, or Enterprise subscriptions.

Lens pricing

Radar: Yes
Lens K8S IDE: Partial: Free with eligibility limits · otherwise paid

Pricing axis

Radar: Per cluster
Lens K8S IDE: Per user

Architecture

Desktop app

Both provide a polished desktop Kubernetes UI. Radar combines a compiled Go core, Kubernetes informer/watch primitives, and Go's lightweight concurrency with the operating system webview; Lens bundles Electron, Chromium, and Node.

Radar install docs

Radar: Strong: macOS · Linux · Windows
Lens K8S IDE: Strong: macOS · Linux · Windows

Current macOS footprint

Approximate installed size on Apple Silicon. Radar delivers the same engine and full UI as either a single native binary that opens in your browser or a packaged desktop app. Checked August 4, 2026 against Radar v1.8.7 and Lens 2026.6.

Radar v1.8.7 Lens downloads

Radar: Strong: ~100 MB native binary · ~200 MB desktop
Lens K8S IDE: ~750 MB desktop

Local browser mode

The same Radar engine can run as a CLI or kubectl plugin and serve the full UI on localhost.

Radar install docs

Radar: Strong: CLI · kubectl plugin · browser UI
Lens K8S IDE: No

Shared in-cluster URL

Radar can serve its full interface from inside a cluster. Lens Teamwork can share cluster access, but the Kubernetes UI still runs in each engineer's Lens Desktop app.

Lens Cluster Connect

Radar: Strong: Radar in-cluster
Lens K8S IDE: No

Hosted browser workspace

Radar: Strong: Cloud
Lens K8S IDE: No

Multi-cluster

Clusters in one view

Lens Desktop catalogs and connects to multiple clusters, including clusters shared through Teamwork. Radar Cloud adds cross-cluster aggregate views rather than only switching the active cluster.

Lens Navigator

Radar: Strong: Cloud scoped fleet views
Lens K8S IDE: Partial: Desktop catalog + Teamwork

Cross-cluster resource search

Radar: Strong: Cloud
Lens K8S IDE: No

Package and application version skew

Radar Cloud compares installed package versions and application versions across selected clusters. It does not provide an arbitrary field-by-field diff of whole environments.

Radar fleet views

Radar: Strong: Cloud
Lens K8S IDE: No

History & incidents

Retained event and resource-change history

Cluster events and resource changes the product itself retains for look-back - not live API state, not your monitoring stack's storage, and not a log of user actions in the product.

Radar timeline

Radar: Strong: Memory · SQLite · Cloud up to 1 year
Lens K8S IDE: None (live state only)

Resource-change diffs

Radar: Strong: Timeline + manifest history
Lens K8S IDE: No

Audit log retention

A record of who did what in the product, distinct from the cluster event timeline. Radar Cloud retention is 7 days on Free, 30 days on Team, and 365 days on Enterprise.

Radar audit log

Radar: Strong: Cloud · 7 / 30 / 365 days
Lens K8S IDE: No

GitOps correlation (Argo CD + Flux)

Generic CRD access is useful; typed sync status, drift, ownership, activity, and actions wired into the rest of the product is a deeper integration.

Radar GitOps Lens Flux CD

Radar: Strong: Argo CD + Flux, in core
Lens K8S IDE: Partial: Flux only, paid tiers

Auth

Organization SSO

Radar: Strong: In-cluster OIDC · Cloud SAML/OIDC
Lens K8S IDE: Partial: Google/GitHub on Pro · SAML/OIDC on Enterprise

SCIM provisioning

Radar: Partial: Enterprise
Lens K8S IDE: Partial: Enterprise tier only

Inherits Kubernetes RBAC

Radar: Yes
Lens K8S IDE: Yes

Works without distributing kubeconfigs

Radar's shared modes use an in-cluster ServiceAccount and per-user RBAC. Lens Teamwork Cluster Connect creates local access configuration for authorized users instead of requiring operators to distribute static kubeconfigs manually.

Lens Cluster Connect

Radar: Strong: In-cluster or Cloud
Lens K8S IDE: Partial: Teamwork Cluster Connect

Feature surface

Resource browsing + RBAC viewer

Radar: Yes
Lens K8S IDE: Yes

Logs, exec, terminal

Lens Desktop includes real-time logs and its Smart Terminal. OpenLens builds lost exec, logs, and shell when those features moved into proprietary Lens code.

Radar: Yes
Lens K8S IDE: Yes

Topology graph

Radar topology

Radar: Strong: Live workload graph
Lens K8S IDE: Partial: Extension-dependent

Live workload-to-workload traffic + mTLS

Radar traffic

Radar: Yes
Lens K8S IDE: No

Image filesystem viewer

Radar: Yes
Lens K8S IDE: No

Cost insights (OpenCost)

Both require OpenCost installed in the cluster. Radar auto-detects it. Lens needs an extension.

Radar: Strong: Auto-detected
Lens K8S IDE: Partial: Via extension

Cluster security audit (Trivy / Kyverno)

Configuration, reliability, and security findings surfaced on the affected resources - and whether that ships with the product or arrives as a separately installed, separately licensed scanner. Lens Security Center installs Trivy Operator and reports image and resource vulnerabilities, including an air-gapped vulnerability database, on premium plans. It does not cover Kyverno policy findings. Radar's checks ship in core with typed Trivy and Kyverno context.

Radar cluster audit Lens Security Center

Radar: Yes
Lens K8S IDE: Partial: Security Center · Trivy only · premium

MCP for external AI agents

What an external agent actually gets from the endpoint: a wrapper over the raw Kubernetes API, or operational context already correlated for agent use. Benchmarked against raw kubectl on 54 live-cluster faults, Radar's MCP server was more accurate and reached a correct diagnosis about four times sooner. Lens Desktop provides read-only kubectl and PromQL tools on paid tiers, across clusters connected to the desktop app while it is running. Radar provides typed diagnostic, topology, resource, GitOps, log, and RBAC-enforced operational tools, including writes where the user is authorized.

Radar MCP MCP vs kubectl benchmark Lens MCP

Radar: Strong: Correlated read + write tools · 4x sooner to a correct diagnosis than kubectl
Lens K8S IDE: Partial: Read-only kubectl + PromQL · premium · needs the app running

Karpenter / KEDA / cert-manager / Kyverno / OpenCost / Trivy

Cluster operators you install yourself. Radar detects each and renders integrated views. Lens uses extensions per integration, except Trivy, which feeds its premium Security Center rather than an extension.

Radar: Strong: Auto-detected, no extension install
Lens K8S IDE: Partial: Via extensions

Collaboration

Slack and webhook alerts

Radar: Strong: Cloud
Lens K8S IDE: No

Resource annotations visible to teammates

Radar: Strong: Cloud
Lens K8S IDE: No

Webhooks

Radar: Strong: Cloud
Lens K8S IDE: No

Invite unlimited teammates

Radar prices per cluster - teammates are free. Paid Lens organization plans are per user, so each additional licensed engineer is another seat.

Radar: Yes
Lens K8S IDE: Partial: Paid per user

Pricing

Free tier

Radar: Strong: OSS unlimited · Cloud 3 clusters
Lens K8S IDE: Partial: Lens Personal · eligibility limits

Paid entry point

Radar: $149/cluster/mo (Cloud Team)
Lens K8S IDE: $25/user/mo Plus or Pro · $50 Enterprise

Compliance

SOC 2 attestation

Radar Cloud is SOC 2 Type 2. Lens currently documents a SOC 2 Type 1 attestation.

Lens compliance

Radar: Strong: Type 2 · Cloud
Lens K8S IDE: Partial: Type 1

Self-host / on-prem

Radar: Strong: OSS · Cloud Enterprise
Lens K8S IDE: Strong: Desktop is local

Lens has been around longer and has a large installed base. Radar is designed for teams that want desktop or local use plus integrated Issues, topology, timeline evidence, GitOps, Helm, traffic, audit, fleet workflows, and MCP without assembling that context from extensions or separate product surfaces.

Is there anything Lens does that Radar doesn't?

A couple of things. A bundled first-party chatbot (Lens Prism)- Radar deliberately doesn't ship one. Diagnose instead drives the agent CLI you already have, Claude Code, Codex, or Cursor, with no API key or account, against a read-only tool surface. A third-party extension marketplace- Lens has years of community extensions for niche tools; Radar's integrations are curated and compiled into the binary, so common ecosystems work out of the box but there's no plugin system for arbitrary add-ons.

More comparisons

Radar vs Freelens

The free fork of the same Lens workflow

Lens alternatives

All six options, not just ours

Migrating from Lens and OpenLens

Step-by-step, with a rollback plan

Try Radar without changing your cluster.

Choose Desktop or local mode now. Move to the Helm chart only when you want a shared URL.

$curl -fsSL https://get.radarhq.io | sh && kubectl radar

Other install methods (Krew, Scoop, .rpm, direct download) →

or try Radar Cloud free →Star on GitHub →

Apache 2.0 · No account for local use · Run Radar OSS forever