Read-only AWS zombie-resource scanner for indie SaaS teams ($200-5k/mo spend)
A strictly read-only CLI/scan tool that finds idle EC2, EBS, load balancers and S3 waste for small AWS accounts, without asking teams to install another always-on SaaS platform.
Turn this into a build spec
One Universal Core, then the exact file layout your platform expects — CLAUDE.md, .cursor/rules, a Lovable knowledge base, a Bolt prompt under its 400-word ceiling. Evidence travels with it.
32 credits · every platform format after it is 5
Reading an open idea needs nothing. Generating a spec from it calls a model and costs real money, so it needs an account and credits — the cost is shown before you spend anything.
Building this?
Tell everyone else. It shows on this page and on the idea cards, and it collects in your dashboard. Ship it and add the link — we fetch it and re-check it weekly.
Sign in to tell others you're building this.
The full evaluation for this idea has not been generated yet. What is below is everything currently on file — we would rather show a short page than pad it.
Supporting evidence4
Multiple independent Product Hunt launches in the same 3-month window target the same complaint: teams can't see AWS waste without onboarding heavyweight SaaS, suggesting a repeatedly validated pain rather than one team's guess.
A specific underserved segment is named directly: indie hackers and small SaaS teams paying $200-5000/month, with a concrete claim of 20-30% wasted spend, which is a viable wedge for a narrow low-cost tool.
Demand signal is accelerating with fresh launches as recently as the last two days of data collection, not a dead trend.
The 'read-only, no IAM credential exposure' framing appears independently in more than one listing, indicating a shared trust objection that a narrowly-scoped scanner can address as a feature rather than a platform.
Falsifying evidence4
At least nine near-identical products already exist in this exact niche (zombie resource / idle EC2 / EBS / S3 waste scanners) launching within months of each other on the same channel, meaning any new entrant is one of a dozen, not a first mover.
All 11 signals come from a single source (Product Hunt) with no independent product database or revenue verification, so the apparent market size and momentum could be an artifact of one launch community's cycle rather than real market depth.
AWS itself ships Cost Explorer, Trusted Advisor and Compute Optimizer for free or at low cost, which already surfaces idle resources and oversized instances — the exact use case several of these tools claim to solve.
At $200-5000/month spend, savings from 20-30% waste reduction are $40-1500/month; charging enough to sustain a business against that ceiling while staying cheaper than the savings itself is a tight unit-economics window, especially competing against several similarly-priced entrants.
Most likely cause of death
The founder ships a competent read-only scanner, discovers eight other nearly identical Product Hunt launches solving the same narrow problem, and cannot differentiate on price or trust fast enough before either AWS's own tooling improves or one of the funded 'remediation' competitors (which promise to fix, not just detect) absorbs the segment. Defensibility would have to come from either automated remediation (not just detection) or a genuinely trusted read-only posture that becomes a distribution channel in itself — neither of which is evidenced here beyond marketing copy.
Demand ladder
A complaint is not a customer. Weighted ×1 / ×3 / ×8 / ×15.
Counted from clustered complaint signals. No candidate-relative commercial check was applied, so no revenue is attributed to this idea.
Verified revenue: not established for this idea. No record ties a revenue figure to a product selling what this would sell.
Momentum
Is this problem getting louder or quieter?
Saturation
How many people are already on it. Most sites hide this.
Problem evidence
Who feels this, how often, and why what they use today does not fix it.
A strictly read-only CLI/scan tool that finds idle EC2, EBS, load balancers and S3 waste for small AWS accounts, without asking teams to install another always-on SaaS platform.
Sources and freshness
Every reference opens the original post. This is the part you should check first.
How sure are we, per claim
Where the data is thin, we say so instead of rounding up.
- demand
- Medium
- payment
- Low
- market size
- Low
- competitor gap
- No data
9 references from 11 signals.
Related opportunities
Nearest by what the problem actually is, not by category label.
Zombie seat auditor for 10-50 person SaaS-heavy teams
A no-bank-connection tool that scans a small team's SaaS stack (M365, Slack, Zoom, Jira, Google Workspace) and flags unused seats and forgotten renewals so they can cancel before the next billing cycle.
Structured work-sample screening for SMB roles under 200 applicants
A hiring tool for small-business recruiters that replaces resume/ATS scoring with short, job-specific work-sample tasks to separate genuine capability from AI-polished applications.
Security scanner for Lovable/Bolt/Supabase-built apps
A pre-deployment scanner that finds exposed databases, leaked keys, and missing RLS in apps built with AI code generators, targeted at vibe-coders shipping on Lovable, Bolt, and v0.
Eleven more sections behind this one
Who signs the cheque, what the space already charges, the seven-day validation plan, and the thresholds at which you should stop. Three ideas are open in full so you can judge the depth before paying.
2 people have looked at this · 0 turned it into a spec · 0 say they're building it