Simulation
Build a simulation
Create a provider-specific canvas, configure nodes, review cost, and preview Terraform.
Build steps
- Open Simulation.
- Choose AWS, Azure, or GCP.
- Drag services onto the canvas.
- Connect services where the architecture needs relationships.
- Select each node and fill required configuration.
- Review the floating cost estimate and warnings.
- Open Terraform Preview before deploying.
Save behavior
- Use manual save when you want a stable draft.
- Check saved history before assuming a design was preserved.
- Keep test designs clearly named so they are not confused with production work.
Node configuration examples
- Compute nodes usually ask for size, image, count, admin username, disk, region, and network settings.
- Storage nodes usually ask for bucket or account name, region or location, replication, storage class, versioning, lifecycle, and access policy.
- Database nodes usually ask for engine, version, class or tier, storage, database name, username, port, SKU, max size, and public access.
- Serverless nodes usually ask for runtime, handler or entry point, memory, timeout, function name, environment, and region.
- Network nodes usually ask for VPC or VNet name, CIDR blocks, subnet ranges, security rules, HTTP, HTTPS, SSH, public IP, load balancer, and backend routing.
- Application nodes usually ask for Git URL, branch, project type, runtime, build command, start command, app port, Docker image, tag, and optional credentials.
Need more help?
Keep moving with the right next guide
If your team still runs into setup issues, empty dashboards, billing delays, callback failures, or alerting problems, continue with troubleshooting before re-running the entire onboarding flow.