Skip to main content

The basics

Yes. Lumovi is free and open source under the Apache 2.0 license, on your desktop and in your cluster. There are no accounts and no telemetry. It’s made in spare time; if it saves you time, you can sponsor its development.
It’s the same app either way, so pick what fits:Plenty of teams use both. See Install the desktop app and Run it in your cluster.
No. Lumovi talks to the API server itself. It still shows the equivalent kubectl command for every change, so you can learn it, copy it or script it, and each terminal gets a kubectl that matches its cluster, for Kubernetes 1.25 or later. Nor do you need Helm: the desktop app ships with the helm it runs.
Kubernetes 1.25 or later. From 1.27, Lumovi also explains fields from the cluster’s own OpenAPI schema. When it runs in your cluster, signing in with a token needs 1.28 or later.
Yes. Lumovi reads your kubeconfig the way kubectl does, with client certificates, tokens and exec credential plugins like gke-gcloud-auth-plugin, aws eks get-token and kubelogin. If kubectl can reach a cluster with your kubeconfig, Lumovi can too. See Connecting clusters.
Lumovi is built around one question: is this cluster healthy, and if not, where should I look first? So it shows problems before everything else, sets usage against capacity, and keeps the details one click away. It’s neither a terminal nor a wall of tables.When you change something, it’s careful: it asks the cluster what you’re allowed to do, shows the kubectl command, checks edits with a dry run, and offers undo. And it’s the same app on your desktop and in your cluster, so a team can share it without installing anything.Lumovi and other Kubernetes tools sets it beside Lens, Freelens, Headlamp, k9s and the Kubernetes Dashboard, and says when each is the better pick.

Your data and your clusters

No. It reads your kubeconfig and never writes to it. A cluster you add in Lumovi goes in a file of its own, in Lumovi’s folder, and each cluster’s settings, like its name and color, are kept in Lumovi’s settings. Signing in to cloud providers is left to the tools made for it.
No. There’s no telemetry and no account. Its audit log stays on your computer. The desktop app talks to your clusters, to a few other places only when you use what needs them, like update checks and chart search, and to GitHub for the sidebar’s sponsor card, sending nothing but the request. See Privacy and security for the full list.
Lumovi needs to reach your clusters, and nothing else. Without the internet, everything works except looking for new versions, searching Artifact Hub, and fetching charts from public repositories, and the sidebar’s sponsor card is Lumovi’s own.
The server: a cluster made read-only on the page is read-only for everyone on it, and their AI assistants, and says who made it so, and when. Lumovi’s admins turn it on and off, or anyone, where there are none, and the audit log records each switch. readOnly: true makes every cluster read-only.
It’s built not to. Changes are always explicit: an action, a dialog that names the cluster and shows the command, and a confirmation. Destructive dialogs start on Cancel, and risky deletes, or anything in a cluster named like production, ask you to type the name first. For a cluster you only want to look at, turn on read-only mode. See Changing things safely.
Yes: an audit log of what was done through Lumovi, by whom, from where, and how it went, with the kubectl command for each change and how each AI assistant’s change was approved. Never Secrets’ values or tokens. The desktop app keeps yours on your computer, for 90 days. Lumovi in your cluster keeps one for the team: people see their own events, its auditors see everyone’s, and it can send them to your log collector or SIEM. Its events are chained, and Lumovi can check them.
Yes, when it runs in your cluster. Its admins say what everyone gets, give teams more where they work, and hold anyone back where it matters, like no shells or Secret values in production. Lumovi’s server holds to it, and never lets anyone do more than RBAC. Each person sees theirs in Your access. See Access for your team.
Yes. Lumovi goes through the proxy in HTTPS_PROXY, HTTP_PROXY and NO_PROXY, as kubectl and helm do, and trusts the certificate authorities your computer trusts, like the one a proxy that inspects HTTPS signs with. The desktop app takes the proxy from your shell. In your cluster, the chart’s proxy and extraCA set them. See Proxies and certificates, or for a server, Proxies and certificate authorities.
Yes, with a policy deployed by your MDM, Group Policy, Intune or configuration management: clusters read-only, AI assistants off or limited, updates left to IT, and the proxy and certificate authorities to use. What it sets is locked, and the app says “Set by your organization”. It sets what Lumovi does: what people may do in a cluster is still its RBAC’s to say.
Only what you want to do. Lumovi acts with your own credentials and RBAC, so a read-only view role is enough to look around. It asks the cluster what you may do before offering an action, and says why when you can’t. See Permissions.

Using it

