srelens

srelens brings Kubernetes browsing, investigation, and operational controls together in a desktop workspace. It is best suited to SREs, platform engineers, and DevOps engineers who want to work from local kubeconfig credentials, including alongside AI agents. Its broad cluster coverage and free, open-source model make it a strong fit for local work, while production web deployments call for more security planning.

Overview

srelens connects directly to Kubernetes API servers using credentials in local kubeconfig files, with no intermediary srelens cloud service. The selected context’s credentials and RBAC permissions determine what users can do, so the interface does not grant more access than the Kubernetes account allows. Added kubeconfig files remain local; pasted configurations are stored in the application directory.

More than 40 resource kinds are in scope, including workloads, networking, storage, RBAC, admission, autoscaling, and custom resources. That breadth can make srelens a useful everyday view across different parts of a cluster, rather than a tool limited to workload status. CPU and memory metrics for nodes and pods rely on Kubernetes Metrics Server.

Key features

Live watches, log streaming, in-pod terminals, port forwarding, Helm release views, and a schema-aware YAML editor bring inspection and troubleshooting tasks into one workspace. Users can also scale or restart workloads and cordon, drain, or evict nodes. These controls make srelens more than a viewer, and requiring confirmation for destructive actions adds a practical check before consequential changes.

The built-in MCP server connects to clients such as Claude Code, Claude Desktop, Cursor, and Codex over stdio or loopback HTTP. Mutating MCP tools require an explicit confirmation argument, and the desktop HTTP server binds to loopback rather than external interfaces. That suits engineers who want AI-assisted workflows without making the desktop server externally reachable by default.

Secret values are masked by default and can be revealed per key. macOS builds are Developer ID signed and notarized; Linux assets include Tauri updater signatures. Windows code signing is on the roadmap, a consideration for organizations that require signed installers today.

Pricing

srelens is free: the Free plan costs nothing, is free to download, and has no paid tier. It is open source under the MIT license and requires neither an account nor a license key. There is no paid upgrade to unlock additional capacity or features; the trade-off is that teams seeking a paid support tier or account-based administration will need to look elsewhere.

Platforms

The desktop app supports macOS, Windows, and Linux, and supports multi-node clusters through a graphical interface. The platform coverage also includes API, web, and self-hosted deployments. For a multi-user web server, production use requires authentication, TLS termination, a stable master key, and RAM-backed storage for decrypted runtime material. That is a meaningful operational burden compared with using the desktop app, and organizations should plan for it before exposing a web deployment to a team.

Who it's for

srelens is a good match for SREs, platform engineers, DevOps engineers, and developers who want a graphical workspace for cluster inspection and operations. Its local kubeconfig access is particularly relevant to people who want cluster permissions to remain governed by Kubernetes credentials and RBAC. Teams looking for a lightweight cluster browser or operational console may value the combination of resource coverage, investigation tools, and workload actions; production web deployments suit teams prepared to manage the required security controls.

For reproducible bugs, support guidance directs users to open a GitHub issue with application log details that can be shared safely. That provides a clear route for reporting problems, though it is community issue-based rather than a paid support channel.

Pros and cons

• Pros: More than 40 resource kinds and a broad set of investigation tools make it useful across varied cluster work.
• Pros: Direct API connections use local kubeconfig credentials, while RBAC governs available actions and configuration files stay on the device.
• Pros: Workload and node operations extend beyond read-only browsing, with confirmations for destructive actions and mutating MCP calls.
• Pros: The free MIT-licensed plan has no account, license key, paid tier, or stated seat cap.
• Cons: CPU and memory metrics depend on Kubernetes Metrics Server, so they are not self-contained.
• Cons: Production multi-user web deployments require several security components and secure handling of decrypted runtime material.
• Cons: Windows code signing is not yet in place, which may matter to teams with installer-signing requirements.

Alternatives

For another free Kubernetes desktop client, compare Rancher Desktop, an open-source desktop application from SUSE's Rancher Engineering group. Choose ctlptl if a free, Apache-2.0-licensed option for Linux, macOS, or Windows better fits your needs; no usage limits or paid plans are stated for it.

Kubeterm offers a free desktop plan across macOS, Windows, and Linux without an account, trial period, or feature gates, and also supports Android and iOS. Kubeli is another free, MIT-licensed option for Linux, macOS, and Windows. Kubus is a free alternative available on Linux, macOS, Windows, and the web.

If container runtimes on macOS or Linux are the priority rather than a Kubernetes cluster workspace, consider Colima, a free MIT-licensed project. Kunobi has a free tier for up to three simultaneous clusters with community support and no sign-up, as well as a Pro plan. Kube Inspector is free and open source, with no paid tier, account, or sign-in.

See the Local Kubernetes Tools directory for more options.

Verdict

Choose srelens if you want a free, local-credential Kubernetes workspace that combines broad inspection, operational actions, and MCP connectivity. Its most compelling advantage is bringing those workflows together without routing desktop cluster access through a vendor cloud. Look elsewhere if your priority is a production multi-user web deployment without additional security operations, or if Windows code signing is a firm requirement.