A Git forge with no landlord.
Sign in and push to repositories that live on the peer-to-peer Radicle network — not an opaque platform. Your identity is a real Radicle key that you own and control. Your repos replicate across peers. If Radish goes dark tomorrow, your project doesn't.
Platform forges
Radish
Your repos
Live on their servers
Your repos
Live on the peer-to-peer Radicle network
Identity
Owned by the platform, revocable
Identity
A real Radicle key — yours forever
Going dark
If they're down, you're down
Going dark
Any Radicle peer keeps your project online
Moderation
Their rules. Their reasons. Their court.
Moderation
Your project's delegates, on-network
scroll
Decentralised Git
Browser-native contributions
No installation required
GitHub OAuth sign-in
Real Radicle keys
Open issues from your browser
Submit patches
Portable identity
Peer-to-peer storage
Code review in the browser
Sovereign infrastructure
Export your key anytime
Decentralised Git
Browser-native contributions
No installation required
GitHub OAuth sign-in
Real Radicle keys
Open issues from your browser
Submit patches
Portable identity
Peer-to-peer storage
Code review in the browser
Sovereign infrastructure
Export your key anytime
Repositories on this node
Seeded and available for browsing and contribution
r
radicle.xyz
Radicle website including documentation and guides
r
radicle-desktop
Radicle desktop app
r
rips
Radicle Improvement Proposals (RIPs)
r
radicle-git
Git libraries for Radicle
h
HardenedBSD-pkg
HardenedBSD Package Manager
p
public-repo-1
This is a test repository. Hello, world!
r
radicle-ci-broker
Radicle CI broker
h
heartwood
Radicle Heartwood Protocol & Stack
r
radicle-explorer
Radicle web interface
r
radicle-tui
Radicle terminal user interface
r
radicle-infra
Radicle Infrastructure as Code (NixOS, OpenTofu, …)
r
radicle-job
Radicle Job Collaborative Object
r
radicle-native-ci
Radicle CI adapter for native CI
Why Radish
Sovereignty without the friction
Portable identity
Your key follows you across any Radish deployment. Sign in anywhere and your Radicle identity — issues, patches, history — is already there.
Keys never leave your hands
Private keys are fetched from your GitHub repo on demand, used to sign the operation, and dropped immediately. Radish doesn't store your key unless you ask it to.
An on-ramp, not a lock-in
When contributors are ready to run their own node, they export their key from Radish and import it into
rad. Identity and history carry over seamlessly.Radicle stays decentralised
Radish is just a UI. Data lives on the Radicle peer-to-peer network. You control your seed node; no third-party platform owns your repositories.