Cost Explorer shows spend. It does not find idle AWS.

Open Cost Explorer after a noisy month. You will see services, accounts, maybe a forecast. You will not see vol-0abc sitting unattached since March in a region nobody uses.

That is not a knock on AWS. Cost Explorer is a bill lens. Compute Optimizer is a rightsizing lens for a few compute families. Cost Optimization Hub rolls some of those recommendations into one console, after you opt in. Budgets shout when a number crosses a line. Trusted Advisor has cost checks, many of them gated by support plan.

None of those tools is a weekly list of wasted resources that a platform team can work, or that a CTO can forward.

What native AWS is good at

Use Cost Explorer (or a CUR in a warehouse) when you need "what did we spend, on which service, in which account." Use Compute Optimizer when you already know the instance exists and you want a smaller size. Use Budgets so someone gets paged at 80 percent.

A FinOps engineer should keep those. unusd.cloud does not replace the CUR.

Where they stop

Idle is not the same as "expensive." A small NAT with no traffic is cheap in one VPC and expensive across thirty. A detached gp3 volume never shows up as a spike. An EKS cluster on extended support looks like "EKS went up," not "this version aged out."

Compute Optimizer will not lecture you about Elastic IPs, unused VPC endpoints, old snapshots, or a SageMaker endpoint left after a demo. Cost Anomaly Detection cares about the shape of spend, not the resource that should not exist.

You also have to remember to look. Native consoles do not sit in Slack. They do not produce a leadership digest. They do not scan every region unless you click every region.

What unusd.cloud adds

A read-only IAM role. 51+ fixed rules across 30+ services and every enabled region. A weekly email. Scan alerts in Slack or Teams. The full report and Navi in the app. On Enterprise, a short org digest on Telegram.

The rules are deterministic. You can explain a finding to an auditor. Navi talks about those findings. It does not invent a volume ID.

We also surface Cost Optimization Hub recommendations when you have opted in (Enterprise), next to our own idle checks. Native insight plus the boring orphans AWS never named.

If your question is "where did the money go," stay in Cost Explorer. If your question is "what can we turn off this week," run a scan.