Connected repositories

The code is the only description that is never out of date.

So that is where the diagrams come from. Connect a repository once, and the picture of your system maintains itself from then on.

Connect a repo See pricing

Read-only repo access
Works with Claude Code, Cursor, Claude Desktop
Free for one editor

doczoid/example-ledgerregenerated 4 min ago · a3f9c2e · main

What it draws

Several views of the same system.

One repository feeds as many diagrams as you need. Each lives in its own document, or several documents, and each regenerates on its own.

High-level architecture

Services, their boundaries, and what talks to what. Grouped into DocZoid containers by subsystem.

Data lineage

Where a piece of data enters the system, what transforms it, and where it comes to rest.

Service dependencies

The call graph between services, including the edges that only exist in configuration.

Data model

Entities and their relationships, read from migrations and schema definitions.

Every one of them is a real DocZoid diagram. Real containers, real edges on real anchor points, a canvas you can drag things around on. Not a rendered image, and not a Mermaid file that you now have to find a home for.

Regeneration

It updates on every push.

DocZoid watches the branch you nominate and regenerates on every push to the tracked branch. There is a button too, for the times you want it now.

Regeneration does not throw away your work. The structure comes from the code; the layout, styling, containers, and notes you added stay where you put them. When a service appears or disappears in the repository, it appears or disappears in the diagram, and every PortalSnip of that diagram updates in place.

How PortalSnips work

Commit pushed to maina3f9c2e
142 files read6.2s
ledger-core split into two servicesstructure
Architecture diagram updated1 diagram
6 embeds refreshed4 docs, 2 zoids

Regenerationa3f9c2e · 4 min ago

on every pushor on demandRead-only repo access

Access

What DocZoid can see, and what it will never do.

Read-only, always

DocZoid reads your repository to generate diagrams. It never pushes, opens pull requests, or writes to your code.

You choose the repositories

Connect one repository or several. DocZoid sees only what you grant, and you can revoke it from the same screen.

Bring your own model

Use your own API key, so generation runs on an account you control and bill.

Or keep it local

Point DocZoid at a local model over MCP when the code is not allowed to leave your network.

Hosts

Where your code lives.

GitHubGitLab· plannedBitbucket· plannedAzure DevOps· planned

Need one that is not on the list? Tell me and it moves up the queue.

Not only from code

You can also just describe it.

The same generator works on a paragraph. Write what the system does and DocZoid lays out the diagram beside it, on the canvas, ready to edit.

Text to diagram0:49

Questions

The ones people ask first.

Does DocZoid write to my repository?: No. Access is read-only. DocZoid reads your code to understand the system and never pushes a commit, opens a pull request, or changes a file.
Can I edit a generated diagram?: Yes. A generated diagram is an ordinary DocZoid diagram: move a box, restyle a container, add a note. Your layout choices survive regeneration; what changes is the structure the code describes.
What about private repositories?: Supported. You choose which repositories DocZoid can see when you connect it.
Which model does the generating?: You can bring your own key, or point DocZoid at a local model over MCP if your code is not allowed to leave your network.
What happens to a monorepo?: Connect the repository and scope a diagram to a directory. One repo can feed several diagrams, each with its own scope, in different documents.
Which plan includes this?: Connected repositories are included from the Team plan.

Connect a repo. See your architecture in five minutes.

Start free Set up MCP

Read-only repo access
Works with Claude Code, Cursor, Claude Desktop
Free for one editor