Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
Radicle
Open-source peer-to-peer code collaboration stack built on git: issues, patches, and review stored as signed collaborative objects in git, replicated by seed nodes.
radicle.dev/Active
Radicle 1.10.3 released 2026-09-08 (radicle.dev); heartwood mirror pushed 2026-10-25 (GitHub API). Site moved from radicle.xyz to radicle.dev. (checked 2026-10-25)
In Version control beyond git
Where it stands apart
- How is it mainly sustained? community, foundation, or research (25% of 16 others)
- Where does the authoritative copy of a project live? a network of federated or peer-to-peer servers (5% of 19 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 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)
Nearest neighbors
- Forgejo 88% of 17 shared answers match
- Gitea 88% of 17 shared answers match
- Game of Trees (Got) 82% 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) MIT and Apache-2.0. | source 2026-10-25 |
| How is it mainly sustained? | stands apart community, foundation, or research FAQ: maintainer-led, funded by Radworks grants; free software. | 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 Peer-to-peer; local cryptographic identity, no maker 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) Code, issues and patches stored as git objects. | 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? | stands apart a network of federated or peer-to-peer servers Peer-to-peer gossip network of nodes and seeds. | 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 forge layer (hosting, review, or merging) Replaces GitHub-style hosting and collaboration; git remains the VCS. | 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 Patches have revisions; no stacked-patch workflow documented. | source 2026-10-25 |
| How are merge conflicts mainly handled? | must be resolved before the merge or commit completes | 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 | source 2026-10-25 |
Sources
This page was derived from:
- Web page · radicle.dev/ · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.