Radicle is an open-source, peer-to-peer code collaboration stack on Git with no central controlling entity, cryptographic identities, and local-first storage.
Key Takeaways
Repositories replicate across peers via a custom gossip protocol; users own all data and control their workflow without third-party reliance.
Social artifacts (issues, patches, discussions) are stored as Git objects via Collaborative Objects (COBs) and signed with public-key cryptography.
Stack is modular: CLI, web UI, TUI, Radicle Node (NoiseXK), and HTTP Daemon can be swapped or extended independently.
Current release is 1.8.0 (2026-03-26); Desktop client launched June 2025. Runs on Linux, macOS, BSD only.
Private repos are supported; a recent vulnerability in Signed References was disclosed and patched alongside the 1.8.0 cycle.
Hacker News Comment Review
Spam and access control is an active concern: by default, seeding a repo shares issues and patches only with followed peers; rad follow and rad block are the current primitive tools, with richer filtering left to builders.
Air-gapped or on-premises multi-node deployment (e.g., three machines isolated from the public network) is technically possible but poorly documented, frustrating teams wanting a self-contained alternative to GitLab.
Commenters see Radicle as a strong fit for agentic workflows given cryptographic identities and signed artifacts by default; the team is actively soliciting agentic-workflow feedback on Zulip.
Notable Comments
@xvilka: Local-only multi-node deployment lacks documentation and requires serious scripting not covered in official guides.
@figbert: Long-standing repo deletion limitations drove early adopters away; private repo support is now more fleshed out.
