DEV Community

Cover image for I built a free tool that turns plain English into cloud architecture diagrams
AI Gen
AI Gen

Posted on

I built a free tool that turns plain English into cloud architecture diagrams

I have a confession: I've spent more of my career arranging rectangles in Lucidchart
than I'd like to admit. Not designing systems — arranging rectangles. Nudging
connectors so they don't overlap. Hunting for the right AWS icon. Then watching the
diagram rot the moment the architecture changed, because updating it meant doing the
whole thing again.

So I built StackBuilder to get out of that loop.

The idea

You describe your infrastructure in plain English. You get a professional cloud
architecture diagram in seconds. That's it.

Type something like:

"A 3-tier web app on AWS: an Application Load Balancer in front of ECS Fargate
services across two AZs, an RDS PostgreSQL Multi-AZ database, S3 for static assets,
and a CloudFront CDN."

And you get a clean, labeled diagram using real AWS iconography — laid out sensibly,
no dragging required.

It works across AWS, Azure, Google Cloud, Kubernetes, Databricks, and multi-cloud
setups. No signup. No template to fill in. Free.

The problems it actually solves

Architecture diagrams that are always out of date.
Every team I've been on has had a Confluence page with a diagram from 9 months ago that
no longer matches reality. Nobody updates it because the cost is too high. If
regenerating takes 30 seconds, you'll actually keep it current.

Explaining infra to non-technical people.
"Can you draw up what our system looks like?" used to mean 40 minutes in a diagramming
tool. Now I describe it, export the PNG, drop it in the doc.

System design interview prep.
This one surprised me — a lot of people use it to work through design problems. Describe
the system, get a visual, reason about it. Faster feedback loop than a whiteboard.

Design docs and RFCs.
The diagram used to be the reason I procrastinated on writing the doc. Not anymore.

How it works

You describe the system. The AI interprets the components, their relationships, and the
provider-specific services, then generates a structured diagram with proper icons. You
can refine it in plain English too ("add a Redis cache in front of the database"), and
export to PNG, SVG, PDF, or draw.io.

Each provider has its own page if you want to start with context already set:

Why no signup

I've abandoned too many tools that made me create an account before I could even tell if
they worked. So StackBuilder doesn't have a wall. Go to
stackbuilder.tech, describe a system, get a diagram. If it's
useful, you'll come back. If not, you didn't waste any time.

What's next

I'm working on saved/versioned diagrams and team sharing. Right now the focus is on
making the generation quality good enough that you'd put the output in front of a client
or a hiring panel — not just use it as a rough sketch.

Try it

https://stackbuilder.tech — free, no signup, works right now.

If you try it, I'd genuinely love to hear what you described and whether the diagram
matched what you had in your head. The "where it got it wrong" feedback is the most
useful thing you can give me at this stage — drop it in the comments.

Top comments (0)