Cloud costs
The whole bill, with the Kubernetes share of every line
Group the bill by provider, service, account, region, instance type, pricing model or cluster. For every bucket, KubeOn shows how much of it ran on Kubernetes and how much did not.
Cloud cost explorer
One explorer across AWS, Azure, Google Cloud and Oracle
KubeOn reads each provider's billing export in place and normalizes it: net amortized cost, list cost and the adjustment between them. Drill from provider to service to the billed item, and switch to Outside Kubernetes to see everything that runs outside your clusters.
- AWS CUR 2.0, Azure cost exports, Google Cloud BigQuery export, OCI cost reports, FOCUS 1.x
- Billed minus list shown as its own column
- The last 3 days re-read daily for late line items
Outside Kubernetes
Everything your clusters don't claim
Outside Kubernetes lists the spend no cluster claimed, by service, region and resource count, next to the Kubernetes share of the bill. Tag rules give it an owner, so databases and queues are budgeted with the teams that use them.
- Spend outside Kubernetes and its share of the cloud bill
- Services by region and resource count
- Owners for spend outside clusters from tag rules
Infrastructure
Every node, disk and load balancer, with its capacity and bill
Infrastructure lists what ran in the window with its billed cost and time-weighted capacity: average vCPU, average memory, instance types and how many nodes were up at once. Open a node to see its hourly rate, list cost, adjustment and what ran on it.
- Nodes, disks, load balancers, network and cluster management
- Capacity chips such as 1,240 avg vCPU or m7i.2xlarge x18
- Per-node breakdown of namespaces and teams
Network cost
Data transfer, split by class and by namespace
Transfer cost is classified as NAT gateway, cross-AZ, cross-region, Transit Gateway, internet egress or inbound. With VPC flow logs, KubeOn maps flows to the namespaces on each end and prices them at your own billed rate, capped at what was billed.
- Cross-AZ counted on both sides, the way it is billed
- A namespace flow map of the costliest paths
- Unattributed transfer shown, not spread
AI and GPU spend
Model endpoints and GPU nodes next to the rest of the bill
Amazon Bedrock, Azure OpenAI and Google Vertex AI charges are grouped by model and team from your billing export, beside the GPU node pools that serve your own models. Budgets and anomaly rules work on AI spend the same way they work on clusters.
- Spend by endpoint, model and team
- GPU nodes with the time they are not doing work
- A run-rate forecast for the current month
Where the Kubernetes savings are
off the monthly bill: $21,842 a month found at our sample company
Sample company, not a customer result
Billing sources
What KubeOn reads from each provider
| Provider | Billing source | Access | Cost basis |
|---|---|---|---|
| AWS | CUR 2.0 Data Export with resource IDs and split cost allocation data, in AWS Glue | Role that reads the export and writes only Athena query results | Net amortized: Savings Plans, RIs, EDP, credits, refunds, tax |
| Microsoft Azure | Cost Management export (amortized or FOCUS) to a storage account | Managed identity with Storage Blob Data Reader and Cost Management Reader | Amortized, reservations and savings plans included |
| Google Cloud | Cloud Billing detailed usage export to BigQuery | Service account with BigQuery Data Viewer and Job User | Net of committed use discounts and credits |
| Oracle Cloud | Cost and usage reports in Object Storage | Read-only policy on the reports bucket | Billed cost, with list cost for comparison |
| Any provider | FOCUS 1.x files in object storage | Read access to the bucket | EffectiveCost and ListCost columns |
| Data centers | KubeOn rate cards or amortized hardware | Configured in KubeOn | Your rates, effective-dated |
Built for the bill as it really arrives
Five billing sources
AWS, Azure, Google Cloud, Oracle Cloud and FOCUS files in one model.
Net amortized cost
Discounts and commitments are already in every number.
180 days from the first connection
First connect allocates 180 days of billing, up to 366 on request. That cost history stays for the life of the workspace; the raw billing rows stay 90 days.
Unmonitored clusters
Clusters in the bill that never sent a snapshot are listed as billed, no agent.
Transfer classes
NAT, cross-AZ, cross-region, Transit Gateway and internet egress, separated.
Account and region scope
Limit ingestion to the accounts and projects that host Kubernetes.
Cloud costs: your questions answered
KubeOn
Keep exploring
Evaluate cloud costs with your team
Bring your platform and FinOps priorities. We will walk through the data, controls and evidence for your evaluation.