Cloudviz API vs D2

Cloudviz API

Diagrams come from the live AWS account through a read-only cross-account role with a per-customer external ID. AWS only, and API access starts at the $49 a month Team plan.

D2

A single local command turns text into a diagram in six formats with no account, key or network call, and CI passes on the default branch. The language is at 0.9.0 with no stable release, its company sponsor has shut down, and one maintainer with limited time wrote every commit since July.

Cloudviz API

1. Call GET /aws/accounts/ first to get the Cloudviz account ID, then request /aws/accounts/{account-id}/{region}/{format}
2. On a 202, wait and repeat the same GET until the diagram is ready
3. Ask for jsonSnapshot or jsonDiagram (there is no plain json format) when the agent has to reason over resources
4. Use a read-only key unless the agent has to add, change or delete AWS accounts

D2

1. Check the exit status of d2, never the output file. The man page says a partial render can be written when an error occurs
2. Run d2 validate file.d2 before rendering, and d2 fmt to normalise the source
3. Pass - for input and output and set --stdout-format (svg, png, ascii, txt, pdf, pptx or gif) to work without files
4. Use --stdout-format ascii when the reader is a text-only model
5. Pass --bundle=false or review image URLs and imports before rendering D2 text from an untrusted source. Release 0.9.0 fetches remote images when bundling