Connected repositories · MCP · Live docs
Architecture docs that update when the code does.
Connect a repository. DocZoid generates the architecture and data-lineage diagrams, keeps them current on every push, and carries them into every doc and slide that embeds them.
- Read-only repo access
- Works with Claude Code, Cursor, Claude Desktop
- Free for one editor
The problem
Your architecture diagram was accurate once.
Diagrams rot because the tool that draws them sits outside the workflow that changes the system. The person who drew it moved teams. Everyone knows it is wrong; nobody knows how wrong. In a 2026 survey, 68% of teams had architecture docs more than six months out of date.
The loop
Four steps, then it maintains itself.
This is the whole product. Everything else exists to make these four steps worth doing.
Connect a repository
Point DocZoid at the repo the system actually lives in. Access is read-only: DocZoid reads your code to understand it and never writes back, opens a pull request, or pushes a branch.$connect doczoid/example-ledger142 files read4 diagrams queuedwatching mainread-only · main DocZoid generates the diagrams
High-level architecture and data lineage to start with, and more besides. Each one is a real DocZoid diagram with real shapes, containers, and edges. Not an image, not a Mermaid file you have to keep somewhere. You can move a box.Generating a diagram0:49 Embed them wherever they belong
Turn any diagram, or any region of one, into a PortalSnip and drop it into the onboarding doc, the incident runbook, the architecture decision record, the board deck. The same object in every one of them.Creating and inserting a PortalSnip0:33 Push a commit
The diagram regenerates, and every embed follows. The runbook is right. The onboarding doc is right. The slide you presented last month is right. Nobody did anything.- Onboarding: the ledgerdoc
- Runbook: payment failuresdoc
- ADR 014: splitting the ledgerdoc
- Q3 architecture reviewzoid
- Platform team wikidoc
- Due diligence packzoid
Propagated to 6 placesa3f9c2e · 4 min ago
What it generates
High-level architecture
Data lineage
Service dependencies
Data model
DocZoid reads your repository to generate diagrams. It never pushes, opens pull requests, or writes to your code.
Model Context Protocol
Your AI already knows the repo. Now it knows the docs.
DocZoid ships a full MCP server. Any MCP client can read your docs and diagrams, create and update them, and pull the current architecture into its context before it answers.
Ask Claude Code to write the decision record for the change it just made, with the regenerated diagram already in it. Point Cursor at the runbook before it touches the payment path. Run it against a local model if your code never leaves the building.
Claude Code
claude mcp add doczoid \
--transport http https://mcp.doczoid.io/v1Cursor and Claude Desktop on the MCP page. Works with a local model too.
One source, three views
A document, a diagram, and a deck are the same thing here.
Write it as a doc. Draw it as a diagram. Present it as a Zoid. They are documents in one team, built on one canvas, sharing live content.
Block-based text, stored as Markdown, with a diagram canvas in a split view beside it. Comments anchor to individual blocks.
Shapes on a snapping grid, bezier edges on anchor points, and containers that group and theme a whole subsystem at once.
16:9 slides on the same canvas as your diagrams. Present full screen, read-only, with the arrow keys.
PortalSnips are what make that true rather than a slogan. A passage or a region of a canvas, inserted in many places, live. Edit the source and every reference follows.
Explore the productFor teams
Built for the people who have to agree on it.
Documentation is not a solo activity. Neither is architecture.
Live cursors
Presence that tells you what
Chat in the document
Review notes
Pinned and threaded comments
Version history
Compared
Plenty of tools generate a diagram. One puts it everywhere it is needed.
Generating a diagram from a repository is close to a solved problem, and some of the tools that do it are free. The part nobody else does is what happens to that diagram afterwards.
| Price | Diagrams from repo | Kept updated | Into docs & decks | MCP | |
|---|---|---|---|---|---|
| DocZoid | $12 to $18 / editor | Yes | Yes | Yes | Yes |
| Eraser | $15 to $45 per member / month | Yes | Yes | Partly | Partly |
| Confluence + Miro | $6 to $15 per user / month, each | No | No | Partly | Partly |
| IcePanel | $40 to $80 per editor / month | No | No | No | No |
| Swark, GitDiagram, Archify | Free | Yes | No | No | No |
Why we build it
Code got cheap. Keeping it explained didn't.
BramLabs is a small product studio in Denmark. We build around one idea: AI writes the code now, but somebody still has to decide what the system is and explain it to the people who have to run it.
That explanation was always the weak part. The architecture lived in a diagram tool, got re-pasted into a deck, and was out of date in both by the time anyone looked. We had drawn the same system three times ourselves and never once trusted the result.
So DocZoid reads the repository instead. The code is the one description of the system that is never wrong, and now the documents, diagrams, and presentations come from it. That is the kind of product we exist to build: one job, done with restraint, designed for the day it is actually in use.
Jimmi Bram · Founder & CTO, bramlabs.io
More about DocZoid and bramlabsPricing
Free to try it. $18 to run it.
Viewers are free on every plan. Only the people who create and change things count as editors.
Team
repos + MCP$18per editor / month
The plan the repo loop lives on. For a team that owns a system.
Start 14-day trialConnect a repo. See your architecture in five minutes.
Free for one editor, no card. If the diagram it draws is wrong, you have learned something about your codebase.
- Read-only repo access
- Works with Claude Code, Cursor, Claude Desktop
- Free for one editor