Everything kubectl does, without the terminal gymnastics
Kubius speaks the Kubernetes API directly - the same as kubectl, just with a fast native UI, live lists and a command palette. Keep kubectl for scripts; reach for Kubius for everything else.
Works with Google GKE, Amazon EKS, Azure AKS, DigitalOcean, self-managed & more · macOS Sonoma (14) or later
The parts of kubectl that should be a click
Straight to the API
No kubectl in the loop - Kubius talks to the cluster API directly over TLS, with the same auth your kubeconfig already uses.
Command palette
⌘K to jump to any resource, in any namespace, across types - faster than recalling the exact get or describe incantation.
Live, not get-loops
Every list is a watch stream. Stop running get in a loop - changes land the instant they happen.
Exec into containers
Drop into a full interactive shell in any container, in its own native window - kubectl exec without the flags.
Apply YAML with a diff
Paste or edit a manifest and see a colour-coded diff before you apply - safer than apply -f and a re-read.
Logs & detail, instantly
Live-follow logs with regex and tail, and a deep detail view for every resource - no more describe piped through less.
Keep your muscle memory
It doesn't replace kubectl - it replaces the tedious parts
Scripts and CI keep using kubectl. You stop typing get pods -n … for the hundredth time.
- Copy any action as the equivalent kubectl command
- Watch streams instead of polling get
- ⌘K command palette across every resource type
- Exec, port-forward and logs in a click
- Apply manifests with a diff preview
- Nothing to install in your clusters
Simple, one-time pricing
Pay once. No subscription.
One-time licence from €49 - no subscription. 14-day free trial, no card required.
Free 14-day trial · macOS Sonoma (14) or later · No agents, nothing to install in-cluster
Questions, answered
Do I still need kubectl?
Not for Kubius - it talks to the Kubernetes API directly and never shells out to kubectl. Keep kubectl for scripts and CI; the two coexist happily.
Does it use my existing kubeconfig?
Yes. Kubius reads ~/.kube/config and uses the same contexts and auth - including the GKE, EKS and AKS exec plugins - you already have.
Can I still get kubectl commands out of it?
Yes - most actions show the equivalent kubectl command you can copy, so it's easy to script later or share with a teammate.
What does my cluster need installed?
Nothing. No agents, no Helm charts. It speaks the standard Kubernetes API; the metrics API (metrics-server) powers live charts when present.