Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
Jujutsu (jj)
Git-compatible VCS with a mutable working-copy commit, stable change IDs, an operation log with undo, automatic rebasing of descendants, and first-class conflicts. Started by a Google engineer; default backend stores data in git repositories.
jj-vcs.github.io/jj/Active
v0.46.0 released 2026-10-07; jj-vcs/jj pushed 2026-10-25 (GitHub API). (checked 2026-10-25)
In Version control beyond git
Where it stands apart
- How is it mainly sustained? big company side project (13% of 16 others)
- What is the basic unit of history? (pick the most specific that applies) changes with stable IDs that survive rewrites (even if stored as commits) (0% of 19 others)
- Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? yes, the workflow is built around stacks (20% of 15 others)
- How are merge conflicts mainly handled? first-class: a conflict can be recorded and resolved later (18% of 17 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)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (67% of 18 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)
- Is it designed with AI coding agents in mind? no (65% of 20 others)
- What size of project is it designed for? ordinary source repositories (74% of 19 others)
Nearest neighbors
- Game of Trees (Got) 71% of 17 shared answers match
- Pijul 69% of 16 shared answers match
- git-branchless 65% of 17 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) | source 2026-10-25 |
| How is it mainly sustained? | stands apart big company side project README: started as a hobby project, now the author's full-time project at Google with other Googlers helping, but 'not a supported Google product'. | source 2026-10-25 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes | source 2026-10-25 |
| Do you need an account to use it? | no account Local CLI VCS; no account. | 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) Default backend stores data in git repositories. | source 2026-10-26 |
| How does it relate to git repositories? | built on git: reads and writes git repositories directly Default storage backend uses git repositories; colocated repos work with git tools. Pluggable backends exist (Google uses its own internally). | source 2026-10-25 |
| Where does the authoritative copy of a project live? | every clone is a full peer; servers are optional | source 2026-10-25 |
| Can you commit, branch, and read history with no network connection? | yes | source 2026-10-25 |
| Is it designed with AI coding agents in mind? | no Not mentioned in README; agents use it, but it was not designed around them. | source 2026-10-25 |
| Which layer of the stack does it mainly replace? | the version control system itself Positions itself as a new VCS, though in practice most users run it over git repos and git remotes. | source 2026-10-25 |
| What is the basic unit of history? (pick the most specific that applies) | stands apart changes with stable IDs that survive rewrites (even if stored as commits) Commits are snapshots, but every change has a stable change ID that survives rewrites, plus an operation log. | source 2026-10-25 |
| Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? | stands apart yes, the workflow is built around stacks No stack command; automatic rebase of descendants makes stacks the natural workflow. | source 2026-10-25 |
| How are merge conflicts mainly handled? | stands apart first-class: a conflict can be recorded and resolved later README: conflicts are first-class objects; resolutions propagate through descendants. | source 2026-10-25 |
| What size of project is it designed for? | ordinary source repositories Not monorepo-specific in the open-source release; Google runs it against its own backend. | source 2026-10-25 |
| Is code review part of the product? | no review workflow Pushes bookmarks to git remotes; no built-in review or forge integration. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/jj-vcs/jj · read 2026-10-25
- Web page · jj-vcs.github.io/jj/ · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.