The Lens alternative that sits next to your databases.
Mongrel is a Lens alternative for Kubernetes: a desktop workbench that browses workloads, pods, services, config, storage, RBAC, and events, applies YAML, manages Helm releases and CRDs, streams metrics and logs, and execs, debugs, and port-forwards into containers. OpenLens was discontinued and Lens moved to subscription pricing; Mongrel covers the cluster surface and puts it beside the databases and terminals those clusters serve.
Linux x86-64 · macOS Apple silicon · Windows x64 and ARM64
// Why teams switch
The cluster is one stop on the trail, not the whole job.
Lens earned its audience by making Kubernetes legible, and its pricing changes and the OpenLens shutdown left a lot of engineers re-evaluating. The deeper observation is that cluster work rarely stays in the cluster: you check a pod, then query the database behind it, then SSH into a node. Mongrel treats Kubernetes as one surface in a workbench that also speaks databases, terminals, files, and containers, so the trail stays in one window.
// What ships
What Mongrel adds around the cluster.
Cluster browsing
Workloads, pods, services, config, storage, nodes, RBAC, and events in a browsable GUI, with cluster-wide status close at hand.
Day-2 operations
Metrics and logs, exec into containers, ephemeral debug containers, and port-forwarding, without dropping to a shell for every action.
YAML, Helm, and CRDs
Apply YAML directly, manage Helm releases, and work with custom resource definitions from the same surface as the built-in kinds.
Databases beside clusters
30+ database engines, from PostgreSQL to MongoDB, one tab over from the pods that run them; query the database and inspect the workload in one window.
Terminals and SSH
SSH, Mosh, Telnet, Serial, and local shells with jump hosts and tunnels, next to the clusters those servers join.
Docker and Podman
Containers, images, volumes, networks, logs, stats, exec, and a file browser for the local and remote daemons behind your images.
// Side by side
Mongrel vs Lens, feature for feature.
| Capability | Mongrel | Lens |
|---|---|---|
| Price and license | Commercial; annual plans from $99/year with a free 7-day trial; no telemetry | Lens is subscription-priced; the FreeLens fork is free |
| Project status | Actively developed commercial product | OpenLens was discontinued; Lens continues as a subscription product |
| Resource coverage | Workloads, pods, services, config, storage, RBAC, events, Helm, CRDs, YAML apply | Broad Kubernetes IDE coverage with an extension ecosystem |
| Operations | Metrics, logs, exec, debug containers, port-forwarding | Logs, exec, port-forwarding, and Prometheus-backed metrics |
| Beyond Kubernetes | 30+ database engines, SSH terminals, SFTP/SCP, Docker, Podman, and an API client | A focused Kubernetes IDE |
| Platforms | Linux x86-64, macOS Apple silicon, Windows x64 and ARM64 | Linux, macOS, and Windows |
// Honest tradeoffs
Where Lens still has the edge.
Lens has years of Kubernetes-specific polish and an extension ecosystem, and FreeLens gives you a real cluster GUI for free; Mongrel is commercial and its Kubernetes surface is younger. If all you want is a free cluster viewer, take FreeLens and be happy. Mongrel's case is consolidation: when your day crosses clusters, databases, terminals, and containers, one paid window replaces three or four separate tools.
// FAQ
Frequently asked questions.
What happened to OpenLens?
OpenLens, the open-source build of Lens, was discontinued, and Lens itself moved to subscription pricing. FreeLens is a community fork that carries the open-source codebase forward for free.
Is there a free Lens alternative?
FreeLens is free and open source, and it is the honest answer if a no-cost cluster viewer is all you need. Mongrel is commercial, starting at $99/year with a 7-day trial; its case is the integrated workbench around Kubernetes, not price.
Does Mongrel support Helm and CRDs?
Yes. Mongrel's Kubernetes surface covers Helm releases and custom resource definitions alongside built-in kinds, and you can apply YAML directly from the workbench.
Can Mongrel exec into pods and port-forward?
Yes. Mongrel supports exec into containers, ephemeral debug containers, port-forwarding, and streaming metrics and logs, next to the databases and terminals those clusters serve.
Does Mongrel replace kubectl?
No. Mongrel wraps everyday cluster operations in a GUI, but kubectl fluency still matters, and Mongrel does not try to hide the underlying resource model. Think of it as the dashboard, the database client, and the terminal agreeing to share a window.
Related guides and comparisons
The cluster, the databases, and the terminals, in one window.
7-day trial. Linux, macOS, Windows. No credit card.