You are paying for things nobody uses.

22 rules read your live inventory. The remaining 6 work from the bill alone, for accounts that would rather upload an export than connect anything.

• cloud.cache.idle

  A cache cluster with no CPU and no hits in 30 days. A bill shows its cost, never that nothing reads it.

• cloud.database.idle

  A database nothing connects to. Low CPU alone is normal, so it takes both signals together.

• cloud.nat.idle

  A NAT gateway moving almost no traffic. Billed by the hour whether or not a byte crosses it.

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. The role holds twenty-four actions, every one of them a Describe, a Get or a List. We read the name and expiry rule of a bucket, never a single object inside it. There is no code path that creates, modifies or deletes anything — not disabled, not behind a flag: absent.

I already have Cost Explorer and Trusted Advisor. Why this?

They answer a different question. Cost Explorer shows you what each service costs — it never knew what was idle. Trusted Advisor checks one AWS account at a time, and Compute Optimizer looks at compute sizing.

Most of what we find is not compute: a disk attached to nothing, a NAT gateway moving three megabytes in a month, a static IP pointing nowhere, a snapshot of a volume that no longer exists, a bucket keeping every file forever. And every finding arrives with the measurement that condemns it and the command that fixes it, across AWS and Google Cloud in one report.

If the native tools already gave you the list, you would not be reading this page.

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 long does an audit take?

It scales with how much you run, not with how long you have been running. The audit runs on a queue rather than holding your browser open, so you can close the tab and the report will be waiting when you come back.

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.