SaaS ideas your next customers are already looking for
100 SaaS startup ideas for the people who said they'd pay, from agency owners to dentists. Micro SaaS ideas, AI SaaS ideas and B2B SaaS ideas: find yours, build it, sign them up.
Popular:
| # | Idea |
|---|
No idea matches this filter.
Pain points in business: what people struggle with
Search the problems to solve, as people described them on Reddit and other platforms, in their own words.
Popular:
| # | Pain point |
|---|
No pain point matches this filter.
Terraform and IaC Drift
Cloud infrastructure drifts from IaC definitions, and unmanaged resources plus noisy alerts make governance and recovery unreliable at scale.
In their words
What we need is something that continuously scans across cloud accounts, surfaces resources outside IaC coverage, and ties that visibility back into the IaC workflow
If we lost an account tomorrow I do not know what percentage of our infrastructure we could rebuild from our Terraform. Probably 50-60%.
the client is paying for automation, so that's what we need to deliver
Being able to see which resources were codified, where live state disagreed with IaC, and which changes were pure clickops made decisions during the outage much less hand wavy.
The additional knowledge required was too much for engineers who were already busy with their day-to-day responsibilities.
triaging drift manually eats a huge chunk of our platform team's week
the engineering team is practically drowning in deployment patch-work and fragmented infrastructure
Having a prod stack get hard stuck halfway through a deploy with absolutely no way to abort is a massive problem.
Terraform Cloud runs drift on a schedule which collapses at 100 + workspaces.
When multiple pipelines share a throttle budget but cannot observe each other's consumption, how do you coordinate them without a central counter?
compliance overhead has gotten heavy enough that native tooling alone isn't cutting it
How do you verify that your IaC reflects your live environment well enough that a restore from it would recover your real production system?
it has caused a widespread bunch of issues as a result of Terraform failures etc
Literally, every week there is a version of that. I have no idea why or how to tackle it but it is highly prevalent across skill set and roles.
Platform, SRE, DevOps engineers
Where they talk
- r/Terraform
- r/devops
- r/AZURE
- r/aws
- r/sre
- r/googlecloud
- r/sysadmin
- r/networking
Tools they use today
- Terraform
- AWS
- OpenTofu
- Spacelift
- IaC
- Azure Policy
- CloudFormation
- GitHub
Why those fall short
- No abort, no state surgery, poor drift detection, hours-long timeouts
- account split feels excessive and profile switching is confusing
- cleanup sprints shot down as non-critical
- no separation of plan/apply roles, no repo pinning, no self-service deploy path
- small PRs pass review and tests; docs go stale
Map of ideas
Drawing the map…