Kubernetes cost by team and department.
Assign clusters, namespaces, workloads or volumes to a team, split shared ones by percentage, and roll teams up into departments.
Example · $48,000 / mo · 2 clusters · 47 namespaces · 1,284 workloads · 4 teams · 3 departments
attributedawaiting owner
Coverage
See how much spend has an owner.
Unassigned spend has its own line, so you can assign it by namespace, label or rule.
Total spend
$48,000
Example · per month · 2 clusters · 47 namespaces
Attributed
$45,000
From assignments, labels and rules
Awaiting owner
$3,000
Assign by namespace, label or rule
How attribution works
Assign, split, trace.
Four ways to assign. Weighted splits when teams share. Every assignment shows where it came from.
Four ways to assign
Map at any level.
Pick one. Or mix.
- 2 clusters
Cluster
Bulk-migrate every workload in a cluster
- 47 namespaces
Namespace
Every workload in a namespace at once
- 1,284 workloads
Workloads
Hand-pick deployments, statefulsets, jobs
- 218 PVs
Persistent Volumes
Storage attributed to the team that uses it
Split shared costs
Weighted, by team.
Payments
Finance
40%Growth
Marketing
35%Platform
Engineering
25%
Source of truth
Provenance, recorded.
Kubeadapt
Assigned in-app
K8s Labels
Driven by kubeadapt.io/team
Namespace
Inherited from rule
Auto-rule
Matched on workload create
Drill down
Every team gets a dashboard.
Spend, projection, run rate and workloads, broken down by category and cluster.
Every team gets one. Every department too.
Install in 5 minutes
Stop paying for unused capacity.
Free up to 100 vCPU. After that, $1.99 per vCPU per month, dropping to $0.60 at volume.