Hey Product Hunt! 👋 Suresh here, maker of CleanCloud. Every SRE team I've spoken to has the same story: someone asks "what even is that S3 bucket?" and nobody knows. It's been there for 18 months, has no owner tag, costs $400/month, and nobody wants to delete it in case it breaks something. CleanCloud exists for exactly that moment — but before it becomes a crisis. It scans your live AWS and Azure accounts for orphaned, untagged, and inactive storage and log resources, using multiple conservative signals before flagging anything. Crucially, it tells you how confident it is (LOW / MEDIUM / HIGH) so you can triage sensibly rather than being overwhelmed by noise. Three things I was stubborn about: Read-only, always — no Delete*, no Tag*, no mutations. Ever. Zero telemetry — your cloud metadata stays in your pipeline. Nothing leaves. CI/CD native — OIDC-first auth (no stored secrets), stable exit codes, JSON/CSV output. Security teams can approve this without a fight. It's not a cost dashboard. It's not an auto-cleaner. It's the tool that gives your platform team a defensible, auditable answer to "what can we safely review for removal?" — without anyone losing sleep over it. "pipx install cleancloud" and run "cleancloud doctor" to validate your setup in under a minute. Would love to hear: what's the cloud hygiene problem that's bitten your team hardest? That's exactly what I'm building rules for next. Many Thanks Suresh

CleanCloud

Shift-left cloud hygiene for AWS & Azure

Shift-left cloud hygiene for AWS & Azure