Skip to content

Connected repositories

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

So that is where the docs and diagrams come from. Connect a repository once, link a document to it, and the description of your system is rewritten from the code whenever you ask.

  • Read-only repo access
  • Works with Claude Code, Cursor, Claude Desktop
  • Free for one editor
A DocZoid document linked to the bramlabs-io/doczoid repository, showing the system overview diagram in three lanes: Clients (web app, MCP clients, CI and scripts), the Next.js 16 server (collaboration server, app routes, MCP server, AI runner) and Supabase (Postgres, Auth, Storage), with Anthropic Claude and the GitHub App in an external services column. Short labelled arrows connect neighbours. The bar above the canvas reads bramlabs-io/doczoid, High level architecture, with a Refresh with AI button.
bramlabs-io/doczoid · High level architecturegenerated from main · Refresh with AI

What it writes

Five kinds of document, each with its diagram.

One repository feeds as many documents as you need. Each is linked to the repo on its own, with its own kind and its own instructions, and refreshes on its own.

High level architecture

Actors, the application's subsystems, the data they keep, and the external services they talk to. Grouped into containers by tier.

Data lineage

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

Security review

Trust boundaries, authentication paths, how secrets are handled, and the places that deserve a second look.

Solution architecture

The design in context: components, integrations, and the decisions the code embodies, written for the person who has to sign it off.

User guide

What the product does, written for the person using it, from the code that implements it.

Your instructions, kept

Tell the AI how this document should be written: the audience, what to leave out, the names your team uses. The note is stored with the document and applied on every refresh.
The same document in split view. On the left, the text: a summary of what DocZoid is and a What it does section with bullet points. On the right, the architecture diagram fitted to the canvas. The repo bar above both reads bramlabs-io/doczoid, High level architecture, Refresh with AI.
Document and diagram, from one repositorybramlabs-io/doczoid · main

Every one of them is a real DocZoid document with 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.

Refresh

Three ways to bring it up to date.

A refresh reads the current code and rewrites the document and its diagram in place. You decide when: by hand, from your AI client, or from CI on every push.

A refresh does not throw away your work. A version snapshot is taken first, your instructions to the AI are applied again, and the result is written into the live document, so people with it open see the change arrive. 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
The bar above a repo-linked document: bramlabs-io/doczoid, High level architecture, and the buttons Refresh with AI, Instructions, and Detach.
  1. In the editorEvery repo-linked doc carries a Refresh with AI button. A version snapshot is taken before the run, so a bad refresh is one click to undo.
  2. From your AI clientThe MCP server exposes the same refresh as a tool, so Claude Code or Cursor can refresh the doc for the change it just made.
  3. From CI, on every pushThe refresh is an authenticated API call. A workflow step on main runs it on every push, and the doc never waits for a person.
The repo bar on a linked documentmain
snapshot before every runinstructions keptRead-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.
The Repos page in DocZoid. Under Connected repos, bramlabs-io/doczoid on main with a Disconnect button. Under GitHub accounts, the bramlabs-io organisation with Manage on GitHub and Disconnect account, and a Connect GitHub account button.
Repos · Bram LabsGitHub App · read access

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 document is an ordinary DocZoid document: edit the prose, move a box, restyle a container, add a note. A refresh rewrites it from the current code, after taking a version snapshot, so you can always step back.
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.

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