AWS sends the bill. We send the fix.

A read-only scan returns the exact resource, what it costs per month and the command that fixes it — or, where no safe command exists, the call to make. Not a dashboard for you to interpret.

Run a free scan read-only · no card · ~2 min
scan · 4 regions · read-only

✓ listing instances, volumes and snapshots

✓ reading CPU and I/O from CloudWatch · 90 days

✓ matching spend against list price

✓ assessing Savings Plan coverage

✓ checking log and snapshot retention

✓ assembling the statement

31 checks · 10 services · none of them writes anything

Recoverable this account

Example
Idle Elastic IP eipalloc-0f3a9c · sa-east-1 $3.60
5 orphaned EBS volumes vol-04b1e7 ×5 · sa-east-1 $22.15
the fix · 3 commands
aws ec2 delete-volume --volume-id vol-04b1e77c  # $8.00
aws ec2 delete-volume --volume-id vol-0a91c3f2  # $7.15
aws ec2 delete-volume --volume-id vol-0ff2d1c8  # $7.00
Graviton-ready instances m5.large ×3 · us-east-1 $58.20
Total recoverable / mo $175.42

Example. The scan is read-only; the statement carries the command where a safe one exists, and the decision where it doesn't.

Proof from a real scan

$20,489 found per year in a real scan

106 individual findings

19 categories of waste

A mid-size, multi-region account. Aggregate figures from a real scan, run through the open-source CLI — no role created, no credentials shared. Read the case study →

31 checks, 10 services

Each one cross-references the account inventory, CloudWatch metrics and the region's list price. No sampling.

EC2 7

  • EC2 eligible for Graviton (ARM)
  • Idle EC2 instances
  • Unattached Elastic IPs
  • Elastic IPs on stopped instances
  • Previous-generation EC2 instances
  • Stopped instances still paying EBS
  • Oversized instances

RDS 6

  • RDS eligible for Graviton
  • Idle RDS databases
  • RDS databases on gp2 storage
  • Oversized databases
  • Previous-generation RDS databases
  • Old manual snapshots

EBS 6

  • Orphaned (unattached) volumes
  • gp3 paying for extra IOPS/throughput
  • Attached EBS volumes nobody uses
  • Snapshots past retention
  • gp2 volumes that should be gp3
  • io1/io2 cheaper on gp3

S3 3

  • Empty S3 buckets
  • Buckets with no lifecycle policy
  • Incomplete multipart uploads

ELB · VPC · DynamoDB 6

  • Load balancers routing to nothing
  • Low-traffic load balancers
  • NAT traffic a VPC endpoint saves
  • Orphan NAT gateways
  • Idle provisioned tables
  • Tables better on Standard-IA

Logs · Route 53 · Compute 3

  • Log groups that never expire
  • Empty hosted zones
  • Compute with no commitment

The report you get

Split between what you can run now and what needs your call. Each group opens with the commands for all of its resources, ready to paste into a terminal.

  • The exact command per resource, with its dollar value
  • An explicit warning on anything destructive
  • PDF of the full statement
See a full report →

Cost Explorer answers a different question.

It is good at what it does: showing where the money went. None of the four lines below is a flaw in it — it is simply a different job.

Cost Explorer Auditaz The question it answers Where my spend went Which spend is wasteHow much you can recover You work it out In dollars, per resource and per yearUsage × list price CloudWatch and pricing on separate screens Cross-referenced in the same checkAfter you close the tab Only looks if you open it again The monitor runs and tells you

Find out your number.

Read-only, no card. If your account is already lean, we say so — and we don't try to sell you anything.

Run a free scan

full report US$12 · monitor US$29/mo