Hi HN,
I’m a solo founder and SRE background engineer. I built CleanCloud to solve a problem I kept seeing on teams I worked with: cloud accounts slowly filling up with orphaned, unowned, or inactive resources created by elastic systems and IaC — but nobody wants tools that auto-delete things.
CleanCloud is a small, open-source CLI that:
- Scans AWS and Azure accounts in read-only mode
- Identifies potential “hygiene” issues (unattached EBS volumes, old snapshots, inactive CloudWatch logs, untagged storage, unused Azure public IPs, etc.)
- Uses conservative signals and confidence levels (HIGH / MEDIUM / LOW)
- Never deletes or modifies resources
- Is designed for review-only workflows (SRE-friendly, IaC-aware)
What it intentionally does NOT do:
- No auto-remediation
- No cost optimization / FinOps dashboards
- No agents, no SaaS, no ML
- No recommendations based on a single risky signal
This is early-stage and I’m explicitly looking for feedback from SREs / DevOps folks:
- Are these the right problems to focus on?
- Are the signals conservative enough to be trusted?
- What rules would you actually want next?
Repo (MIT licensed): https://github.com/sureshcsdp/cleancloud
If this looks useful, a helps a lot. Brutally honest feedback welcome.
Many Thanks
Suresh
