Your kubecost estimate says one thing.
The AWS bill says another.
KubeReconcile is the one tool built purely for the reconciliation gap. Upload your CUR/FOCUS bill and a kubecost export — we attribute idle, shared, and network cost to namespaces and teams, then explain the variance in plain English.
Free tier: 1 cluster, full monthly report. No card.
From two CSVs to an answer in seconds
No agents to install. No live cloud credentials. Just the two exports you already have.
Upload two files
Your AWS/GCP CUR or FOCUS export, and a kubecost allocation export. Parsed in memory, never stored.
We reconcile the gap
The engine buckets the estimate-vs-bill variance into idle, shared, network, storage and discounts — summing exactly to the gap.
Get the narrative
A per-namespace and per-team true-cost table, plus a written explanation you can paste into a Slack thread or a budget review.
Built for the gap nobody else explains
Idle & shared cost, attributed
Nodes you pay for but no namespace requested. Control-plane fees. DaemonSets. We split the unallocated remainder back to the teams that drove it.
Network the estimate never sees
Cross-AZ traffic, NAT gateways, egress, load balancer hours — invisible in-cluster, very visible on the bill. We surface and allocate it.
Plain-English variance report
Not another dashboard. A written explanation of why the estimate diverged from the bill — the part big tools gloss over.
Kubecost shows you the estimate. We explain the difference.
The big cost tools are excellent at projecting allocation. None of them sit you down and explain, in words, why this month's bill was 40% over that projection — and which team owns the overage. That single question is the entire product.