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.
Inherited AWS to Terraform Import for Consultancies
Turns inherited AWS accounts into reviewed Terraform pull requests for consultancies.
One engineer inherited an AWS account with hundreds of resources never written as code. This tool turns them into Terraform pull requests.
The evidence
Score: 29 out of 100
- No opening found
- 25 pay or would pay
- 757 people describe it
- 43% hit it at least weekly
- 10.2K upvotes on their posts
Cloudgeni plus free aws2tf and terraform query cover imports; one-off migrations drive heavy churn.
In their words
Manual terraform import at this scale is brutal, writing HCL by hand, then reconciling state one resource at a time.
inherited an aws account with no documentation and need to understand whats in it
how do I bring existing resources into being managed by terraform? How do I organize the repository(s) of terraform files?
The tools that already cover it
- Cloudgeni: Closest rival: Import and Drift agents open pull requests for Terraform or Bicep. Each Pro seat covers 1 cloud account and 2 repos. Its import docs say it suits small groups of resources, not whole-estate runs in one pass. Enterprise lists unlimited accounts and multi-tenant access controls.
- Firefly: Does ClickOps detection (console-made resources) and automated Terraform generation, but is aimed at enterprises (NASCAR, Paramount and HPE are named customers); small firms are priced out.
- ControlMonkey: ClickOps scanner and full drift remediation start at Pro; the free tier only detects drift. Sold through sales calls with no public price.
- env0: Drift detection on every tier, but import of existing resources is not listed; it is a full deployment platform, not an account adopter.
- Spacelift: Drift detection from Starter+, no import tool listed, and the $20 000 yearly floor is steep for small firms.
- HCP Terraform (HashiCorp): Drift checks compare Terraform-managed config with live objects; its docs do not describe finding resources made outside Terraform.
- Pulumi Cloud: Cloud account discovery from Essentials and drift detection from Pro, but it moves you onto Pulumi rather than Terraform.
- Brainboard: Importing from AWS or Azure is Enterprise only and carries a separate per-resource fee.
- Free tools: aws2tf (AWS-run sample, MIT-0 license, 1 612 resource types, aims for zero-change plans); terraform query with generate-config (Terraform 1.12 or later, 100 resources per query by default); Terracognita (2.4k stars). Terraformer (14.5k stars) archived March 16, 2026; driftctl (2.7k stars) in maintenance mode; the CloudFormation IaC generator scans up to 100 000 resources but outputs CloudFormation, not Terraform.
How it was challenged
- Demand may be seeded: the wedge's two posts (Aug 17, Aug 24) and an HCP-alternatives post (Aug 19) are tool-shopping questions from accounts appearing once in our data.
- No consultancy or MSP voiced this pain; the only signal is Cloudgeni's per-account seat pricing.
- A lead engineer can run free aws2tf or terraform query, then let a coding agent loop on terraform plan until zero changes; the wedge is mostly a prompt.
- Adoption happens once per client account, so a flat $299 monthly plan sells an event as a subscription; expect cancellations after each import and little expansion.
- Cloudgeni's Enterprise tier already lists unlimited cloud accounts and multi-tenant access controls; the price gap closes with one sales call, and venture funding can ship zero-diff checks.
The pain point it solves: Complex Kubernetes Operations
Teams struggle with the time, expertise, and manual effort required to deploy, configure, and operate Kubernetes clusters and workloads.
Platform and DevOps teams
Where they talk
- r/kubernetes
- r/devops
- r/homelab
- r/selfhosted
- r/sysadmin
- r/aws
- r/sre
- r/AZURE
Tools they use today
- Kubernetes
- Docker
- Terraform
- Ansible
- EKS
- Helm
- k3s
- kubectl
Why those fall short
- Dozens of env vars, issues, docs scattered or paywalled
- runner setup feels like an afterthought, not ergonomic
- documentation very old and outdated; knowledge in devs' heads
- unknown
- definitions use other Kubernetes terms instead of plain explanations
Map of ideas
Drawing the map…





