Skip to content
KubeGlass

KubeGlass vs Lens and Freelens

Lens is a desktop app for Kubernetes from Mirantis. It is free for students, hobbyists and small organizations, and organizations with more than $10 million in revenue or funding need a paid plan. Mirantis now calls it Lens K8S IDE; older pages call it Lens Desktop. Freelens is an MIT-licensed desktop app forked from Open Lens, the open-source core Lens was built on, with no account and no paid plans. KubeGlass is a web console that runs as one binary on your computer or in a cluster.

The open-source Open Lens repository is retired: its README says the open-source version “has been retired and is no longer maintained”. Freelens carries that code forward.

At a glance

Section titled “At a glance”
KubeGlass Lens Freelens
License AGPL-3.0 Proprietary, built on Open Lens (MIT) MIT
Cost Free Personal plan free for students, hobbyists and small organizations. Organizations with over $10 million in annual revenue or funding need Plus, Pro or Enterprise, from $25 per person per month billed annually Free
Account None A Lens ID, to activate the app None
Runs as A binary that opens the UI in your browser, a container, or a Helm chart in a cluster A desktop app for macOS, Windows and Linux; latest release 2026.9.181013, 18 September 2026 A desktop app for macOS, Windows and Linux on x64 and arm64; latest release v1.10.3, 7 July 2026
Shared deployment for a team Yes, one in each cluster, with each person signed in and acting as themselves No web version. Teamwork (Pro and Enterprise) gives remote access to clusters from each person’s app No
Several clusters Every kubeconfig context in one list with its problem counts; installed in a cluster, only that cluster Kubeconfig files in ~/.kube and folders you add; EKS and AKS discovery and the Hotbar need a paid plan Kubeconfig files and folders, with the catalog and Hotbar
Live updates Watches Watches Watches
Logs Merged across a workload’s pods, previous run, search One pod at a time, with a switcher for pods and containers One pod at a time; a third-party extension merges pods
Shells Pod exec, node shells (opt-in), a shell on your computer (opt-in) A built-in terminal and pod shells A terminal with bundled kubectl and Helm, pod shells, attach and node shells
Port forward Pods and Services, when KubeGlass runs on your computer Yes Yes
YAML Edit with a server-side dry run and a diff An editor; the side-by-side diff (Advanced editor) needs a paid plan An editor
Helm Releases, history, values, upgrade, rollback, uninstall, chart catalog Charts and releases, with upgrade and rollback Charts and releases, with upgrade and rollback
Argo CD and Flux Built in Built in, on paid plans Flux through an official extension; Argo CD through a third-party one
Metrics metrics-server or Prometheus, PromQL, Alertmanager alerts, rightsizing Lens Metrics installs Prometheus for you, or it uses yours; cost monitoring needs a paid plan Your Prometheus, or metrics-server
Access review An access matrix for any user, group or ServiceAccount, and who can do something Lists of roles and bindings; Security Center (paid) reports risky roles Lists of roles and bindings
Security Best-practice checks, certificates, Trivy Operator reports, images, Gatekeeper and Kyverno violations Security Center (paid), which needs the Trivy Operator Not documented
Relationships A tree on each object’s page Not documented A resource map extension
Change history Changes to workloads, Services, Ingresses, config and autoscalers, with revert after a dry run No; the editor’s revert only discards unsaved edits No
Extending it An extensions file for links, commands to copy, list columns and palette names The old extension API is no longer supported, and the current docs don’t describe a new one Extensions installed from npm
Keyboard k9s-style keys in every list, and a command palette A command palette and shortcuts A command palette and shortcuts
AI An MCP server with 41 read-only tools Ask AI and a read-only MCP server, on paid plans Extensions, such as the AI extension
Telemetry No usage telemetry; OpenTelemetry tracing to your own collector if you turn it on Usage tracking and error reports, which you can turn off in Preferences Sentry and the telemetry setting removed

Choose Lens if

Section titled “Choose Lens if”
  • You want a desktop app with commercial support from Mirantis and features such as Security Center, cost monitoring and Teamwork in one subscription.
  • Your organization already pays for Lens, or qualifies for the free Personal plan.
  • You want Lens to install a Prometheus stack in a cluster for you.
  • You prefer a desktop app to a browser tab.

Choose Freelens if

Section titled “Choose Freelens if”
  • You want a free desktop app in the Lens style, with no account.
  • You want extensions; Freelens keeps an extension system, with official extensions for Flux, a resource map and AI.
  • You work on several kubeconfig files locally and want a desktop catalog and Hotbar.

Choose KubeGlass if

Section titled “Choose KubeGlass if”
  • You want a browser UI, or one deployment for a team, where each person signs in and is limited by their own RBAC.
  • You want Argo CD, Flux, Argo Rollouts and Helm without a subscription or extensions.
  • You want logs merged across a workload’s pods, YAML diffs before applying, and change history with revert, all free.
  • You review access: who may do something, and what any user, group or ServiceAccount may do.
  • You want k9s-style keys.
  • You want an MCP server for AI clients without a paid plan.

Moving from Lens or Freelens

Section titled “Moving from Lens or Freelens”

  1. Install KubeGlass and start it. It reads ~/.kube/config, or every file in KUBECONFIG:

    Terminal window
    brew install kubeglass/tap/kubeglass
    kubeglass

  2. Lens and Freelens can also watch folders of kubeconfig files. KubeGlass reads one kubeconfig (or the files in KUBECONFIG); to add the others, paste them under Clusters › Add cluster, or have it read every kubeconfig in a folder. Either way KubeGlass merges them into the kubeconfig it reads.

  3. Clusters that sign in through an exec plugin, such as the AWS or gcloud CLI, work as they do in Lens, as long as the CLI is installed where KubeGlass runs.

  4. If you installed Lens Metrics, that Prometheus stays in the cluster. KubeGlass looks for a Prometheus with node metrics in the cluster; if it doesn’t find the one you want, set KUBEGLASS_PROMETHEUS_URL. See Security and monitoring.

  5. Lens’s Hotbar has no equivalent. Pin clusters in Clusters › All clusters and namespaces in the namespace picker.

Sources

Section titled “Sources”

Checked on 5 October 2026.