[candiddevmike]

Terraform is far too brittle of a tool/language to use LLMs IMO, even with guardrails. Naive changes like the kind LLMs tend to do can be catastrophic... I'm struggling to see the benefits of this product compared to more clickops-y infra LLM tools that just build out the infra without the GitHub shenanigans. I don't see a market where folks are savvy enough to understand the value of what you're doing here but unable to just have copilot or whatever generate all of this for them.

[calebtv]

Yeah Terraform does have some sharp edges, but we chose it because it's the most widely used IaC language and lets you review any changes the agent wants to make before actually applying them in your cloud. One issue with an agent making click-ops changes is there's little to no visibility into what actually changed other than going through the console to verify it yourself. Terraform also lets you do more static checks like cost estimates and policy enforcement before deploying the changes.

[candiddevmike]

So there was originally BuildFlow[0], then LaunchFlow[1], and now infra.new? How many pivots are you folks going to do? What happened to all the customers you had on these products?

0 - https://news.ycombinator.com/item?id=35169256

1- https://news.ycombinator.com/item?id=40063124

[calebtv]

This will hopefully be our last pivot :) BuildFlow never took off and we're still supporting the companies who use the LaunchFlow Python SDK.