Know where every cent of your cloud goes.
All your clouds in one statement as simple as your bank's, organized by cost center and reconciled with the invoice.
Every cloud and every cluster, in one statement.
- Oracle Cloud
- AWS
- Azure
- Kubernetes
- and much more…
Reads like your bank statement.
Every charge on its own line, on the day it happened, with a name you understand. No spreadsheets, no console for each cloud.
Statement
Charges from every provider, by day, with search and filters. Export to CSV, XLSX and PDF.
Reconciliation
Every cent in the statement is checked against the provider's billed total. If it doesn't match, you'll know.
Dashboard
The whole month on one screen: how much, where it went and what changed. Increases show in amber, without alarm.
Other platforms estimate. We start from the invoice.
OpenCost starts from list prices. Kubecost starts from them too and, with its billing integration, corrects them against the invoice after about 48 h. nuvem.cash starts from what your provider actually charged you, inside Kubernetes too, split by node, namespace and workload down to the last cent.
By workload
Total: R$48,230.00 = the invoice for the cluster's nodes
- checkout-apiR$9,646.00
- checkout-workerR$4,823.00
- spark-jobsR$12,057.50
- gatewayR$6,752.20
- ingressR$2,893.80
- grafana-stackR$4,823.00
- IdleR$4,823.00
- UnmonitoredR$2,411.50
Workloads plus idle plus unmonitored = the nodes' invoice. Difference: R$0.00.
Estimate, correct later or start from the invoice?
Point by point, with a source for every claim.
| Aspect | OpenCost | Kubecost | nuvem.cash |
|---|---|---|---|
| Starting point | Public list price | List price, corrected by the invoice later | Each node's invoice line |
| When it becomes an invoice number | Never, in allocation | After ~48 h; the most recent 36 h show as unreconciled | Always: the statement only shows what has been billed |
| Sum of allocations = node invoice | Not stated in the documentation | Not found in the documentation | Guaranteed to the cent, per node and per day |
| Late provider corrections | Not applicable | Reprocesses a 3 to 7 day window | Followed in any month |
| License | Apache-2.0 (CNCF) | Apache-2.0 chart; image license not stated; commercial Enterprise | Apache-2.0 agent, read-only collector |
Sources: official OpenCost and Kubecost (IBM) documentation, accessed on October 18, 2026.
Every cost to its owner. From the first month to today.
Write a rule once and it classifies your entire history, not just what comes in from now on. When you fix something by hand, your classification wins over the rule.
- By tag, namespace or account: the criteria your cloud already uses.
- A new rule reclassifies your entire history, back to the first month.
- Your manual classification always wins over the rule.
- Iftag team = datathenData & ML
- Ifnamespace = checkoutthenProduct
- Ifaccount = stagingthenEngineering
Rules apply to the workspace's entire history.
Ask. It analyzes and proposes — you approve.
The Assistant reads your costs and your tags, finds what changed and suggests rules, cost centers and reports. Nothing is applied without your click.
Custom report
Cost per team this quarter
Ask for it in one sentence or duplicate a standard report. Save it and export it to PDF.
In your cloud, we only read.
In your cloud accounts, we only read cost data. In the cluster, the open-source agent only reads your resources.
Open source agent
Apache-2.0, with a read-only collector in the cluster. You can audit every line of code.
No stored keys
AWS via assume-role, Azure via a multi-tenant app with a certificate, and OCI via a policy. Revoke it whenever you want.
Cost data only
No application logs and no data about your customers. LGPD compliant, with a named data protection officer.
A product with an engineering team behind it.
nuvem.cash is made by nuvem.online, an engineering house in Cloud & FinOps. Every number has someone who answers for it: you talk to the people who built the reconciliation, and the answer comes with the why.
- 540 of 540
days in which the Oracle Cloud statement matched the invoice, to the cent
- 23.7 M
cost lines processed
- 7
Kubernetes clusters allocated from the invoice
- 3
clouds in the same statement
Measured in production on October 18, 2026: aggregate numbers for the connected accounts and clusters.
Frequently asked questions
What's the difference between invoice cost and an estimate?
What access do you ask for in my cloud?
What about Kubernetes?
How much does it cost?
Do I need to understand FinOps?
See what your cloud really costs.
Create your account, connect a cloud and check the statement against your invoice.
Free plan, no credit card required.
