Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
Pijul
Distributed VCS based on a theory of patches: independent changes commute, conflicts are first-class and resolved by a change of their own. Hosting on the Nest.
pijul.org/Active
pijul 1.0.0-beta.24 published to crates.io 2026-09-14; still beta after many years. (checked 2026-10-25)
In Version control beyond git
Where it stands apart
- How does it relate to git repositories? own storage format, one-time import or no git interop (21% of 19 others)
- What is the basic unit of history? (pick the most specific that applies) patches that commute (5% of 19 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)
- 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)
- 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)
- Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? no (53% of 15 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
- Darcs 94% of 16 shared answers match
- Mercurial 81% of 16 shared answers match
- Fossil 69% of 16 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active Active but slow; never left beta. | source 2026-10-25 |
| How is the main thing licensed? | copyleft or source-available with restrictions GPL-2.0-or-later. | source 2026-10-25 |
| How is it mainly sustained? | Not documented Only an OpenCollective fund is mentioned; who runs it is unclear. | source 2026-10-26 |
| 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 DVCS; Nest hosting is optional. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | none of these (its own format or interface) Own patch format. | source 2026-10-26 |
| How does it relate to git repositories? | stands apart own storage format, one-time import or no git interop Has a 'pijul git' import command; no ongoing two-way sync. | 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 | source 2026-10-25 |
| Which layer of the stack does it mainly replace? | the version control system itself | source 2026-10-25 |
| What is the basic unit of history? (pick the most specific that applies) | stands apart patches that commute | source 2026-10-25 |
| Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? | no No stacks concept; dependencies between patches are tracked automatically instead. | source 2026-10-25 |
| How are merge conflicts mainly handled? | stands apart first-class: a conflict can be recorded and resolved later 'Conflicts never come back' once resolved; conflicts are part of the repo state. | 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? | no review workflow The tool itself has no review; the Nest host has discussions. | source 2026-10-25 |
Sources
This page was derived from:
- Package registry · crates.io/crates/pijul · read 2026-10-25
- Web page · pijul.org/ · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.