Kubius · Visualisation

See how your cluster actually connects

A list of resources doesn't show how they relate. Kubius draws the connections - deployment to replicaset to pods, service to endpoints, ingress to service - as a live dependency graph you can click straight through.

Works with Google GKE, Amazon EKS, Azure AKS, DigitalOcean, self-managed & more · macOS Sonoma (14) or later

Relationships, not just lists

Dependency graphs

See an application's resources and how they link - workloads to pods, services to endpoints, ingress to backends - laid out as a graph.

Click straight through

Click any node to jump to that resource's detail view, then back to the graph - so exploring relationships is fast.

Live

The graph reflects the live cluster, so as pods come and go the picture updates.

Cluster dashboards

Beyond a single app, cluster dashboards show node health and pressure across every namespace on one screen - customisable per cluster.

Export the picture

Export a graph as PNG or SVG to drop into a doc, a review or an incident write-up.

No agents

Built entirely from what the Kubernetes API reports - nothing to deploy into the cluster.

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

What does the visualisation show?

A live dependency graph of how resources connect - a Deployment to its ReplicaSets and pods, a Service to its endpoints, an Ingress to its backend service - so you can see an application's shape, not just a flat list.

Can I navigate from the graph?

Yes - click any node to open that resource's detail view and jump back, which makes tracing a relationship much faster than reading YAML.

Can I share a diagram?

Yes - export any graph as a PNG or SVG for docs, reviews or incident write-ups.

Do I need anything installed?

No - the graphs and dashboards are built from the Kubernetes API using your kubeconfig; there are no agents or exporters.

See your cluster as a picture