You open Cloudcraft to sketch the architecture for next week's design review, and the sign-up button takes you to a Datadog account. Or your team has a live Cloudcraft diagram of production, but the review needs what it cannot show: a change that is not deployed yet, or the calls behind a login.
Cloudcraft is very good at one job: turning a connected cloud account into an accurate picture. This post covers what it does today, five alternatives with their trade-offs, and how to draw a small AWS web app that explains more than an inventory can.
What Cloudcraft does well
Cloudcraft made its name with 3D isometric cloud diagrams, drawn by hand or generated from a connected AWS or Azure account. Datadog acquired it in 2022, and at the time of writing (November 2026) it comes in two forms:
- Cloudcraft in Datadog. A live, read-only diagram built from data that Datadog's cloud integrations already collect, for AWS, Azure, Google Cloud, Oracle Cloud and VMware vSphere. It draws 3D by default with a 2D toggle and overlays security findings and cost. Datadog's documentation requires resource collection in each integration, and an environment with more than 10,000 resources must be filtered before it renders.
- Cloudcraft standalone. The original app, still documented, with AWS and Azure libraries, a budget estimate, and live sync on its Pro plan through read-only access.
The pricing page now lists only Cloudcraft in Datadog: free with any Datadog subscription, with unlimited users and diagrams.
Why teams look for an alternative
- You do not use Datadog. Signing up on cloudcraft.co now starts a Datadog account, and the live diagram depends on Datadog's integrations. Free inside Datadog helps most when Datadog is already your monitoring platform.
- You need to draw what does not exist yet. Cloudcraft in Datadog is read-only by design, and a design review needs the proposed change.
- You need other diagram types. A login flow is a sequence diagram, a service boundary is a C4 view, and a schema is an ER diagram.
- Live and edited do not mix. In the standalone app, moving a component on a live diagram turns it into a static snapshot, and switching back to live discards your edits.
What to compare
Two questions decide most choices: do you need live import, and do you need to draw what is not deployed yet?
| Tool | Live account import | Clouds | Planned designs, other diagram types | Price model (November 2026) |
|---|---|---|---|---|
| Cloudcraft in Datadog | Yes, read-only | AWS, Azure, Google Cloud, Oracle Cloud, vSphere | No | Included with any Datadog subscription |
| Lucidchart with the Cloud Accelerator | Yes, scheduled or manual refresh | AWS, Azure, Google Cloud | Yes | Enterprise add-on, through sales |
| draw.io | No | AWS, Azure and Google Cloud shapes | Yes | Free, Apache 2.0 source |
| Hava | Yes, daily sync | AWS, Azure, Google Cloud, Kubernetes | No | $59 to $249 a month per plan |
| Eraser | Yes, on paid plans; scans on demand | AWS, Azure, Google Cloud, VMware and more | Yes, also as code | Free tier; Business $45 per member per month, annual |
| Archboard | No; drafts from Terraform or CloudFormation | Provider-neutral Cloud pack | Yes | Free tier; Pro $10 per seat per month |
Five Cloudcraft alternatives
Lucidchart with the Cloud Accelerator
Lucid announced in April 2025 that Lucidscale would become part of its Cloud Accelerator, and since August 2026 new documents with cloud data open directly in Lucidchart. You connect AWS, Azure or Google Cloud with read-only credentials that Lucid stores, or upload a file, and stored credentials can refresh the data on a schedule. Version compare shows what changed between imports, and Terraform generation from AWS shapes is in beta.
- Best for: organizations already on Lucid that want cloud diagrams next to everything else they draw.
- Trade-offs: the Cloud Accelerator is sold to Enterprise accounts through sales, and the move from Lucidscale is still in progress. See Lucidchart alternatives for the editor itself.
draw.io (diagrams.net)
draw.io is free, with Apache 2.0-licensed source, in the browser or as a desktop app. Its AWS libraries include Amazon's isometric shapes, with Azure and Google Cloud libraries alongside, and real-time co-editing works for files in Google Drive, OneDrive, Confluence Cloud or Nextcloud.
- Best for: a free, familiar editor with full control over your files, and a home for a Cloudcraft export.
- Trade-offs: nothing comes from your cloud accounts, so every change is manual, and a shape is a picture with a label. See draw.io vs Archboard, and Visio alternatives if your cloud diagrams live in Visio today.
Hava
Hava reads AWS accounts, Azure subscriptions, Google Cloud projects and Kubernetes clusters through read-only access and lays out diagrams grouped by VPC. It syncs daily or on demand through its API, CLI or a CI pipeline, keeps previous versions for comparison, and exports to Visio, PNG, CSV and JSON. Its own documentation says plainly that Hava is not a drag-and-drop tool.
- Best for: auditors and platform teams that want a current inventory with history.
- Trade-offs: no planned designs and no other diagram types. Pricing at the time of writing: $59 a month for one user and three cloud sources, $249 for unlimited users and ten sources, and custom for Enterprise, which includes self-hosting.
Eraser
Eraser pairs design documents with diagrams. You write architecture, sequence, ER and flowchart diagrams as code or draw them on a canvas, with real-time co-editing. Paid plans add read-only data sources for AWS (a role limited to the SecurityAudit policy), Azure, Google Cloud, VMware and more, and Eraser's AI drafts cloud diagrams from them. Scans run when you trigger them, not on a schedule.
- Best for: teams that write design docs and want diagrams as text next to the prose.
- Trade-offs: the syntax is Eraser's own, and live data starts on Business at $45 per member per month, billed annually (pricing), with one data source. Free holds three files. See Archboard vs Eraser.
Archboard
Archboard is a hosted workspace for structured diagrams. Its Cloud pack uses provider-neutral types such as Compute, Managed DB, Object Storage and CDN, so an RDS instance is a Managed DB node labeled RDS. The same canvas holds Network, Kubernetes, C4 Model, Sequence and Entity Relation packs, and people and AI agents connected over MCP edit it live. Free tools turn Terraform, CloudFormation, Kubernetes YAML or Docker Compose into a first draft, so a diagram built from Terraform code can show a change before it is applied.
- Best for: teams that design changes and need cloud, C4 and sequence diagrams in one place.
- Trade-offs: there is no live import from cloud accounts, so spotting drift is your job, and it is closed-source SaaS with no self-hosted edition. Free covers one seat, three diagrams and 15 diagram nodes per diagram; Pro is $10 per seat per month. Archboard's comparison pages set it against Lucidchart, Miro, draw.io, Eraser and IcePanel.
How to choose
| If you mainly need | Start with |
|---|---|
| What runs now, and you already use Datadog | Cloudcraft in Datadog |
| An inventory with history, without Datadog | Hava |
| Cloud imports in an existing Lucid Enterprise account | Lucidchart with the Cloud Accelerator |
| A free editor and files you keep yourself | draw.io |
| Diagrams as text inside design docs | Eraser |
| Planned designs next to C4, Kubernetes and sequence diagrams | Archboard |
Many teams keep two kinds of diagram: a generated inventory for operations and audits, and a drawn one for design reviews. When they disagree, you have found drift or a mistake.
The AWS web app diagram
A small AWS web app that follows the three-tier pattern, drawn by hand, with every edge saying what flows over it:
Diagram contents
- Users
- Route 53
- CloudFront
- AWS Region eu-west-1
- S3: static assets
- VPC
- Public subnets, AZ a + b
- Application Load Balancer
- Private subnet, AZ a
- ECS task: api
- RDS PostgreSQL primary
- Private subnet, AZ b
- RDS standby
- DNS query
- HTTPS :443
- /assets/* via OAC
- /api/* HTTPS
- HTTP :8080
- SQL :5432
- sync replication
How to read it:
- Left to right is the request path. Users resolve the name in Route 53 (the dashed edge), then send HTTPS to CloudFront.
- CloudFront splits by path.
/assets/*comes from S3 through origin access control (OAC);/api/*goes to the Application Load Balancer. - Frames show what is reachable. Only the ALB sits in public subnets; the ECS tasks and databases are private, one of each per Availability Zone.
- Both tasks write to the primary. The standby receives synchronous replication, serves no reads and matters only on failover.
- The Markdown block lists the settings worth writing down.
Drawing AWS architecture diagrams clearly
- One question per diagram. This one answers how a request reaches the database and what survives losing an Availability Zone.
- Draw reachability with frames. Public versus private is what a security reviewer checks first; a separate post covers VPC subnets, route tables and NAT gateways.
- Label every edge with a protocol and port, or a path.
HTTP :8080behind the load balancer invites the right question about TLS. - Use current icons, or none. AWS releases its architecture icons three times a year and warns that some third-party libraries carry legacy sets. With generic shapes, put the service name in the label.
- List what you left out, such as NAT gateways, VPC endpoints and IAM roles, in a note.
Build it in Archboard
- Sign in with Google or GitHub and create a diagram. If the stack is already in code, Terraform to diagram or CloudFormation to diagram gives you a first draft; the AWS three-tier architecture template is another start.
- Add a Region frame from the Cloud pack. Inside it, add an Object Storage node for S3 and a VPC frame from the Network pack.
- Inside the VPC, add three Subnet frames from the Network pack: the public subnets and one private subnet per Availability Zone, each with its CIDR range.
- Put a Cloud LB from the Cloud pack in the public frame for the ALB. In each private subnet, add a Compute node for the ECS task and a Managed DB node for the RDS primary or standby.
- Left of the Region, add a Person from the C4 Model pack, a DNS node from the Network pack for Route 53 and a CDN node from the Cloud pack for CloudFront.
- Draw labeled edges: a dashed DNS query, HTTPS :443,
/assets/*via OAC,/api/*HTTPS, HTTP :8080 to each task, SQL :5432 to the primary and sync replication to the standby. - Add a Markdown block from the Core pack with the settings, and short Core Text notes.
The example uses 15 diagram nodes, within the Free plan.
FAQ
Is Cloudcraft free? At the time of writing (November 2026), Cloudcraft's pricing page lists it as free with any Datadog subscription, for unlimited users and diagrams. Datadog itself is priced separately, and the logs, cost and security views need the matching Datadog products.
What is the best free alternative to Cloudcraft? For drawing by hand, draw.io is free and ships AWS, Azure and Google Cloud shapes. Archboard's Free plan gives one seat, three diagrams and every node pack. Neither scans a live account; that takes Datadog, a paid plan or a trial.
Can I generate an AWS architecture diagram from my account automatically? Yes. Cloudcraft in Datadog, Hava, Lucid's Cloud Accelerator and Eraser's data sources read an account through read-only access. Expect an inventory that you still filter and label before it explains a design.
Does Cloudcraft support Google Cloud? Cloudcraft in Datadog covers AWS, Azure, Google Cloud, Oracle Cloud and VMware vSphere. The standalone app documents AWS and Azure only.
Can I move my Cloudcraft diagrams to another tool? The standalone app exports a 2D version to draw.io's format, and Cloudcraft in Datadog exports SVG and PDF. Archboard's importers read code such as Terraform and CloudFormation, so moving there means redrawing: a good moment to cut each diagram down to one question.