what i learned cleaning up our own aws bill (and why i built a free scanner for it)

we're a tiny team running our own aws. no finops person, just us. i spent a weekend going through the bill line by line and found the usual pile of forgotten infra: unused elastic ips nobody was using, ebs volumes from instances we'd deleted months ago, a nat gateway someone forgot when we moved off a vpc, old launch configs still attached to nothing. the part that got me: most "waste scanners" want read access to your account. we didn't want to hand over creds. so i built a browser-only one. it runs the rules locally, shows you a safe-delete list (what to remove, in what order, what to check first), no upload, no api calls to your account. it's free and open: https://getcloudsaver.com/?src=ih still early but the interesting part was how much was just forgotten infra. curious what others have caught billing them — and whether a safe-delete list (vs auto-delete) is the right call for a tool like this.