Cost visibility, organized your way
Kubernetes costs are cluster-wide by default. You see the total bill, but not who's responsible for what. Now you can.
Create teams and departments, assign namespaces and workloads to them, and see cost breakdowns by organizational unit.
Two ways to set it up
Kubernetes labels (automatic)
If your workloads already carry team and department labels, Kubeadapt picks them up automatically. The agent reads these labels from your deployments, statefulsets, and daemonsets, and the dashboard groups costs accordingly. No manual mapping needed.
Manual setup (from the dashboard)
No labels? Create teams and departments directly from the Teams page, then assign namespaces and workloads through the UI. You can mix both approaches: let labels handle most workloads and manually assign the rest.
What you get
Per-team cost cards show monthly run rate, CPU/memory usage, workload count, and efficiency percentage. Teams are ranked by spend so the biggest cost drivers are visible immediately.
Department rollups group teams under departments. Expand any department to see which teams fall under it and how costs distribute.
Cost Explorer integration: the Cost Explorer has a dedicated Teams & Departments tab. Filter queries by team or department, and save scoped dashboards to share with team leads.
Detail pages let you drill into any team or department to see assigned namespaces, workloads, and cost trends over time.
How it works
The hierarchy: Department > Team > Namespace > Workload. When the agent sends cluster data, the backend calculates resource costs per namespace, then rolls them up into team and department totals. Costs cover CPU, memory, GPU, and storage based on actual usage.
Getting started
Go to Dashboard > Teams. If your workloads have labels, teams will already be populated. Otherwise, click "Add Team" or "Add Department" to build your org structure manually.