See how traffic reaches your services
Ingress and Gateway routing is easy to misconfigure and hard to read in YAML. Kubius lays out the hosts, paths, backend services, TLS and status conditions for every route, so you can see what's actually wired up.
Works with Google GKE, Amazon EKS, Azure AKS, DigitalOcean, self-managed & more · macOS Sonoma (14) or later
Routing you can actually read
Hosts and paths, mapped
Every rule's host and path is laid out beside the service and port it routes to - no scrolling YAML to trace a route.
TLS at a glance
See which hosts are TLS-terminated and which Secret holds the certificate, so a missing cert is obvious.
Status conditions
For Gateway API resources, Kubius renders the gateway and per-listener conditions and each route's parent conditions - so you see whether it's actually accepted and programmed.
Straight to the backend
Click through from a route to the Service (and its endpoints) it points at, to confirm the target is healthy.
Live
Routes update live as they change - handy while you're rolling out a new host or path.
Ingress and Gateway API
Understands classic Ingress and the newer Gateway API (Gateway, HTTPRoute) and renders both sensibly.
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 routing resources does Kubius show?
Both classic Ingress and the Gateway API (Gateway and HTTPRoute). For each it lays out hosts, paths, backend services and ports, TLS, and the status conditions.
Can I see if a route is actually working?
Yes - Gateway API resources render their gateway, listener and parent-route conditions, so you can tell whether a route was accepted and programmed rather than just declared.
Can I trace a route to its backend?
Yes. Click through from a route to the Service it targets and on to that service's endpoints to confirm the backend is healthy.
Which clusters and controllers work?
Any cluster your kubeconfig reaches - the resources are standard Kubernetes objects, so it works regardless of your ingress controller.