Cloud Billing Analysis Tools
3 free tools · 123 reference pages · no login · nothing uploaded
These are the tools that read your own billing data, and the ones where it matters most that your file never leaves your browser. Your file is parsed by JavaScript in your browser and is never transmitted, which is a property of how the tools are built rather than a promise in a privacy policy.
The bill diff answers the most-asked question in cloud cost: why did it go up? Not just which service moved, but whether the movement came from using more or from paying more. Those two have completely different owners and completely different fixes, and a per-service total cannot tell them apart. Charges with no quantity are reported as unattributable rather than being forced into one bucket or the other.
The allocation score grades how much of your spend can actually be attributed to a team, against the FinOps Foundation's own KPI. Untaggable charges are excluded rather than counted against you, and the fix list is ranked by unallocated dollars rather than by resource count, because a hundred untagged test instances matter less than one untagged production database.
Both accept AWS CUR, GCP billing exports, and FOCUS. Both work on CSV; CUR 2.0 Parquet exports need re-exporting as CSV first.
3 tools in billing data & finops operations
Cloud Bill Diff
Why did the bill go up? Separate the rate change from the usage change.
Drop in two billing exports. AWS CUR, GCP billing export, or FOCUS, and get a per-service and per-SKU breakdown of what moved, split into how much came from using more and how much from paying more. Reads the files in your browser; nothing is uploaded.
Cost Allocation Score
Grade your tagging against the FinOps Foundation KPI, in one file drop.
Upload a billing export and get a score out of 100 for how much of your spend can actually be attributed to a team, with untaggable charges excluded rather than counted against you, and a fix list ranked by unallocated dollars, not resource count.
FOCUS 1.4 Validator
Check a billing export against FOCUS 1.4: no size cap, nothing uploaded.
Validate a FOCUS dataset against the 1.4 specification: mandatory columns, data types, nullability, allowed values and currency codes. Every finding quotes the specification line it came from. The official validator supports 1.3 and caps uploads at 10 MB; this has no cap and runs in your browser.
Reference libraries
Pages behind these tools, one per column, recipe, pattern or SKU. They are worth reading on their own and they are what the tools above check against.
Other categories
Two files compared, or every day reconciled.
Finitizer runs this analysis continuously across every account and provider, catches a rate change or a usage spike the day it happens rather than at month end, and routes each finding to the team that owns it.