AI infrastructure diagram generator.
Where things run, what can reach what, and which boundaries the traffic crosses on the way.
Infrastructure or architecture
An architecture diagram shows logical components and their relationships; an infrastructure diagram shows where those run and how they are connected physically or virtually. Networks, availability zones, clusters and environment boundaries belong here and clutter the other one. Keeping them separate is what stops either becoming unreadable.
How Lucid Train draws one
Describe what you want, or point it at a repository. The agent emits a semantic graph of nodes and edges with no coordinates, and the ELK layout engine computes positions and orthogonal routing. That separation is the reason the output cannot come back with boxes overlapping or arrows crossing through cards, which is the characteristic failure when a language model is asked to place things on a canvas itself. It also means editing is editing the graph: change a component and the layout re-solves rather than drifting out of alignment.
Boundaries are the content
The valuable lines on an infrastructure diagram are the boundaries: public to private, region to region, environment to environment, your network to a third party's. Each one is a place where latency, cost or a security control applies, and a diagram that draws them is answering questions a component diagram cannot.
Read from infrastructure as code
Terraform, CloudFormation, Bicep and Kubernetes manifests all describe this precisely, and none of them require account access to read. That makes an infrastructure diagram cheap to regenerate, which is the only way one stays accurate: hand-drawn infrastructure diagrams are stale within a quarter without exception.
Local, offline, your models
It runs as a desktop application. Against a local Ollama model the whole thing works offline with no API key and no telemetry, which is the practical difference from every browser-based diagram tool: your architecture never leaves the machine.
What an infrastructure diagram carries
| Element | Why it is there |
|---|---|
| VPC or virtual network | The outer boundary |
| Subnets, public and private | What is reachable from outside |
| Availability zones or regions | Failure domains |
| Compute instances, clusters, nodes | Where workloads run |
| Load balancers | Entry points and their scope |
| Storage and volumes | What persists and where |
| Security groups and firewall rules | What can reach what |
| VPN, peering, private links | Connections to other networks |
| Environment boundary | The dev, staging and production split |
Try it
Questions
Related
- AI Architecture Diagram GeneratorDescribe the system, or point it at the repository and let it find out for itself.
- AI System Design Diagram GeneratorFor a design doc, a review, or the whiteboard round where you have forty minutes and need the shape to be right.
- AI Sequence Diagram GeneratorFor when the question is not what the components are but in what order they talk, and what happens when step four fails.
- AI ER Diagram GeneratorPoint it at the schema you already have. The relationships are declared, so the diagram is a rendering rather than an interpretation.