Waste detection & scans
Waste detection scans both clouds for resources you’re paying for but not using — and prices what each one costs you to keep.
What it looks for
Section titled “What it looks for”Coverage spans the common waste categories on both clouds, including:
- Idle compute — instances and VMs that are stopped or doing nothing.
- Orphaned storage — unattached disks and volumes.
- Forgotten networking — unused public IPs, idle gateways.
- Oversized resources — instances demonstrably larger than their workload, verified against observed utilization rather than assumptions.
- Off-hours burn — resources running through nights and weekends that don’t need to.
Each finding shows the resource, its location, the waste category, severity, confidence, and an estimated monthly saving.
Running scans
Section titled “Running scans”- All plans: waste detection runs automatically as part of the scheduled scan pipeline — no action needed.
- Enterprise: scans can also be triggered on demand from the Scans page — Run All for the full pipeline (cost sync → analysis → waste → recommendations), or each scan type’s own Run button for a targeted refresh.
- Every run starts with a pre-flight connection check — if a connection can’t authenticate, the run stops with a clear message instead of half-completing.
Finding lifecycle
Section titled “Finding lifecycle”Waste findings persist across runs:
- A finding stays active while scans keep confirming it.
- It resolves when a scan confirms the resource is gone or fixed.
- You can dismiss findings that are intentional (e.g. a stopped VM kept for DR).