Find what you pay for
and nobody uses.
Somewhere in your bill there is a disk nobody mounted and a database nobody queries. We find them — in dollars, with the command that removes each one.
The gap
Your bill and your code have never met.
Each kind of tool sees one half of the question, and the waste lives in the half neither one sees. We find it and show the evidence — without changing anything in your account.
A billing tool sees the invoice
- What EC2, RDS or ElastiCache cost this month.
- Which service grew, and by how much.
- Nothing about whether a resource is actually used.
A code tool sees the repository
- What your Terraform or CloudFormation declares.
- Whether the plan matches what is checked in.
- Nothing about what the cloud account is actually running or billing today.
The crossing finds what neither can
- A cache cluster with no CPU and no hits in 30 days (cloud.cache.idle) — a bill shows its cost, never that nothing reads it.
- A database nothing connects to (cloud.database.idle) — low CPU alone is normal, so it takes both signals together.
- A NAT gateway moving almost no traffic (cloud.nat.idle) — billed by the hour whether or not a byte crosses it.
Worth a look?
Is it worth looking at all?
Two questions we can answer without touching your account: what you spend, and what kind of thing runs there.
These are the prices the audit engine itself uses, applied to the inventory an account this size tends to carry — arithmetic on a hypothetical account, not a measurement of yours.
An account this size, running this, with nobody watching it typically carries this much idle infrastructure each month.
Only an audit gives you your actual number — your inventory could be tidier than most, or a good deal worse.
What every audit looks for
- Disks attached to nothing
- Static IPs pointing nowhere
- NAT gateways with no traffic
- Databases nothing connects to
- Load balancers with no backend
- Load balancers whose backend is failing
- Cache clusters nobody reads
- Instances that sat still
- Snapshots of volumes that are gone
- Disks on a pricier tier than they need
- Resources billing the same amount every month
- Services whose cost jumped
- Commitments bought and never used
How it works
Three steps. No write access.
Grant read-only access, or hand over the bill your provider already exports. What each step actually produces is below it.
Create a read-only role
We generate an external id and hand you the exact trust policy. One CloudFormation click. ReadOnlyAccess plus Cost Explorer — nothing else.
We inventory and read the bill
Every resource in the region you connect, plus 30 days of real spend grouped by service. No agents installed, nothing written.
You get a number
Findings ordered by dollar impact, each with the raw evidence behind it. If we cannot prove it, we mark it as uncertain instead of guessing.
Amazon Web Services
Resources, usage metrics and the real spend. Where the engine has the most mileage.
Microsoft Azure
Reader and Cost Management Reader, both read-only. Less mileage on real accounts.
Google Cloud
No service account key changes hands. The bill figure needs the BigQuery export.
The rules
Rules, not heuristics. Every one of them shipped.
Each one is code running in the engine today, and each states what it proves and what it does not. Pick one to see the finding it produces.
A volume with no instance behind it bills at full rate while serving no workload. We tell you its size and what it costs.
Example figures. The rule ids are the real ones the engine uses.
What it looks like
Your infrastructure, before and after.
A list tells you three things are idle. The drawing shows you they are wired to nothing — which is the whole reason they are waste.
Example data — the findings and figures from a real audit of our own test account
What you could remove
Today
$4.95/moVPC · vpc-producao
subnet-1a
Unassociated static IP
$3.65/mo
Orphaned snapshot
$0.50/mo
After cleanup
$0.00/moVPC · vpc-producao
subnet-1a
removing the dashed resources saves $4.95/month
What you get
One audit is a number.
Two are a direction.
The first report tells you what is wasted today. Keep auditing and the line answers the question that actually matters — whether it is going down.
Waste found
Example data
Waste opportunity
The audit is free and it is the whole finding: what is wasted, where, and how much. $29 a month adds every finding instead of the largest one, a daily check for new waste and the month-over-month comparison. Cancel any time — your reports stay yours.
Objections
Questions with real answers.
Every answer below was checked against the code before it was written. The ones we cannot answer yet say so.
- What do you put in my account?
- Nothing. No agent is installed and nothing runs inside your network — we call the provider's own read APIs from our side, and you revoke the access whenever you want. Every call is a
Describeor aGet: there is no code path that creates, modifies or deletes anything — not disabled, not behind a flag: absent. - Is the file I upload stored?
- Not the file — it is parsed in memory and discarded, never written to disk. The report it produces is saved, and it keeps the resource ids of what was found; it would be useless otherwise. So: not the bill, but yes to the ids inside the findings.
- How do I know a finding is not a false positive?
- Every finding ships with the raw evidence and a confidence level, and the engine stays quiet when it cannot prove something. A resource whose metrics we failed to read is never accused. A load balancer whose targets are still health-checking is skipped — that is a deploy, not waste.
- How long does an audit take?
- Minutes, and it scales with how much you run rather than how long you have been running. A five thousand instance account takes about three minutes.
- Where does my data live, and can I delete it?
- Your reports live on our server, and you can erase them whenever you want — there is a delete endpoint that removes every audit, finding, connected account, daily digest and queued job we hold for your organisation. It asks you to type the word, not tick a box.
- What if someone else connects the same cloud account?
- The first organisation to connect a cloud account claims it, and only that organisation can audit it or read its history. Someone else pointing at the same account is refused. Asking for a report that belongs to another organisation returns the same not found as asking for one that never existed.
- Who else uses this?
- You would be early. There are no customers to point at yet, so there are no logos and no testimonials on this page — inventing either would lose the argument this product is making.
One audit, and you stop guessing. It takes minutes.
Connect an account read-only, or upload the bill your provider already exports. Either way you get the findings with the evidence behind them.
The audit is free. The paid plan is 14 days on us, no card — read-only either way, and nothing is installed in your account.