Set requirements
Set users, budget, reliability, security rules and deployment choices, or keep the smart defaults.
Start from the defaults
Open Requirements from CloudForge Home or the Blueprint menu.
If you approved a PRD, CloudForge fills in the form from it. If you did not, the form shows editable defaults. You can fill it in by hand, or go back and draft a PRD first.
You do not need to change every field. Keep the defaults and change only what matters to you.
What you can set
| Section | What it covers |
|---|---|
| Cloud Provider | AWS (fixed), the regions to use, and whether to run in more than one region. |
| Scale | Users at launch, at 6 months and at 18 months. Peak and average traffic. Data volume. Traffic pattern: uniform, bursty, scheduled or event-driven. |
| Cost | Your monthly budget, how sensitive you are to cost, and reserved capacity. |
| Reliability | Availability target, how much data you can lose (RPO), how fast you must recover (RTO), and redundancy across zones or regions. |
| Performance | API response times, page load time, and whether users are spread around the world. |
| Security | Rules to follow (HIPAA, SOC 2, PCI-DSS, GDPR or none), where data must stay, and encryption at rest and in transit. Encryption is on by default. |
| Deployment | Containers, serverless, virtual machines or a mix. TerraformTerraformA language for describing cloud infrastructure as code. CloudForge writes Terraform for your architecture into the infra/ folder. as the infrastructure tool (fixed). Your CI/CD platform. How new versions roll out. |
Need something that is not on the form? Choose Add Custom Section.
Get suggestions
- Open the suggestions on a field to see what CloudForge recommends. Choose Apply to use one.
- Choose Regenerate to fill the form again from your PRD. You can add an instruction first, for example "Use serverless where you can".
Confirm
Choose Confirm Requirements. CloudForge saves them as .cloudforge/NFR.nfr.yaml.
Next: The architecture canvas.