AI diagram generator

AI cloud architecture diagram generator.

Read your infrastructure as code and draw it, with the real service names and no cloud credentials required.

Download for macOS
v0.1.33 · .dmg · Apple Silicon & Intel
Signed & notarized by Apple · opens without a Gatekeeper warning
sha256 698955a0187bc039f4c74f5d05a9f10fbb27376a45788a0a241d1326b73873c7
Download for Windows instead
$curl -fsSL https://lucidtrain.com/install.sh | sh

Read the configuration, not the account

Terraform, CloudFormation, Bicep, Pulumi and Kubernetes manifests all describe infrastructure precisely, and all of them are files. Reading files rather than connecting to an account means no credentials, no read-only role to provision, and the ability to diagram an environment you have no access to. A tool that wants production access to draw a picture is a poor trade.

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.

Multi-cloud in one diagram

Plenty of real systems span providers, usually not by design: object storage in one, a managed database in another, an identity provider somewhere else. Because tiers are the organising principle rather than provider boundaries, a diagram can hold all of it and still read clearly, with provider showing up as the icon rather than as a container.

Icons are bundled, so it works offline

Service logos ship with the app rather than being fetched. A diagram that silently loses its icons on a plane or inside an air-gapped network is one you cannot rely on for a review, and that is a surprisingly common failure in browser-based tools.

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.

Equivalent services across providers

TierAWSAzureGCP
CDNCloudFrontFront DoorCloud CDN
GatewayAPI GatewayAPI ManagementAPI Gateway
ContainersECS, EKSAKS, Container AppsGKE, Cloud Run
FunctionsLambdaFunctionsCloud Functions
RelationalRDS, AuroraSQL DatabaseCloud SQL
Object storageS3Blob StorageCloud Storage
QueueSQSService BusPub/Sub
CacheElastiCacheCache for RedisMemorystore

Try it

shell
$ Read the Terraform here and draw the cloud architecture. Group by tier, use the real service names, and mark what crosses a region boundary.
FAQ

Questions

Does it need cloud credentials?

No. Everything is read from files, so it works with no account access at all.

Which providers are supported?

AWS, Azure and GCP have bundled icons and are recognised by service name. Others draw correctly with generic glyphs rather than official marks.

Can it diagram what is actually running?

Indirectly: export a description with your provider's CLI and point it at the output. It will not fetch that itself, which keeps the credentials question entirely on your side.

Does it use official cloud provider icons?

It uses bundled service icons that render offline. Newer or more obscure services fall back to a generic glyph rather than the exact vendor mark.

Related