Kubius · ArgoCD

Your Argo apps and your cluster, in one native window

See every Argo Application, its sync and health status, and the resources it manages - right beside the live cluster - without port-forwarding to the Argo UI or logging in again.

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

GitOps visibility, natively

Every Application, live

All your Argo Applications in one list, watched live - sync state, health, and which are drifting or degraded, at a glance.

App to resources

Drill from an Application straight to the workloads, Services and config it manages, then into logs, events and metrics for each.

Sync & health at a glance

Synced, OutOfSync, Healthy, Degraded - surfaced where you're already working, not behind a separate dashboard tab.

No port-forward, no extra login

Argo data sits beside your cluster in the same native app - no kubectl port-forward to the Argo server, no second sign-in.

Beside everything else

GitOps view in the same window as logs, RBAC, metrics, cost and right-sizing - one tool for the whole cluster, not five.

Reads from your cluster

Kubius reads Argo's own CRDs from the cluster API over your kubeconfig - no agents, and nothing about your apps leaves the Mac.

GitOps without the tab-juggling

The Argo UI's clarity, beside the live cluster

Stop port-forwarding to the Argo dashboard just to check whether an app synced.

  • Every Argo Application, watched live
  • Sync and health status at a glance
  • Drill from app to the resources it manages
  • No port-forward, no second login
  • Beside logs, metrics, RBAC and cost
  • Reads Argo CRDs - nothing to install

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 need to port-forward to the Argo server?

No. Kubius reads Argo's Application CRDs directly from the cluster API using your kubeconfig - no port-forward and no separate Argo login.

Can I see what an Application manages?

Yes - drill from an Application into the workloads, Services and config it owns, then straight into logs, events and metrics for each.

Does it work with my existing ArgoCD install?

Yes. It reads the standard Argo Application resources already in your cluster; there's nothing extra to deploy.

Stop port-forwarding to the Argo dashboard