What moved your cloud bill last month?
The invoice is one number. These tools show what changed, who changed it, and what is safe to switch off.
Find it, price it, stop it
Measurement first, then the smallest safe intervention. Anything not publicly released is marked.
Find it, and price it
The bill is a sum; the cause is a change. These attribute the movement, hunt the resources that cost money while doing nothing, and put a figure on the manual work that never appears on an invoice at all.
Stop it
Halting spend is easy; halting it reversibly, with a recorded path back, is the part that makes it usable.
The papers
Every paper carries the methodology behind any number it emits, and what the tool deliberately does not do. Pick them up from the catalogue.
- Knowing what changed your cloud bill, and whya ranked diff of two Cost Explorer periods
- Stopping an AWS account's spend without losing anythinga reversible spend killswitch with a recorded restore path
- Deriving least privilege from what a role actually dida CloudTrail-to-Terraform IAM policy minimiser
- Finding cloud resources that cost money and do nothinga zombie-resource scanner with confidence scores
- Pricing CI toil in euros so it can compete for budgeta CI/CD toil analyser that prices the waste in euros
Cost and carbon are the same measurement taken twice. Cutting one usually cuts the other.
Working on this?
Tell me what you are looking at and I will tell you honestly whether any of this helps. No pitch attached, and the papers are free either way.