This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Control Cloud
Live multi-cloud map and checks before terraform apply
Control Cloud reads your clouds and on-prem hosts through the provider API with read-only credentials, draws them as one live topology and checks every change against the live tenancy before apply: credentials and scope, network, hosts, template dependencies. The Terraform it generates ships to your repo and runs under your pipeline. No agents in your VMs. Free plan: 1 operator, 1 provider.
Maker here. I run infrastructure across more than one public cloud plus an on-prem rack, and the incident I kept repeating was a change that lints clean and plans clean, then fails on apply or breaks something that lives in another console: a subnet with no NAT, a template that assumes a secret nobody created, a host that stopped answering last week.
Control Cloud is what I built around that:
- One live topology, read through each provider's API with read-only credentials and refreshed on its own; no agents in your VMs. What Terraform never created is still on the map.
- Pre-deploy validation against that live state, not a static plan: credentials and their scope, network (a missing network or subnet is an error; no NAT, egress or firewall is a warning), on-prem hosts reachable, and the dependencies of the template you picked. Anything it cannot confirm is reported as informational, never as passed. It is not a policy engine, and it does not check quotas yet.
- Terraform you own: the generated HCL ships to your repository and runs under your pipeline and your credential.
- Every action lands in an immutable audit log.
Free plan: 1 operator, 1 provider. Team comes with a 7-day trial.
What I would like feedback on: which checks you would add first (IAM reach and quotas are the obvious gaps), and whether validating against live state belongs in a UI or in a plan-time hook in CI. Honest critique welcome.
No comment highlights available yet. Please check back later!
About Control Cloud on Product Hunt
“Live multi-cloud map and checks before terraform apply”
Control Cloud was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #180 on the daily leaderboard. Control Cloud reads your clouds and on-prem hosts through the provider API with read-only credentials, draws them as one live topology and checks every change against the live tenancy before apply: credentials and scope, network, hosts, template dependencies. The Terraform it generates ships to your repo and runs under your pipeline. No agents in your VMs. Free plan: 1 operator, 1 provider.
Control Cloud was featured in SaaS (45.4k followers) and Developer Tools (523.2k followers) on Product Hunt. Together, these topics include over 156.4k products, making this a competitive space to launch in.
Who hunted Control Cloud?
Control Cloud was hunted by Gonzalo Gjuka. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Control Cloud stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Maker here. I run infrastructure across more than one public cloud plus an on-prem rack, and the incident I kept repeating was a change that lints clean and plans clean, then fails on apply or breaks something that lives in another console: a subnet with no NAT, a template that assumes a secret nobody created, a host that stopped answering last week.
Control Cloud is what I built around that:
- One live topology, read through each provider's API with read-only credentials and refreshed on its own; no agents in your VMs. What Terraform never created is still on the map.
- Pre-deploy validation against that live state, not a static plan: credentials and their scope, network (a missing network or subnet is an error; no NAT, egress or firewall is a warning), on-prem hosts reachable, and the dependencies of the template you picked. Anything it cannot confirm is reported as informational, never as passed. It is not a policy engine, and it does not check quotas yet.
- Terraform you own: the generated HCL ships to your repository and runs under your pipeline and your credential.
- Every action lands in an immutable audit log.
Free plan: 1 operator, 1 provider. Team comes with a 7-day trial.
What I would like feedback on: which checks you would add first (IAM reach and quotas are the obvious gaps), and whether validating against live state belongs in a UI or in a plan-time hook in CI. Honest critique welcome.