Draft1
The useful decision here is the output format: a draw.io file you can keep editing, not a PNG you have to regenerate every time something changes. Accepting Terraform, docker-compose and SQL as input means the diagram can be derived from the actual infrastructure rather than someone's memory of it. The documented API with a PATCH endpoint for iterating in plain English makes it viable as a docs-pipeline step rather than a one-off toy.
Pros
- Accepts Terraform, docker-compose and SQL as input, not only prose
- Output opens in draw.io and stays editable rather than being a flat picture
- Covers ER, UML, Kubernetes, network, cloud, flowchart and database diagram types
- Documented REST API with key auth, an OpenAPI spec and an endpoint for iterating on an existing diagram
Cons
- Quotas count prompts, so failed attempts and refinements cost the same as successes
- Only three free diagrams before a card is needed
- Collaboration and GitHub version control are held back for the $99 per user Enterprise tier
- No company registration number published, only a Paris street address in the terms