hey, yes - right now it's only deployable to our AWS shared tenancy account, but we're working on bring your own cloud and long-term we see most serious users to go towards that setup. if you're interested in plugging this into your aws account - get in touch with me here nodar@neptune.dev
LLMs are decent at writing Terraform, but Terraform wasn’t designed for agents. A tiny app change often explodes into hundreds of lines of diff across modules, IAM, networking, state.
> use AI to write terraform for me
The real problem isn’t generating config, it’s control. With vibecoded Terraform you get:
* no guardrails on what can change
* hard to review whether a diff is safe
* easy to accidentally destroy or over-permission infra
* state + implicit dependencies are brittle for autonomous edits
We built Neptune to solve those issues and eliminate as many footguns as possible. We are spending a lot of our time thinking about guardrails so you can deploy code with AI safely
I write make Terraform PR’s with Cursor daily. The Terraform Registry is easy for the agent to comprehend, HCL has been stable for years now. Good terraform linters and plugins exist. and you can pretty easily tell your agent to run and analyze terraform plans without applying.
If Cursor/CC can’t be trusted with my TF code base why should I trust your tool? The same guardrails are needed for any of those not to mention the pesky meat-based code contributors.
This looks interesting - will I be able to bring my own cloud?
hey, yes - right now it's only deployable to our AWS shared tenancy account, but we're working on bring your own cloud and long-term we see most serious users to go towards that setup. if you're interested in plugging this into your aws account - get in touch with me here nodar@neptune.dev
I don't fully get this - can't I just use AI to write terraform for me?
Short answer: you can, but it breaks down fast.
LLMs are decent at writing Terraform, but Terraform wasn’t designed for agents. A tiny app change often explodes into hundreds of lines of diff across modules, IAM, networking, state.
> use AI to write terraform for me
The real problem isn’t generating config, it’s control. With vibecoded Terraform you get: * no guardrails on what can change * hard to review whether a diff is safe * easy to accidentally destroy or over-permission infra * state + implicit dependencies are brittle for autonomous edits
We built Neptune to solve those issues and eliminate as many footguns as possible. We are spending a lot of our time thinking about guardrails so you can deploy code with AI safely
I write make Terraform PR’s with Cursor daily. The Terraform Registry is easy for the agent to comprehend, HCL has been stable for years now. Good terraform linters and plugins exist. and you can pretty easily tell your agent to run and analyze terraform plans without applying.
If Cursor/CC can’t be trusted with my TF code base why should I trust your tool? The same guardrails are needed for any of those not to mention the pesky meat-based code contributors.
Neat!
What about GCP? can my agents deploy to my GCP account using Neptune?
what's your pricing?
working on that still, for now it's completely free to use