Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
zz
Collaboration layer for open source where humans and AI agents work as peers: hosted git repos, a protocol for posting, claiming, reviewing, and merging work in 'Lanes', and per-repo 'Ladder' summaries stored as git notes.
zzmq.dev/Active
Repo zzmq-dev/zz created 2026-10-12, pushed 2026-10-25 (GitHub API); npm zzmq 1.2.0 published 2026-10-15. Began as an entry in Cloudflare's 'next git platform' competition. (checked 2026-10-25)
In Version control beyond git
Where it stands apart
- Can it run entirely on your own device or infrastructure, without the maker's servers? partly (some features need the maker's servers) (11% of 19 others)
- Do you need an account to use it? account required (22% of 18 others)
- Is it designed with AI coding agents in mind? yes, agents are a primary design target (20% of 20 others)
What it shares with most of the community
- Is it actively maintained? active (90% of 20 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (53% of 19 others)
- Who is it for? developers (90% of 20 others)
- How does it relate to git repositories? built on git: reads and writes git repositories directly (53% of 19 others)
- Can you commit, branch, and read history with no network connection? yes (94% of 17 others)
- What is the basic unit of history? (pick the most specific that applies) snapshots (commits) with no identity that survives a rewrite (74% of 19 others)
- Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? no (53% of 15 others)
- How are merge conflicts mainly handled? must be resolved before the merge or commit completes (65% of 17 others)
- What size of project is it designed for? ordinary source repositories (74% of 19 others)
Not documented
The public sources we read don't say:
- How is it mainly sustained?
Nearest neighbors
- Cursor Origin 86% of 14 shared answers match
- Gitea 81% of 16 shared answers match
- Forgejo 75% of 16 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) BSD-2-Clause (GitHub API); the site does not state a license. | source 2026-10-25 |
| How is it mainly sustained? | Not documented Started as a competition entry; no funding or operator info found. | source 2026-10-26 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | stands apart partly (some features need the maker's servers) Runs on Cloudflare (Workers, Durable Objects, D1, Artifacts); the engine runs locally against a plain git clone in --local mode; no turnkey self-hosting. | source 2026-10-25 |
| Do you need an account to use it? | stands apart account required zz login with Cloudflare or Google account; username is your email. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | git (repository format and protocol) Hosted git repos with git notes. | source 2026-10-26 |
| How does it relate to git repositories? | built on git: reads and writes git repositories directly | source 2026-10-25 |
| Where does the authoritative copy of a project live? | one central server per project (hosted or self-hosted) Hosted on zzmq.dev. | source 2026-10-25 |
| Can you commit, branch, and read history with no network connection? | yes Through ordinary git clones; Lanes and Ladders need the service. | source 2026-10-25 |
| Is it designed with AI coding agents in mind? | stands apart yes, agents are a primary design target Humans and agents share one kind of identity and one protocol. | source 2026-10-25 |
| Which layer of the stack does it mainly replace? | the forge layer (hosting, review, or merging) | source 2026-10-25 |
| What is the basic unit of history? (pick the most specific that applies) | snapshots (commits) with no identity that survives a rewrite | source 2026-10-25 |
| Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? | no Large tasks decompose into parallel sub-task Lanes, not stacks. | source 2026-10-25 |
| How are merge conflicts mainly handled? | must be resolved before the merge or commit completes A coordinator merges with a three-way merge and raises an Ask on conflict. | source 2026-10-25 |
| What size of project is it designed for? | ordinary source repositories | source 2026-10-25 |
| Is code review part of the product? | yes, it has its own review interface Any participant may review; merge is a separate step. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/zzmq-dev/zz · read 2026-10-25
- Web page · zzmq.dev/ · read 2026-10-25
- Web page · zzmq.dev/docs/architecture/ · read 2026-10-25
- Web page · zzmq.dev/docs/overview/ · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.