AI Diagram Tools Compared: After Generation, Who Owns It
This review skips image quality and compares only what can be objectively verified, opening with its scope and boundary statement: not a hands-on benchmark, data verified from each project's official repository on 2026-09-15, star counts moving in real time, and no subjective quality scoring. It lines up five projects: cathrynlavery/diagram-design (39,807 stars, MIT, HTML, 44 open issues, created 2026-04-16), mermaid-js/mermaid (90,244 stars, MIT, TypeScript, 1,785 open issues, created 2014-11-01), excalidraw/excalidraw (131,918 stars, MIT, TypeScript, 3,471 open issues, created 2020-01-02), terrastruct/d2 (25,416 stars, MPL-2.0, Go, 528 open issues, created 2022-09-05) and plantuml/plantuml (13,313 stars, LGPL-3.0, Java, 588 open issues, created 2010-11-04). The analytical frame is three paradigms: text engines (Mermaid, D2, PlantUML, where authors describe structure and the engine owns layout, at the cost of layout control and a rendering dependency), self-contained artifacts (diagram-design, where a coding agent emits offline-openable HTML with inline SVG, at the cost of a heavy drawing spec), and hand-drawn interactive tools (Excalidraw, strong for human whiteboarding, where an agent produces a scene file rather than a finished image). The core claim: what you buy in a diagram tool is not generation, but who owns the artifact afterward, what form it takes, and who can open it. It closes with a selection table by team shape, and stays honest about evidence: licenses are described by type and distribution implications without absolute commercial conclusions, and the problem-density section explicitly states it is not a quality verdict, since the three differ enormously in size, age and feature surface.