Your agent does the work. You approve the change.
Lumovi is a Kubernetes dashboard with a built-in MCP server. Claude Code, or any MCP client, works through it as you; by default, each change waits for you.
For macOS, Windows and Linux.
One Helm chart, for your whole team.
~/shop
revision 6 · checkout:v1.13.2 · ran 9 days
Deployment · shop · 47d old
checkout
Pods
Claude Code asks
Change Deployment checkout
Deployment · shop · production Production
Why
v1.14.0 panics on start: PAYMENTS_API_KEY isn’t set. v1.13.2 ran for 9 days without a restart, so rolling back gets checkout serving again.
The cluster accepts it+1 −1 lines
Equivalent command
kubectl apply --server-side --force-conflicts --field-manager=lumovi -f checkout.yaml -n shop --context production~/shop
revision 6 · checkout:v1.13.2 · ran 9 days
Deployment · shop · 47d old
checkout
Pods
Claude Code asks
Change Deployment checkout
Deployment · shop · production Production
Why
v1.14.0 panics on start: PAYMENTS_API_KEY isn’t set. v1.13.2 ran for 9 days without a restart, so rolling back gets checkout serving again.
The cluster accepts it+1 −1 lines
Equivalent command
kubectl apply --server-side --force-conflicts --field-manager=lumovi -f checkout.yaml -n shop --context productionClaude Code asks, the cluster checks, you approve, and it’s recorded.
Four guarantees
What holds, and how.
Never past their access
An agent acts as the person who connected it. Their RBAC applies to every request.
How: Each request reaches the API server as that person. Security
A person approves changes
By default, every change waits for a person: the diff, the agent’s reason, the kubectl command.
How: A dry run first; made only if it still does what you saw. Approvals
Rules you set
Per cluster and namespace: what agents see, whether changes ask, and whether they read Secrets or logs.
How: The strictest rule wins, setting by setting, within the administrator’s limits. Permissions
A log you can check
Every change, its approval and reason, and every tool an agent calls, each event chained to the last.
How: Each event holds the one before’s SHA-256; check it with jq. Verify
What an agent can never do.
- Go past the RBAC of the person it acts for.
- Change a read-only cluster, or where your rules say “Never”.
- Delete without asking.
- See what your rules hide: by default, Secrets’ values.
- Open a shell or a port forward, or run Helm.
The audit log
Check the log yourself.
Each audit event holds the hash of the one before it, so a changed, removed or inserted event shows. The Audit log page checks the chain for you. Keep the newest hash elsewhere, and a rewrite shows too. Or work out any event’s hash yourself:
jq -jcS 'del(.hash)' | sha256sumAll 214 events hold.
In your cluster
For your whole team, in your cluster.
Install Lumovi from one Helm chart. People sign in with single sign-on, a proxy or tokens, and their agents sign in through Lumovi as them, with nothing to copy.
- Less than RBAC, never moreAdmins give groups less than their RBAC allows, by cluster and namespace.
- Limits on every agentAdmins set limits on what agents may do that nobody’s own rules can loosen.
- One log for the teamKept on a volume in your cluster, and read by the auditors you name.
Questions your security review will ask.
- Does anything go to an AI company?
- Lumovi has no AI of its own and needs no API key. Your agent sends what it reads to its own provider, so your rules can hide Secrets, env values, logs and namespaces from it.
- What does Lumovi itself send out?
- Nothing about you or your clusters, anywhere you didn’t ask it to. No telemetry, no account. The docs list every connection it makes.
- Does Lumovi need cluster-admin?
- No. With tokens, or single sign-on that passes people’s tokens on, its service account may do nothing. Otherwise it impersonates each person, and never Kubernetes’ own users or groups.
- Is the audit log tamper-proof?
- No. It’s checkable: a changed, removed or inserted event shows. Keep the newest hash elsewhere, and a rewrite of the whole log shows too.
- How do we verify what we install?
- The macOS app is signed and notarized, the Windows app signed. Each installer has signed build provenance and a bill of materials. The image and chart are signed too.
Get started
Run in your cluster
One Helm chart. Everyone signs in as themselves.
Run in your clusterDownload
The desktop app, for macOS, Windows and Linux.
DownloadConnect your agent
Turn it on, paste one line, ask what’s failing.
Connect your agent
Get Lumovi.
Free and open source under the Apache 2.0 license, with no telemetry. Download it for your computer, or install it in your cluster for everyone on your team.
LatestVersion 1.23.2, released October 25, 2026.Release notesSHA-256 checksumsSBOM Verify your download
Every installer is on the latest GitHub release.
On your computer
It keeps itself up to date. Install the desktop appmacOS
Your systemmacOS 13 or later. Signed and notarized by Apple.
Disk images (.dmg). Also as .zip for Apple silicon and Intel, or with Homebrew:
brew install --cask lumovi/tap/lumoviWindows
Your systemWindows 10 or later, on x64 and arm64.
Signed by Open Source Developer Péter Kóta. While the certificate is new, Windows may still warn: choose More info, then Run anyway.
Linux
Your systemA recent 64-bit distribution.
Format x64 arm64 AppImage 190 MB 189 MB .deb 154 MB 147 MB .rpm 137 MB 132 MB
git clone https://github.com/Lumovi/Lumovi && cd Lumovi && npm ci && npm run dist- Kubernetes
- 1.25 or later
- kubectl
- Not needed
- Helm
- Not needed
In your cluster
Lumovi in your clusterHelm chart
Any cluster on Kubernetes 1.25 or later. Then open localhost:8080 and sign in with a token. Upgrading it later signs nobody out.
Install Lumovi in your clusterhelm install lumovi oci://ghcr.io/lumovi/charts/lumovi \ --namespace lumovi --create-namespace kubectl port-forward --namespace lumovi service/lumovi 8080:80
Then give it an address of its own, sign people in with single sign-on, harden it for production, or see every setting. The same chart runs a fleet for many clusters, and an agent in private ones. It’s on Artifact Hub, signed.
Container image
Without Kubernetes, on a machine of its own: Lumovi shows a cluster, or a fleet of them, from a kubeconfig.
Run it without Kubernetesdocker run --rm -p 8080:8080 \ -v "$PWD/kubeconfig:/kubeconfig:ro" -e KUBECONFIG=/kubeconfig \ ghcr.io/lumovi/lumovi
For linux/amd64 and arm64. Each release is signed with a build provenance attestation, which you can verify.
And a whole Kubernetes dashboard.
Every cluster, what’s failing first, and its logs, map and history a click away.







