What are CloudForge Delivery Workspaces?

CloudForge Delivery Workspaces help teams move from a requirement or Designer diagram into reviewable architecture, engineering, and DevOps artefacts. The Architect Workspace creates clarification questions, impact analysis, ADRs, risks, Mermaid diagrams, and delivery backlog items. Engineering and DevOps workspaces prepare implementation and release readiness.

How do Designer diagrams connect to CloudForge Workspaces?

Designer remains the visual source of truth for cloud architecture diagrams. Workspaces explain and prepare the delivery work around that design: Architect Workspace turns requirements into architecture packs and diagrams, Engineering Workspace turns approved architecture into implementation tasks, and DevOps Workspace turns the design into deployment readiness.

CloudForge is a visual cloud infrastructure designer for Azure, AWS, and GCP. You can drag-and-drop cloud resources, pull live Azure and AWS inventories, or describe your architecture in plain English and the AI will generate the diagram. It then produces production-ready Terraform, Pulumi, ARM templates, Bicep, or CloudFormation code automatically.

Does CloudForge have a free trial?

Yes. CloudForge has a trial for evaluation. Paid plans unlock production workflows such as Azure and AWS live resource import, team governance, Terraform and Pulumi generation, drift checks, and priority support.

Which cloud providers does CloudForge support?

CloudForge supports Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP) with 100+ resources for each provider. You can design multi-cloud and hybrid architectures in a single interface.

Can CloudForge generate Terraform code automatically?

Yes. CloudForge generates production-ready Terraform code directly from your visual diagrams. It also supports ARM templates, Bicep, and CloudFormation. The generated code follows cloud provider best practices and is ready to deploy.

Does CloudForge have an AI architecture designer?

Yes. The AI Architect lets you describe your infrastructure in plain English (e.g. "a highly available 3-tier web app on Azure with a PostgreSQL database and Redis cache") and instantly generates the full architecture diagram with proper resources, connections, and Terraform code.

Do I need my own API key to use CloudForge AI?

No. CloudForge includes managed AI powered by Anthropic Claude on AWS Bedrock, so you do not need to bring your own API key. AI usage is credit-metered and included with your plan, and you can use the AI Architect, code generation, and self-healing Terraform out of the box.

What is CloudForge Holographic Review Mode?

Holographic Review Mode is an immersive 3D "solar-system" view of your cloud architecture, where resources orbit as an interactive holographic scene. It is designed for stakeholder presentations and design walkthroughs, letting teams explore and review an architecture in three dimensions.

Does CloudForge have a desktop app?

Yes. CloudForge offers a native Windows desktop app (Windows 10/11 x64). Download the zip, extract it, and run CloudForge.exe. A macOS and Linux version are coming soon.

Can I import existing Terraform files into CloudForge?

Yes. CloudForge can parse your existing .tf Terraform files and automatically generate a visual architecture diagram from them. You can then edit the diagram and regenerate the Terraform code.

Is CloudForge a good Cloudcraft alternative?

Yes. CloudForge is a Cloudcraft alternative with AI-powered architecture generation, Terraform and Pulumi export, multi-cloud support for Azure/AWS/GCP, live resource import, and a native Windows desktop app.

Templates/Hub-Spoke with Transit Gateway

AWS

Networking

advanced

Hub-Spoke with Transit Gateway — AWS Architecture Template

Transit Gateway hub interconnecting prod, dev, and shared-services VPCs with centralised egress and DNS.

Why this architecture works

Transit Gateway replaces an unmanageable mesh of VPC peerings with one hub and per-spoke route tables
Route-table segmentation keeps prod and dev spokes unable to reach each other unless explicitly allowed
Centralised NAT egress in one place means one set of egress controls and logs instead of per-VPC sprawl
Shared-services VPC hosts DNS and tooling once, consumed by every spoke
VPC flow logs to CloudWatch give a single pane for east-west traffic forensics

What's inside (7 resources)

Prod Spoke VPC

aws-vpc

Dev Spoke VPC

aws-vpc

Shared Services VPC

aws-vpc

Transit Hub

aws-transit-gateway

Private DNS

aws-route53

Central Egress

aws-nat-gateway

Flow Logs

aws-cloudwatch

From template to running infrastructure

Open this template in the CloudForge visual designer (free account, no credit card).
Customize resources, names, and connections on the drag-and-drop canvas — or ask Vani, the AI architect, to adapt it.
Generate production-ready Terraform or CloudFormation in one click.
Review the plan diff and security scan, then deploy with human approval.

Related architecture templates

Landing Zone Network

AWS · Networking

Hybrid VPN Connectivity

AWS · Networking

Private-Subnet-Everything App

AWS · Networking

Hub-Spoke Network Topology

Azure · Networking