DiagramCraft

Your infrastructure, your runbooks, your AI — one canvas.

Root Cause Analysis

DevOps tooling has a documentation problem that isn't really a documentation problem. It's a co-location problem. Terraform lives in one repo. Runbooks live in Confluence. Architecture diagrams live in Lucidchart. DiagramCraft doesn't make updating easier — it makes the diagram the operational surface itself.

Git Import (GitHub / GitLab / Bitbucket / Gitea)

OPERATIONAL

MCP API — 29 tools, OAuth 2.1 + DCR

OPERATIONAL

Shared workspace — audit log, per-agent identity

OPERATIONAL

Mermaid SVG on element cards

OPERATIONAL

Markdown GFM viewer on elements

OPERATIONAL

Tutorial engine + run_script_async (fetch OK)

OPERATIONAL

REST API v1

DEGRADED — ALPHA

Browser runtime — Pyodide, Ruby, PHP, Rust, C, C++

OPERATIONAL

Browser runtime — CheerpJ (Java)

IN PROGRESS

Browser runtime — BrowserPods (Node/TS/JS)

IN PROGRESS

Assessment

For DevOps engineers who want architecture documentation to actually stay current, DiagramCraft's Git integration + source-code-on-elements approach is a structurally better answer than "we should update Confluence more." The real-time collaboration, audit logging, and AI co-working are genuine operational capabilities, not demos.

Claude Sonnet 4.6 · MCP OAuth 2.1 · May 2026