Radicle Explorer
LSP for reviewing code changes/diffs in text
Last verified:
What is Radicle Explorer?
Radicle Explorer is a web interface that lets you interact with Radicle, a peer-to-peer code collaboration and publishing stack built on Git, directly from your web browser. It provides a graphical way to browse Radicle repositories, view issues, patches (pull requests), and code reviews without needing to use the command line. The tool connects to publicly available Radicle seed nodes to access decentralized code repositories.
Key features include browsing repositories on seed nodes, viewing and creating issues, examining patches for code review, accessing the Git object database for files, and exploring the decentralized network of repositories. The interface supports local-first operation, meaning it works offline and users own their data. It integrates with the Radicle protocol's Collaborative Objects (COBs) system for social interactions like issues and code review.
Radicle Explorer is designed for developers and open source contributors who want sovereign code infrastructure without relying on centralized platforms like GitHub. It is ideal for teams and individuals who value data ownership, censorship resistance, and peer-to-peer collaboration. The tool is particularly useful for those already familiar with Git who want a web-based interface for Radicle's decentralized code forge.
Radicle Explorer pricing
Pricing model: Freemium
Radicle is completely free and open source software under MIT and Apache 2.0 licenses with no paid tiers. The protocol and clients will remain free software forever. There is no subscription model or pricing structure. Self-hosting costs only electricity if running on your own hardware (Mac/Pi/NUC) plus approximately $10/year per domain. The Radicle team maintains a public server instance at app.radicle.xyz that is free to use. Radworks funds development and may offer hosting services, but the core protocol remains free.
Radicle Explorer pros
- Peer-to-peer architecture with no single controlling entity
- Built on Git for familiar workflow and efficient data transfer
- Local-first design works offline with always-available functionality
- Full control over your data and workflow without third-party reliance
- Cryptographic verification of all data authenticity and authorship
- Open source under MIT and Apache 2.0 licenses
- Web interface accessible directly from browser without CLI knowledge
- Browse repositories, issues, and patches on public seed nodes
- Censorship-resistant code collaboration
- Supports private repositories shared among trusted peers only
- Built-in Tor support for privacy at protocol level
- Modular design allows swapping components and developing custom clients
- Reproducible and signed builds for all binaries
- No subscription fees or corporate control over your code
- Repositories replicated across peers for persistence and availability
Radicle Explorer cons
- Currently only supports Linux, macOS, and BSD (no Windows yet)
- Basic search functionality still work-in-progress
- No native CI/CD capabilities yet (planned for future)
- Advanced code review functionality not fully implemented
- No inbox system for repository notifications yet
- Multi-device support not yet available (single identity per device)
- No built-in GitHub mirroring or full migration tooling yet
- Tor/I2P integrations still early and not thoroughly tested
Frequently asked questions about Radicle Explorer
What is Radicle Explorer and how is it different from GitHub?
Radicle Explorer is a web interface for Radicle, a peer-to-peer code collaboration platform built on Git. Unlike GitHub, there is no single entity controlling the network or user data. Repositories are replicated across peers in a decentralized manner, giving users full control of their data and experience without compromising on social collaboration features. GitHub uses a client-server model while Radicle is truly peer-to-peer.
Do I need to run my own node to use Radicle Explorer?
Yes, a node is essential for Radicle's sovereignty. However, you don't need to keep it running constantly if conserving bandwidth is a concern - Radicle works well while offline. You can also use the public instance at app.radicle.xyz maintained by the Radicle team without running your own node.
How do I browse repositories on seed nodes?
You can browse repositories directly through the web interface by connecting to publicly available seed nodes. The interface lets you explore repositories, issues, and patches on any public node. Once you install Radicle and set up your identity, you gain access to all public repositories on any public node.
Can I create private repositories on Radicle?
Yes, Radicle supports private repositories that are only shared among a trusted set of peers, not the entire network. These are not encrypted at rest but rely on selective replication and are completely invisible to the rest of the network.
How does code review work in Radicle Explorer?
Radicle uses patches (its version of pull requests) implemented via Collaborative Objects (COBs). It supports non-destructive updates to patches and code reviews tied to patch revisions. Patches and issues are stored within Git's object database and are available offline. Advanced code review functionality is still being developed.
What operating systems does Radicle support?
Currently Radicle only works on Linux, macOS, and BSD variants. Windows support is not available yet, but the team plans to add it if there is enough demand from the community.
How do I migrate existing GitHub projects to Radicle?
There are community tools under development for migrating issues and pull requests. Full migration tooling is planned for the future. You can also easily set up a cron job to pull from GitHub and push to Radicle periodically for mirroring, though built-in mirroring is not yet available.
Is Radicle Explorer free to use?
Yes, Radicle is free and open source software under MIT and Apache 2.0 licenses and will remain free software forever. There is no monetization strategy or paid tiers. The protocol doesn't use or depend on any blockchain or cryptocurrency despite Radworks having a governance token.
How does Radicle handle repository persistence when nodes go offline?
Repositories are replicated across multiple peers on the network, remaining available as long as at least one seeding node is online. Users control which repositories they personally host and seed. Certain nodes act as seed nodes - always-on public nodes - ensuring data availability across the network.
Can I self-host the Radicle Explorer web interface?
Yes, there are multiple deployment options: run locally, self-host on your own server, or deploy on static hosting like Vercel. For self-hosting, run npm install && npm build to create a deployment build, then configure your web server to serve the /build directory. You can also use docker-compose for container deployment.