Results, savings & exports

• Each finding shows a plain-English reason (e.g. "Unattached 500 GiB gp3 volume", "Running db.r5.large is idle — no connections over up to 45 days").
• Estimated monthly savingsuses live AWS list pricing where available, with published defaults otherwise. When a specific instance type's price can't be resolved, the finding says so rather than showing a misleading $0.00.
• With cost insights enabled, a finding's cost switches from that estimate to its real spend once your Cost & Usage Report covers the resource. The Resources page tags each figure actual or estimatedso you always know which one you're looking at.
• Idle detectors report the signal behind the verdict (average CPU, lookback window, tunnel-down duration) in the finding details, so you can judge for yourself.
• The Dashboard tracks findings you've cleaned up as realized savings— when a previously flagged resource stops appearing in the next scan, it's counted as resolved.
• Export: on the Resources page, click Export CSV to download the current (filtered) findings — resource type, ID, region, account, reason, tags, and estimated savings — ready for spreadsheets or ticketing workflows.

How estimates are calculated

• Estimates use AWS on-demand list prices from the AWS Pricing API, refreshed at least daily. They do not account for Reserved Instances, Savings Plans, Spot, or private discounts — if your account has heavy commitment coverage, actual savings from deleting a resource may be lower than shown.
• Monthly figures assume a resource runs (or is stored) continuously: hourly rates are multiplied by 730 hours. These are forward-looking "what you stop paying if you remove it" numbers, not a reconstruction of past bills.
• Snapshot estimates are upper bounds. EBS and RDS snapshots are incremental, so AWS usually bills less than the full provisioned size we price them at.
• Where the Pricing API is unavailable, estimates fall back to published flat rates (e.g. $0.40/month per Secrets Manager secret); where a price genuinely can't be known (an unrecognized instance type), the finding is shown without a dollar figure instead of guessing.