agent-native diagram state infrastructure

Diagrams your AI agents can maintain.

Zindex is a stateful diagram runtime for agents. Create architecture diagrams, ERDs, workflows, org charts, and topology maps from structured data - then patch, validate, diff, and render them as systems change.

Not a whiteboard. Not a Mermaid clone. A database-like backend for diagrams with stable IDs, typed operations, semantic validation, immutable revisions, auto-layout, and SVG/PNG rendering.

Install MCP Browse examples Read the API docs →

zindex architecture

why zindex

AI agents can generate diagrams, but they usually regenerate the whole thing every time. IDs change. Layout shifts. Diffs are meaningless. Validation is missing. Zindex turns diagrams into durable state agents can safely patch, validate, diff, and render.

Keep diagrams in sync with reality

Agents update existing diagrams from codebases, schemas, APIs, tickets, HR data, or infrastructure - without redrawing from scratch.

Make diagram changes reviewable

Every edit creates an immutable revision. Diff diagrams by scene structure, not pixels.

Catch broken diagrams before they ship

Validation catches missing endpoints, invalid references, bad containment, layout issues, and family-specific mistakes.

Let agents describe structure, not pixels

Agents define nodes, edges, relationships, and constraints. Zindex handles layout, routing, labels, and rendering.

Render anywhere

One canonical scene can become SVG or PNG across themes without changing the underlying state.

three workflows that need a stateful runtime

One-shot diagram tools can't track change. These workflows do, because the diagram is durable state.

PR architecture diffs

Agents diff scene structure on every PR, surface what changed in the system, and gate merges on validation. The reviewer sees a structural diff instead of an arbitrary new SVG.

View example → 02

ER diagrams from migrations

Schema migrations become ER scenes that update incrementally. Each release produces an immutable revision, so you can show the schema as it stood at any point in time.

View example → 03

Compliance data-flow audit trails

Every revision is a snapshot of how data flowed through the system. Auditors get a timestamped history with stable references, not a folder of screenshots.

View example →

where it fits

Zindex is the middle layer between agent reasoning and visual output.

agents / LLMs decide what should change

zindex apply changes through DSP protocol

renderers display the result

A database for diagrams.

Store the diagram once. Patch it with operations. Validate every change. Render any revision.

the protocol

DSP (Diagram Scene Protocol) is the machine interface for diagrams. Agents describe what exists, not how to draw it.

example.scene.json

{
  "schemaVersion": "0.1",
  "diagramFamily": "architecture",
  "scene": {
    "id": "payments-arch",
    "units": "px"
  },
  "elements": [
    {
      "id": "api",
      "kind": "node",
      "nodeType": "service",
      "shape": "roundedRect",
      "label": "API Gateway"
    },
    {
      "id": "queue",
      "kind": "node",
      "nodeType": "queue",
      "label": "Job Queue"
    },
    {
      "id": "e1",
      "kind": "edge",
      "from": { "elementId": "api" },
      "to": { "elementId": "queue" },
      "router": "orthogonal"
    }
  ]
}

Semantic, not geometric

Agents declare nodes, edges, and relationships. Layout is computed, not hand-placed.

Layout engine built in

A Sugiyama-style hierarchical layout pipeline figures out positions, edge routes, and label placement automatically. Agents describe the graph; the engine handles the geometry.

Patchable

Stable IDs enable incremental updates. Add a node, move an edge - without regenerating the entire diagram.

Renderer-agnostic

One canonical scene, multiple outputs: SVG and PNG with 4 render themes (clean, dark, blueprint, sketch).

Deterministic

Same input, same output. Validate → normalize → layout → render. Every step is inspectable.