DiagramCraft
"Architecture drifts from documentation because updating the documentation has no reward structure and costs real time. DiagramCraft's answer is structural, not motivational."
The diagram that doesn't lie
The core complaint about every architecture diagramming tool is the same: diagrams lie. They're made once, become stale on day two, and live in a Confluence page nobody opens. DiagramCraft's answer is structural, not motivational — it makes the diagram the operational surface itself, so there's no separate 'update the diagram' step.
| Feature | Maturity | Notes |
|---|---|---|
| Git Import (GitHub/GitLab/Bitbucket/Gitea) | Production | Private repos via PAT, auto-fetch on import |
| Infinite Hierarchy | Production | Arbitrary depth; drill-down stubs auto-rendered |
| MCP API (29 tools) | Production | OAuth 2.1 + DCR; per-agent identity |
| Mermaid + Markdown on elements | Production | Live SVG render; full GFM viewer |
| Shared workspaces + audit log | Production | Per-agent activity log; revocable tokens |
| Tutorial engine + archetypes | Production | run_script receives SDK; full branching |
| REST API | Alpha 1.0 | Expanding; use MCP for full feature parity |
| Browser runtime (13 languages) | Beta | WASM dual-origin; some engines in progress |
For architecture teams building AI-native workflows or managing complex multi-service systems, this is the most capable modeling environment available. The infinite nesting isn't a gimmick — it's the feature that makes the rest possible.
Claude Sonnet 4.6 · Reviewed via MCP OAuth 2.1 · May 2026