Zindex

ClaudeCommunityby Zindex

The diagram runtime your agents share. Zindex validates each saved change and keeps its revision and image. Diagrams from AI are usually one-offs, redrawn from scratch in the next conversation. With Zindex, Claude saves the diagram, and your team's Claude, Claude Code and the agents you build keep working on that same diagram. Ask Claude for an architecture (AWS diagrams in the official AWS Architecture Icons included), an entity-relationship model, a sequence, a BPMN workflow, a network, an org chart, a UI flow or a flowchart. Every change is a new numbered version, and nothing in a diagram's history can be rewritten: each version's hash covers the one before it. Claude can open any version by number or date, see who changed what, and compare any two versions. Each version's image is kept, so an engine update never changes an old picture. In a later chat, Claude finds the diagram, reads a short brief instead of the whole drawing, and sends only what changes. In a team workspace (Team plan), everyone's Claude works on the same diagrams. An edit made from an older version is refused, so nobody's work is overwritten. Claude can also start from a Mermaid flowchart or erDiagram, and edit an architecture or database diagram as Mermaid text. Share a diagram when you choose: publish it, or make a share link that shows its images to anyone with it. The images go into a README, an issue, a doc or a Claude artifact. On Pro and Team, a workspace can keep its diagrams in its own private GitHub repository with bring your own storage. What it needs: a Zindex account, free to start. Claude asks you to sign in. Share links and bring your own storage need Pro or Team: see zindex.ai/pricing. What it doesn't do: Zindex runs no model on your diagrams. Claude says what's in them; Zindex lays them out and draws them with deterministic code. Download any version as SVG, PNG, Mermaid or JSON, or your whole history in one file.