Write what you want to build.
Describe the idea and answer the few questions CloudForge still has. It drafts the PRD, and you review and approve it.
Describe what you want to build. CloudForge helps you design the architecture, estimate the monthly cost and generate Terraform in your project. Review the plan, then apply it to your cloud account.
Product walkthrough. Sample project, prices illustrative.
Product walkthrough. Sample project, prices illustrative.
PRD, .cloudforge/PRD.md
Describe the idea and answer the few questions CloudForge still has. It drafts the PRD, and you review and approve it.
NFR, .cloudforge/NFR.nfr.yaml
Speed, scale, region, budget and security come filled in from your PRD. Change any field, then confirm.
Architecture, .cloudforge/architecture.json
CloudForge draws the design from your requirements. The cost overlay prices every service before you deploy anything.
Build, infra/ and src/
Approval writes Terraform for the whole stack from fixed templates. Agents then build each component, and a step counts as done only when its evidence is saved.
Deploy, your AWS account
Stacks shows your declared Terraform beside live state and marks drift. It lists every add, change and destroy before it runs. To destroy a resource, you type its address.
Architecture diagrams, cost estimates and Terraform often live in different places. When one changes, the others need attention too. CloudForge puts them in the same project so you can work through the design and review the files it produces.
| The job | Today | With CloudForge |
|---|---|---|
| Where the design lives | A diagram in one place, decisions in another. | A canvas built from your requirements, with notes on the choices. |
| Where the price lives | A separate spreadsheet or calculator. | A monthly estimate on each service in the canvas. |
| Where the Terraform lives | Terraform to write and check against the diagram. | In infra/, one module per service. Each box links to its file. |
| What proves it is done | Checks and test results spread across the project. | The agent saves its checks as evidence. You review and confirm the Terraform plan before applying it. |
Prices come from AWS pricing data when you add a pricing key.
Write a brief, set your requirements and work through the architecture. CloudForge saves the design and generates Terraform in your project. Its agent can also write application code one part at a time.
CloudForge uses your requirements to create an architecture on the canvas. Each service has a monthly estimate, so you can see where the cost comes from.
This sample: 7 services, about $690 a month.
Sample project. Illustrative.

The design records what was chosen, an alternative and the reason for the choice.
Sample decision note. Illustrative.

Database
.cloudforge/architecture.json

infra/modules/alb/main.tf

Approving the design writes plain Terraform into your repo, one module per box. Double-click a service on the canvas to open its Terraform at the line that defines it.
Sample project. Illustrative.
The agent saves evidence for its checks before marking a part done. If it cannot measure a goal, it leaves it marked unverified.
Sample part and record. Illustrative.
| Requirement | How it was measured | Result |
|---|---|---|
| Data stays in eu-west-2 | Terraform check on the region setting | Verified |
| Reminders retried 3 times | Retry test in backend/app | Verified |
| Booking page p95 under 300 ms | Not measured. No load test is saved. | Unverified |
.cloudforge/evidence/app-servers/result.json
Every checkout writes an order event, and finance, fraud and the warehouse each get their own copy. If one of them is down, its copies wait in line, and no one counts an order twice. Every event is kept for 30 days, so it can be checked or replayed.
Sample brief. Illustrative. Priced at 2 million orders a month in us-east-1.
A public API for 40 partner companies. Each partner gets its own key and its own rate limit. The goal is p95 under 200 ms, and the data stays in eu-central-1.
Sample brief. Illustrative. Priced at 20 million requests a month in eu-central-1.
Adjusters upload claim documents. Every file is encrypted and kept for seven years. Every read is logged, and nothing leaves us-east-1.
Sample brief. Illustrative. Priced at 50,000 files a month, in month 12, in us-east-1.
Sample projects on AWS. Prices are illustrative, worked out on 27 October 2026 from AWS list prices at the usage shown under each brief; in the product they come from AWS pricing data when you add a pricing key. Folders are under infra/.
It first sets up a storage bucket and lock table for Terraform state. For your infrastructure, it shows you a plan and waits for your confirmation before applying it. By default, the agent asks before running a command that changes anything. Destructive operations always need your approval.
It can. The agent cannot mark a part done without saved evidence from lint, build, tests and Terraform checks. A goal it cannot measure, such as latency, stays marked unverified.
CloudForge runs locally on your machine and uses your own cloud account credentials. The Privacy Policy explains what data can leave your device and when.
Yes. It is plain Terraform in the infra/ folder, with the standard provider and no CloudForge plugin. Set up its state storage once with the included bootstrap folder, then run it as you normally would.
CloudForge is a desktop IDE for cloud infrastructure. You can write a brief, design an architecture, estimate its cost and generate Terraform from the design. You can also review the plan and apply it to your cloud account.
Developers and small teams building cloud applications, including people working without a dedicated infrastructure team.
Yes. The agent writes it into backend/ and frontend/, one part of the architecture at a time, and by default asks before it writes a file.
CloudForge gives you a canvas and a place to work through the infrastructure, alongside an agent that can write code. The design links to the Terraform it generates, and the agent saves evidence for its checks.
AWS today, with Terraform templates for about 190 services. More cloud integrations are coming soon.
Windows x64 and macOS.
CloudForge will be a membership, with pricing coming soon. Joining the waitlist is free and needs no payment.
We use your name, email and country only to tell you when access opens. To be removed, email [email protected]. The Privacy Policy has the details.
100+ people are on the waitlist.
Windows x64 and macOS. AWS is supported today. Joining the waitlist is free; membership pricing is coming soon.