Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
GitButler
Git-based version control client (desktop GUI plus 'but' CLI) with parallel and stacked branches, unlimited undo, conflicted commits, and forge integrations; describes itself as built for AI-powered workflows.
gitbutler.com/Active
release/0.22.3 published 2026-08-29; gitbutlerapp/gitbutler pushed 2026-10-25 (GitHub API). (checked 2026-10-25)
In Version control beyond git
Where it stands apart
- Do you need an account to use it? optional account (0% of 18 others)
- Is it designed with AI coding agents in mind? yes, agents are a primary design target (20% of 20 others)
- Which layer of the stack does it mainly replace? the git client and local workflow, on top of git (10% of 20 others)
- Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? available, but not the main workflow (13% of 15 others)
- How are merge conflicts mainly handled? first-class: a conflict can be recorded and resolved later (18% of 17 others)
- Is code review part of the product? no, it hands off to an external forge's review (e.g. GitHub pull requests) (11% of 19 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)
- 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)
- What size of project is it designed for? ordinary source repositories (74% of 19 others)
Nearest neighbors
- Cursor Origin 60% of 15 shared answers match
- Game of Trees (Got) 59% of 17 shared answers match
- git-branchless 59% 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? | copyleft or source-available with restrictions Functional Source License FSL-1.1-MIT (converts to MIT after two years). | source 2026-10-25 |
| How is it mainly sustained? | company with a paid product, tier, or ads Venture-backed company; no pricing page found (gitbutler.com/pricing returned no tiers). Poll bug: no option for 'company, free 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? | stands apart optional account Local git client; forge accounts are added optionally. No login gate found. | 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) Writes ordinary git commits. | 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? | 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? | stands apart yes, agents are a primary design target README: 'built from the ground up for AI-powered workflows' and 'designed for ... modern agentic workflows'. | source 2026-10-25 |
| Which layer of the stack does it mainly replace? | stands apart the git client and local workflow, on top of git | 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 Writes ordinary git commits; parallel branches are applied together in one working directory. | source 2026-10-25 |
| Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? | stands apart available, but not the main workflow Stacked branches are a feature; parallel (virtual) branches are the signature workflow. | source 2026-10-25 |
| How are merge conflicts mainly handled? | stands apart first-class: a conflict can be recorded and resolved later Docs: can 'store the commit marked as conflicted' and resolve later with 'but resolve'. | 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? | stands apart no, it hands off to an external forge's review (e.g. GitHub pull requests) Forge integrations open pull requests on GitHub/GitLab. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/gitbutlerapp/gitbutler · read 2026-10-25
- Web page · docs.gitbutler.com/ · read 2026-10-25
- Web page · docs.gitbutler.com/cli-guides/cli-tutorial/conflict-resolution · read 2026-10-25
- Web page · gitbutler.com/ · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.