Built and launched: GreenOps Scan CLI (free) — a local AWS scanner for finding cost and carbon waste from your terminal.
What it does:
• Runs locally with your AWS credentials
• Scans common AWS services for waste patterns (idle, oversized, underused resources)
• Produces actionable findings with estimated cost + CO2 impact
• Gives you a prioritized list of fixes, so you can act fast
Why CLI-first: I wanted something engineers can run in minutes, script in CI, and use without heavy setup.
I launched it on Product Hunt today. If this sounds useful, I’d love your feedback — and an upvote is appreciated (no pressure):
https://www.producthunt.com/products/greenops-scan
Combining cost and carbon in the same findings is interesting because both can justify fixing the same infrastructure waste for very different reasons.
From the engineers who've reacted to GreenOps Scan so far, are they primarily pulling it in because of the cost savings, the carbon visibility, or are you actually seeing both matter in the decision?
I came across GreenOps Scan and the decision to make it CLI-first caught my attention.
I’d bet “what should I actually work on next” hits harder than anyone warns you about going in. Genuinely curious how you handle that moment—gut feel, a framework, someone you call?
And if there are AI tools to help you with this, why would you use them—or why wouldn’t you?