CloudSaver AI
Free AWS waste scanner — find 28–35% wasted cloud spend.
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.
Just me, solo dev. Spent the last few months building CloudSaver. Drop your AWS cost CSV, it runs locally and gives you a safe-delete list: what's waste, the order to delete it in, and what to check before you touch anything. No upload, no auto-delete. It's open source and free. If you want me to sanity-check your plan, I offer a $19 review. Still early. Would love feedback from anyone who's cleaned up AWS bills before. try it: https://getcloudsaver.com/?src=ih
-
1
The strongest part is the safety boundary: analyze locally, produce a deletion plan, but never auto-delete. That makes the tool useful for finding AWS waste without asking users to hand over credentials or blindly trust automation.
-
1
Thanks aryan. that was the whole point really. small teams get the same safety net the big shops have, without handing over creds or auto-deleting stuff.
-
1That’s exactly the kind of thing real developer usage should expose. I’d be interested to hear what you learn from the RC1 feedback — would you be open to sharing the best email to reach you on?
-
1
sure thing. support@getcloudsaver.com is the best one. on real usage feedback so far: mostly small stuff. grouping at 200+ resources is the open problem, not safety. would love to hear what you'd want if you ran it on your own accounts
-
-
-
-
1
Running everything locally without uploading anything is a strong trust signal for a tool that touches AWS billing data. Have you tested it against larger accounts (hundreds of resources) yet, or is it still tuned for smaller setups?
-
1
Good question. tested on a few hundred resources, no issues yet. rules get noisy at that scale though, still working on grouping. what's your setup like?
-
1
Makes sense, grouping is the hard part once volume goes up — flat rule lists don't scale past a certain point. My setup's smaller scale (backend + game logic services), but I went through the same "rules get noisy" phase with anything that fires per-resource instead of per-pattern. Curious if you're grouping by tag, by resource type, or something smarter — that's usually where these tools live or die for me
-
1
Honestly right now it's mostly resource type. tag-based is on the list but not done. i'm with you, that's where it lives or dies. / what's your game stack? curious what kind of resources you end up with at the messy end.
-
1
Node/Express + Postgres (Prisma) on the backend, Angular on the front, a handful of cron jobs driving game rounds. The messy end for us is mostly stale/orphaned state from those crons — content banks running dry, rounds that should've auto-resolved and didn't, that kind of thing. Less "unused EC2 instance" and more "background job that silently stopped doing its job." Different flavor of waste, same instinct to go hunt for it
-
1
this is the part that gets overlooked. the delete-order list is what makes cleanup safe. without it everyone just leaves it alone and the bill grows quietly. the solo dev at $40/mo is the whole pitch in one number. forgotten infra is the most expensive kind because nobody's mad enough to go hunting for it. glad it landed. if you want to poke at the actual scanner, it's here: https://getcloudsaver.com/?src=ih (free, runs in your browser, no creds). curious whether your own waste ends up more "orphaned EIPs" or "jobs that silently stopped" once you run it.
-
-
-
-
-
-
1
To add context: the scanner's main job is catching the boring waste nobody notices. orphaned elastic IPs, 90-day-old snapshots, idle load balancers. one solo dev i know was paying ~$40/mo for stuff he'd forgotten existed. the delete-order list is what makes it safe to actually clean up.
Small team, no dedicated cloud person. that's us.
last month our aws spend crept up and we couldn't pin it down. so i sat down, built a checklist, and went through it line by line. found ~$360/mo of pure waste:
- 3 unattached EBS volumes from long-dead instances (we "terminated" but the disks stayed)
- an old lambda version still getting a trickle of invokes
- a nat gateway running for an environment nobody uses anymore
- 40gb of snapshots older than a year, all from pre-launch tests
the harder part wasn't finding them. it was being scared to delete in case something broke.
so i ordered the list by risk: what to delete first, what to check before each one, and what order to do it in. that ordering was the whole game.
I'm the one who built it. your CUR file stays local, nothing leaves your machine. https://getcloudsaver.com
it's not magic. just a safe list so you're not guessing.
what's the dumbest thing you've found wasting money on aws? always curious what others have run into.
Shipped something small but useful this week: CloudSaver AI, a free scanner that takes your AWS billing CSV and shows exactly where you're wasting money — idle EC2, unattached EBS, oversized RDS, forgotten NAT gateways. A few honest notes (no hype): - It runs 100% in your browser. Your CSV never leaves your machine. No account, no credentials. - The "28–35% wasted" number is from Flexera's 2025 State of the Cloud report, not my guess. - I'm a solo maker, so the free scanner is the real product; I also offer a $19 human-reviewed audit for teams that don't want to do the fixing themselves. Why I built it: every FinOps tool I found either needed a sales call or a $45k contract. Small teams and agencies managing client AWS deserve a 10-second answer. Would love feedback from anyone here running AWS — especially on what waste patterns I'm missing. (Link in first comment.)
-
1
The interesting positioning is not competing with enterprise FinOps platforms — it's removing the first barrier for smaller teams that aren't ready for those tools.
The next challenge is turning "you are wasting money" into "here is the safest way to fix it and keep it fixed."
-
1
exactly. the second paragraph is the real product. anyone can say "you're wasting money" — trust comes from "here's exactly what to delete, in what order, and what to check first."
-
1
Glad that resonated. I enjoyed seeing how you're thinking about the problem.
I'd be interested in comparing a few more thoughts outside the thread. What's the best email to reach you on?
-
1
thanks Aryan — would love to keep the conversation going. you can DM me here on IH, or reach me through the contact link on this product page. curious to hear how teams are actually dealing with this.
-
-
-
-
1
Thanks for reading — the site link is on this product page.
Comment