Yes. The desktop app lists every context in your kubeconfig on its start screen, and the clusters you added in Lumovi, with whether each one answers. Switch between them from the cluster menu at the top of the sidebar, or with ⌘K. Each cluster remembers its own namespace, read-only setting and usage history source.Lumovi in your cluster shows the one cluster it runs in, unless you set it up as a fleet. There, a cluster’s read-only setting and usage history source are the server’s, the same for everyone.
Yes, with a fleet: one Lumovi for many clusters, private ones too. People sign in once, with single sign-on or through a proxy, and its home page sums up every cluster, the ones that need attention first. In each cluster, they see and change what their own RBAC there allows: Lumovi impersonates them, or passes their own token on.A fleet runs in a cluster with the Helm chart, or without Kubernetes, with Docker or on a platform like Sevalla. For clusters it can’t reach, an agent in each one dials out to it. See Clusters in a fleet for using one.
No. A restart, as an upgrade does, signs nobody out, and lets go of none of the AI assistants people allowed: Lumovi keeps them in a Secret of its own, each entry sealed with a key kept apart, and no cookie or token in it that works as it is. Open pages reconnect by themselves. See Across restarts.
Yes. Lists load in chunks of 500 and are paginated and virtualized, so thousands of pods stay smooth. They stop at 5,000 objects by default, with a note saying so; a label selector narrows a list on the server. Busy lists refresh less often.
Yes, every kind the cluster serves, found through API discovery. They get the columns kubectl get prints and a status read from their conditions. Plugins for popular projects (cert-manager, Argo CD, Flux, Karpenter and more) add better columns, links and actions, and give each project an entry in the sidebar, with everything it runs in one list. You can write your own plugins too. See Custom resources.
Yes, in the desktop app and on your team’s Lumovi. Lumovi has a built-in MCP server, so any AI assistant or agent that speaks MCP can read your clusters through it, and find what’s wrong. They ask before they change anything: each change is checked by the cluster, then waits in Lumovi with its diff and its kubectl command, for you to approve or reject. Lumovi has no AI of its own and needs no API key: it’s a tool your assistant uses, with your credentials, and you say what it may do, and where: what it sees, whether its changes ask you, and whether it reads Secrets’ values, env values and logs. In the desktop app, it’s off until you turn it on. On a server, assistants sign in through Lumovi in your browser, and act as you. See AI assistants, and On a server.
From a Prometheus or VictoriaMetrics in the cluster, which Lumovi finds by itself and reaches through the API server with your own credentials. Live usage comes from metrics-server. See Usage history.
Yes. Lumovi follows your system, or you can pick light or dark from the theme button at the bottom of the sidebar, or with ⌘K.

The project

Lumovi was started by Peter Kota, first as a tool for work: an app to open a cluster and know in a second whether it’s healthy. It’s developed in the open with its contributors on GitHub.
Lumovi is the same app, with a new name. Lumovi 1.0.0 has everything KubeStacks had. A few things don’t carry over:
  • Installed copies don’t update into Lumovi. Download Lumovi and install it. It’s a separate app, so KubeStacks stays until you remove it.
  • Settings start over. Your theme, read-only clusters, usage history sources and the rest stay in KubeStacks’ own folder, which Lumovi doesn’t read. Your kubeconfig is read as before.
  • Your own plugins go in ~/.lumovi/plugins instead of ~/.kubestacks/views, and start with apiVersion: lumovi.dev/v1beta1 instead of kubestacks.dev/v1alpha1. Lumovi doesn’t use a file with the old apiVersion, and lists it as not in use under All plugins.
  • Environment variables start with LUMOVI_ instead of KUBESTACKS_.
  • In your cluster, the image is ghcr.io/lumovi/lumovi and the chart oci://ghcr.io/lumovi/charts/lumovi, and the server’s settings are LUMOVI_* variables. See Install Lumovi in your cluster.
  • Report what’s wrong, or what’s missing, in an issue.
  • Add support for a tool you run. A plugin for it is YAML, checked against the tool’s CRDs, with no code to write. It’s an easy and welcome first contribution. See Included plugins for what Lumovi has, and Build from source for how to add one.
  • Contribute. Pull requests are welcome; for anything bigger than a small fix, open an issue first. See Build from source.
  • Sponsor its development on GitHub Sponsors. The desktop app has a link in Help → Sponsor Lumovi… too.
  • Star it on GitHub, so others find it.
One card above the sidebar’s footer, in the desktop app, in the web UI Lumovi serves from a cluster, and in a fleet’s hub: Lumovi’s own, “Help keep Lumovi free.”, or a sponsor’s, with their picture, one line and a link, which opens in your browser.
  • Nothing is tracked. Lumovi reads the card from GitHub, as it starts and every hour, and sends nothing but the request: no ID, no cookie, nothing about you or your clusters. It counts no views and no clicks. There’s no switch to turn it off. Without a way to GitHub, it’s Lumovi’s own card. See The sponsor card.
  • Sponsoring. The card shows one sponsor at a time. Sponsoring Lumovi is on GitHub Sponsors, where each tier says what it includes. A sponsor’s card is a change to sponsor.json in the public Lumovi/main-sponsor repository, by pull request, which merges once its check passes. Its README says what a card may be: the picture, the words and the link. It shows everywhere within the hour, with no release.
Privately, please, by email to security@lumovi.dev, or through a GitHub security advisory. See Reporting a vulnerability.
Each installer, the image and the chart is built by Lumovi’s release workflow on GitHub, which attests it, and lists what it’s made of in a bill of materials. The image and the chart are signed with cosign too. Check an installer with gh attestation verify: see Verify your download. For the image and the chart, see Check a release.