Platform overview
One agent per cluster. One hub for every dollar.
KubeOn joins what runs in your clusters with what you are billed for, then turns the result into allocations, budgets and changes your teams can act on.
Architecture
Data moves one way: out of your clusters
The agent reads the Kubernetes API and writes a snapshot. The hub reads snapshots and billing exports. Nothing calls into your clusters.
KubeOn hub
KubeOn Cloud or self-hosted in your account
- 1Ingest snapshots
- 2Normalize labels
- 3Allocate
- 4Reconcile
- 5Recommend
Product
Eight areas, one cost model
Every area reads the same allocations, owners and policies, so numbers agree from one screen to the next.
Visibility: What it costs and who owns it
Action: What to change and who approves it
Platform: Answers and data you can trust
Data model
Owners from your labels, normalized at read time
KubeOn reads team, cost center and application from the labels you already use, then resolves spelling differences when it reads them. Nothing is re-tagged in your clusters, and mappings are effective-dated so history stays as reported.
| Label in the cluster | Resolved key |
|---|---|
| Team | team |
| team | team |
| TeamName | team |
| kubernetes.io/team | team |
| cost-center | cost_center |
| CostCenter | cost_center |
Freshness
What happens, and when
Every hour, on the hour
The agent writes a snapshot of nodes, pods, workloads, volumes and services.
20 minutes past
The hub ingests new snapshots and checks each one against its row counts.
Hourly at :50
Budgets, alert rules and anomalies are evaluated and notifications sent.
Every 30 minutes
Savings are recomputed from the latest usage and prices.
Daily
Billing is read, the last 3 days re-read for late items, and costs allocated and reconciled.
Daily, after allocation
Change proposals are regenerated, keeping every reviewed decision.
Coverage
The same product on every platform
Billing sources and identities differ by provider. What you can do with the data does not.
| Capability | AWS | Azure | Google Cloud | On-premises |
|---|---|---|---|---|
| Cost allocation on max(request, usage) | Included | Included | Included | Included |
| Reconciliation to the bill | Included | Included | Included | Rate card |
| Savings and change proposals | Included | Included | Included | Included |
| Node sizing and family changes | Karpenter, node groups | Node pools | Node pools | Node pools |
| Budgets, alerts and anomalies | Included | Included | Included | Included |
| Network transfer cost | Included | Included | Included | Rate card |
| Agent identity | IRSA or Pod Identity | Workload Identity | Workload Identity | Token or service account |
| Self-hosted hub | Terraform or Helm | Helm | Helm | Helm, air-gapped |
See your own clusters in KubeOn.
A 30-minute walkthrough on your billing data, with an engineer who has run Kubernetes cost programs.