// Kubernetes IDE & GUI for macOS · Lens, OpenLens, Freelens and k9s alternative

The Kubernetes GUI for Mac that keeps credentials off disk.

Sign in to GKE and EKS inside Krust. Tokens stay in the macOS Keychain, not in files any npm package can read, and Claude Code gets only the access you approve. Free for every engineer; Team is $59 per seat a year, not $300.

$ brew install --cask vanchonlee/tap/krust

Free, no sign-up · v1.9.0 for macOS 14+ · works with your kubeconfig, or without one · Watch the 55s tour

Krust Pods view listing pods across all namespaces, with a pod inspector showing containers, events and conditions
~160 MBRAM with 1,700 pods
< 1 scold start
0 agentsinstalled in your cluster
0 accountsneeded to start

// New in 1.9

Your kubeconfig is readable by every npm package you install.

In 2025, Shai-Hulud harvested cloud credentials during npm install, and the Nx s1ngularity release turned installed AI agents into secret hunters. Deleting ~/.kube/config doesn't help: the gcloud and AWS logins it calls are still on disk.

Credentials live in Krust, not on disk

Sign in to Google Cloud or AWS in Krust. Saved credentials sit in the data protection Keychain, readable only by Krust, with optional Touch ID. No gcloud, AWS CLI or kubeconfig file needed.

Short-lived tokens, one tab at a time

kubectl and helm in a Krust terminal tab get a token over that tab's own socket. Nothing is written to disk, and iTerm, VS Code or an npm script find no login to use.

Claude Code gets only what you grant

The agent talks to a local proxy and never holds the credential. Read-only refuses changes and hides Secret values. Ask, the default, waits for your approval. Write turns itself off after 15 minutes.

Kubernetes RBAC still applies; Krust can only narrow it. GKE and EKS sign-in are part of Pro. Claude Code security for Kubernetes → · Why kubeconfig is the problem

One tool for everyone who ships to Kubernetes

// For developers

Is my deploy working? Find out in seconds.

  • See if your rollout is healthy, without kubectl
  • Tail logs across every pod of a service at once
  • Port-forward with stable local URLs that survive restarts
  • Spot CrashLoopBackOff and read why, right next to the pod
  • Claude Code sessions that already know your cluster

// For SREs & platform teams

When it breaks, everything is in one window.

  • Troubleshoot with an AI agent that shows its evidence
  • Follow Argo CD from sync state to the resource that broke
  • Diff resources across clusters, roll back with confirmation
  • Keep GKE and EKS credentials off engineers’ disks
  • RBAC map, Trivy scans and security audit built in
  • One license key for the whole team, no cluster agent

01 / Investigate

An AI agent that shows its work.

Ask why a pod keeps restarting. Claude Code runs right beside your cluster view, reads resources, events, logs and metrics, and explains the cause with the evidence it found. When it proposes a fix, nothing runs until you approve it.

How the agent works →
Claude Code inside Krust explaining why an Argo CD Redis pod restarted, citing logs, events and node state

02 / GitOps

See what Git changed, and what it broke.

Follow an Argo CD application from sync state into its resource tree, manifests, diff, logs and revision history. Compare the same resource across clusters, then roll back with a confirmation.

Argo CD in Krust →
Krust following an Argo CD application into its resources and sync state

03 / Your way

A Mac app for some. A terminal for others.

K9r ships in the same install: a k9s-style terminal UI on the same Rust engine. GUI people and terminal people use one tool, one license, and see the same cluster state.

Meet K9r →
K9r terminal UI listing pods with keyboard shortcuts

// For platform teams

Give every engineer Pro for less than one Lens seat costs.

Krust Team is $59 per engineer per year from 10 seats. One license key, add or remove people anytime, company invoice. No cluster credentials left on laptops, AI agents limited to the access each engineer approves, and nothing to install in your clusters.

Just you? Krust is free forever, or Pro at $79/year. See all plans.

10 engineers, one year

Lens Pro$3,000
Krust Team$590
You keep$2,410

Krust vs Lens, Freelens and k9s, honestly

k9s and Freelens are great and free. Lens runs everywhere. Krust is the native Kubernetes GUI for Mac teams that want both speed and a full workspace.

KrustLensFreelens / OpenLensk9s
InterfaceNative Mac app + K9r terminalElectron desktop appElectron desktop app, open sourceTerminal
Memory, ~1,700 pods~160 MB~1,250 MB+Not measured (Electron)~750 MB
GKE/EKS credentials on diskNo, Keychain + short-lived tokensYes, kubeconfig + cloud CLI loginYes, kubeconfig + cloud CLI loginYes, kubeconfig + cloud CLI login
Free for work useYes, any company sizeUnder $10M revenue onlyYesYes
Team price / seat / year$59$300FreeFree

Compare in depth: Krust vs Lens · OpenLens & Freelens alternative · Krust vs k9s

Try it on your cluster in a minute.

$ brew install --cask vanchonlee/tap/krust

Includes Krust.app and the k9r command · or download the DMG · Release notes

Questions

Can I use Free at work?

Yes. Free has no company-size or revenue limit.

Do I still need a kubeconfig?

No. Sign in to GKE or EKS inside Krust (Pro) and remove the gcloud and AWS CLI logins. Importing kubeconfig contexts stays free.

Does any cluster data leave my Mac?

Krust talks to the Kubernetes API directly from your Mac. Claude Code reaches the cluster only through Krust’s local proxy, in the mode you choose, and uses the model provider you configure.

How is a Team license different from buying Pro?

Same features. Team is cheaper per seat, uses one key for everyone, and comes with a company invoice.