Comments URL: https://news.ycombinator.com/item?id=47541129

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47529234

Points: 3

# Comments: 1

We've noticed a gap for small teams: getting a prototype working locally or on Vercel and Supabase is easy, but graduating to a full fledged deployment on a cloud provider is a nightmare.

If you don't have a dedicated DevOps engineer, you're usually stuck clicking around hoping that some combination of checkboxes will do the trick .

We're building Grafos V2 to act as your application's production agent.

• You provide your application, optionally tell it what you need if its not obvious (e.g. I need a special type of MLOps or custom model garden models) and choose your cloud provider.

• The agent understands the nitty-gritty details so you don't have to.

• It outputs verifiable infrastructure code, using your repository to store the source of truth.

We are opening a Closed Alpha to 100 users to test this out. If you're building anything and want your app productionized without the infrastructure headache, let us know in the comments or sign up in the link of the post

Comments URL: https://news.ycombinator.com/item?id=47510116

Points: 4

# Comments: 4

Been writing TF since 0.11 and survived the 0.12 migration. Built multi-cloud architectures (AWS B2B banking, GCP peering, Crossplane self-service). After all this time Terraform never gets much easier, you just build more complicated headaches.

Yes, Terraform is the `right` way of doing things. It allows you to review changes before applying but at the cost of being obscure. Most SWEs don't want to deal with it and even infra engineers will occasionally do some click-ops and then reconcile.

Originally, I built a tool to auto-generate architecture diagrams from Terraform code, mostly because I hated having to manually update diagrams and expected other people did as well. After releasing it and talking to early users, I realised seeing the infrastructure was an issue but it wasn't the main issue. Changing it safely was. As an SRE, I really wanted to create a tool to help devs self-serve infrastructure and to speed up infra changes without having to add another abstraction layer on top. So, we created Grafos.ai and added an agentic layer to explain and modify the code, as well as a policy management system so you can define all of your organisation's policies, automatically run them against the changes, and also update your terraform to match them easily.

We didn’t want to create an invasive and potentially destructive AI and give it to your infrastructure and we didn't want to break your development processes, so we built some ground rules into it.

* Its doesn't do arbitrary code changes, it creates PRs so you can double check your terraform before anything is applied * Zero state or secret access, so you don’t have to trust it at all, it’s just your terraform code * Live visualisation so you can instantly see actually what changes are being proposed * Natural language guardrails and policies so you can make sure all changes are in line with your organisation's guardrails and style guides.

I’d love for you to try it and tear it apart, it’s early days and we’re shipping features and changes literally everyday so any feedback good or bad would be amazing!

Comments URL: https://news.ycombinator.com/item?id=47221965

Points: 2

# Comments: 3