For teams
Built for the people who have to agree on it.
Documentation is not a solo activity, and neither is architecture. Everything in DocZoid is multiplayer by default: the doc, the canvas, and the deck.
- Read-only repo access
- Works with Claude Code, Cursor, Claude Desktop
- Free for one editor
While you work
You can see what everyone is doing.
Text edits, diagram changes, and slide changes all broadcast as they happen, with an autosave indicator that tells you the truth.
Live cursors
Presence, with detail
Autosave you can verify
Talking about the work
The conversation stays with the thing it is about.
Four different ways to say something, because a note on a shape is not the same as a question about a paragraph.
Chat
Review notes
Pinned comments
Anchored comments
A notification bell carries the unread badge for document updates, comments, replies, and team invitations.
Who can do what
Four roles, two visibilities, two kinds of link.
Every document is private to you or visible to the team, so a draft can become a published thing without moving anywhere.
A public link is read-only and opens for anyone. A team link opens only for your team and is always available for quick internal sharing. Both come with a QR code, which is more useful in a workshop than it sounds.
Teams and sharing in the guide- Owner
- Full control of the team, its content, and its members.
- Admin
- Manage content and members.
- Member
- Create and edit content.
- Viewer
- Read-only. Free on every plan.
Every document keeps automatic versions as you work, and you can name one deliberately. Versions are numbered semantically and record who made the change and when.
Consultancies
If documentation is your deliverable.
Client work produces exactly what DocZoid is for: a system somebody else has to understand after you leave. There is a founding partner programme, and it is open.
Invite the people who have to agree with you.
- Read-only repo access
- Works with Claude Code, Cursor, Claude Desktop
- Free for one editor