# Pijul Distributed version control. Source: [Console review]() Website: [https://pijul.org/]() Profile updated: 2026-10-16 ## Supported tech stack Research checked: 2026-10-11 ### Runs on - FreeBSD (Operating system) - Linux (Operating system) - Windows (Operating system) - macOS (Operating system) ### Written in - Rust (Language) Source: [Research source]() Documented compatibility; coverage may be incomplete. Written in describes implementation, not user-project language support. Version-control tool builds with Rust and documents macOS/Linux/FreeBSD installation plus community Windows binaries. ## Console’s review — 2026-04-23 Reviewed: 2026-04-23 Author: [David Mytton]() Citation: [This review]() ### What we like Independent changes can be applied in any order without changing the result - much simpler than rebase. Conflicts are expected and considered a first-class state that can be resolved, then never come back. Changes are stored as patches which model an atomic unit of work rather than a snapshot or version. ### Tradeoffs Development seems sporadic, although it is seemingly active. This review reflects Console’s assessment at publication on 2026-04-23. Features and limitations may have changed since the review date. ## Is Pijul a fit? Based on [Console’s review published on 2026-04-23](). Summary updated: 2026-10-16 ### Who it’s for Developers of distributed projects should consider Pijul for version control ### Why consider it Pijul allows for independent changes to be applied in any order without changing the result [Selection criteria]() · [About Console]() · [Browse tools]()