<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: AI Gen</title>
    <description>The latest articles on DEV Community by AI Gen (@noahkash).</description>
    <link>https://dev.to/noahkash</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3986295%2F7d925a9a-752d-41c4-8035-dd4b2f9a4612.png</url>
      <title>DEV Community: AI Gen</title>
      <link>https://dev.to/noahkash</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/noahkash"/>
    <language>en</language>
    <item>
      <title>I built a free tool that turns plain English into cloud architecture diagrams</title>
      <dc:creator>AI Gen</dc:creator>
      <pubDate>Mon, 15 Jun 2026 22:15:15 +0000</pubDate>
      <link>https://dev.to/noahkash/i-built-a-free-tool-that-turns-plain-english-into-cloud-architecture-diagrams-2jii</link>
      <guid>https://dev.to/noahkash/i-built-a-free-tool-that-turns-plain-english-into-cloud-architecture-diagrams-2jii</guid>
      <description>&lt;p&gt;I have a confession: I've spent more of my career arranging rectangles in Lucidchart&lt;br&gt;
than I'd like to admit. Not designing systems — &lt;em&gt;arranging rectangles&lt;/em&gt;. Nudging&lt;br&gt;
connectors so they don't overlap. Hunting for the right AWS icon. Then watching the&lt;br&gt;
diagram rot the moment the architecture changed, because updating it meant doing the&lt;br&gt;
whole thing again.&lt;/p&gt;

&lt;p&gt;So I built &lt;a href="https://stackbuilder.tech" rel="noopener noreferrer"&gt;StackBuilder&lt;/a&gt; to get out of that loop.&lt;/p&gt;

&lt;h2&gt;
  
  
  The idea
&lt;/h2&gt;

&lt;p&gt;You describe your infrastructure in plain English. You get a professional cloud&lt;br&gt;
architecture diagram in seconds. That's it.&lt;/p&gt;

&lt;p&gt;Type something like:&lt;/p&gt;

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

&lt;p&gt;And you get a clean, labeled diagram using real AWS iconography — laid out sensibly,&lt;br&gt;
no dragging required.&lt;/p&gt;

&lt;p&gt;It works across &lt;strong&gt;AWS, Azure, Google Cloud, Kubernetes, Databricks, and multi-cloud&lt;/strong&gt;&lt;br&gt;
setups. No signup. No template to fill in. Free.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problems it actually solves
&lt;/h2&gt;

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

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

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

&lt;p&gt;&lt;strong&gt;Design docs and RFCs.&lt;/strong&gt;&lt;br&gt;
The diagram used to be the reason I procrastinated on writing the doc. Not anymore.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

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

&lt;p&gt;Each provider has its own page if you want to start with context already set:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://stackbuilder.tech/aws" rel="noopener noreferrer"&gt;AWS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://stackbuilder.tech/azure" rel="noopener noreferrer"&gt;Azure&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://stackbuilder.tech/gcp" rel="noopener noreferrer"&gt;Google Cloud&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://stackbuilder.tech/kubernetes" rel="noopener noreferrer"&gt;Kubernetes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://stackbuilder.tech/databricks" rel="noopener noreferrer"&gt;Databricks&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://stackbuilder.tech/multi-cloud" rel="noopener noreferrer"&gt;Multi-Cloud&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why no signup
&lt;/h2&gt;

&lt;p&gt;I've abandoned too many tools that made me create an account before I could even tell if&lt;br&gt;
they worked. So StackBuilder doesn't have a wall. Go to&lt;br&gt;
&lt;a href="https://stackbuilder.tech" rel="noopener noreferrer"&gt;stackbuilder.tech&lt;/a&gt;, describe a system, get a diagram. If it's&lt;br&gt;
useful, you'll come back. If not, you didn't waste any time.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

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

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://stackbuilder.tech" rel="noopener noreferrer"&gt;https://stackbuilder.tech&lt;/a&gt; — free, no signup, works right now.&lt;/p&gt;

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

</description>
      <category>webdev</category>
      <category>devops</category>
      <category>aws</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
