KubeOn
One agent per cluster, one platform for every cost
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.
From the invoice to a change your team approved
KubeOn prices every workload, reconciles it to the bill and gives each cost an owner. Savings ship through your pipeline, or KubeOn applies them where you grant write access. The agent stays read-only by default.
Three ways to put savings to work
Read-only
The agent uses get, list and watch only. See every cost and saving, and change things yourself.
Pull requests
KubeOn opens them on the files that deploy each workload. Production always waits for a person.
Write access
A separate controller, granted feature by feature: rightsizing, node pools, autoscaling and live migration.
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.
Your environment, outbound only
Clusters with the KubeOn agentEKS, AKS, GKE, OpenShift, on-prem
Cloud billing exportsCUR 2.0, Azure exports, BigQuery- FOCUS files and rate cardsAny provider or data center
Metricsmetrics-server and Prometheus- Object storage you ownS3, GCS or Azure Blob, KMS-encrypted
KubeOn hub
Fully managed by UnitVane
- 1Ingest snapshots
- 2Normalize labels
- 3Allocate
- 4Reconcile
- 5Recommend
What your teams get
- Allocation and chargebackBy team, namespace or label
- Change proposalsPull requests, or applied by KubeOn
- Budgets and alertsSlack, Teams, email, webhooks
- Reports and APIScheduled, CSV, REST
- Ask KubeOnAnswers with traced figures
KubeOn modules
One cost model across every area
Every area reads the same allocations, owners and policies, so numbers agree from one page to the next.
Visibility: what it costs and who owns it
Every pod priced on max(request, usage), idle split out
The full bill, net of Savings Plans and credits
Saved views, scheduled delivery, CSV and API
Action: what to change and who approves it
Rightsizing from p95 usage, priced per month
Each saving as a reviewable patch with evidence
KubeOn applies savings for you, where you grant write access
Budgets, forecasts, alert rules and anomalies
Orphaned, released and over-sized volumes, and cheaper storage classes
Platform: answers and data you can trust
An AI reviewer for savings, proposals and anomalies
Plain-language answers, every figure traced
10 health checks and a heartbeat per cluster
Where the Kubernetes savings are
off the monthly bill: $21,842 a month found at our sample company
Sample company, not a customer result
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: a change applies from the date you choose, and days before it keep their allocation.
| 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
The agent sends a snapshot of nodes, pods, workloads, volumes, services and Karpenter NodePools to KubeOn.
As each snapshot arrives
KubeOn ingests it and checks it 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 |
| GPU cost, idle GPU time and sharing | Included | Included | Included | Rate card |
| Budgets, alerts and anomalies | Included | Included | Included | Included |
| Network transfer cost | Included | Included | Included | Rate card |
| Agent identity | Cluster token | Cluster token | Cluster token | Cluster token |
Let's get started
A 30-minute walkthrough on your own billing data, for your clouds, your clusters and your model providers.