Introducing Radicle Garden
A managed, always-on Radicle node that keeps your repositories reachable when your laptop is not.
Radicle is peer-to-peer infrastructure for code. Your repositories live on your machine, signed by your own key, and replicate to the network through other nodes that happen to be online when someone wants to fetch them.
A Garden subscription gives you a managed, always-on Radicle node that sits alongside the one on your machine and replicates the repositories you care about.
In a nutshell, Radicle Garden is about convenience for those users that prefer it. It is also a great way to give back and support the Radicle project!
A subscription includes:
-
A publicly addressable seed with guaranteed replication for the repositories you choose.
-
Web hosting of those repositories under your own
node-name.radicle.gardensubdomain. -
5 GB of storage to start with (talk to us if you need more).
-
Ongoing maintenance and upgrades, so your node always runs the latest stable release.
-
A simple dashboard for adding or removing repositories on demand.
-
Outgoing webhooks for triggering CI runs on Jenkins or any other engine.
Why a hosted seed is consistent with peer-to-peer
A peer-to-peer protocol guarantees the right to participate, not continuous availability. The protocol guarantees your code will be reachable by any node in the network, as long as there is at least one other node seeding it. It doesn’t guarantee any node will be seeding it, however. Guaranteed availability is something you have to provision deliberately. It doesn’t come for free.
You have three options:
-
Keep a machine running yourself
-
Trust some community-run public permissive seed
-
Pay a small amount for a node that you control – you just don’t have to operate
Garden is the third option. The first two never go away.
What we won’t do
A few things matter to us and are worth stating plainly.
-
We don’t gate the network. Garden is one seed among many. Your local node keeps using whichever other peers it already trusts; we’re an addition, not a replacement.
-
We are walkaway-safe. If Garden disappears tomorrow, your local repositories continue to work, your collaborators can still publish through other peers, and nothing depends on us being around — that is the whole point of building on Radicle in the first place.
-
We don’t see anything you wouldn’t already gossip. For public repositories, we replicate what is by design replicated to any other peer. For private repositories, we only replicate the ones you explicitly add to your
rad idallow-list — and the allow-list is yours to change. -
We don’t need to know the keys of your private node. Identity in Radicle is an ED25519 key pair you generate locally. All commits and identity updates are signed on your machine — Garden never sees the private half of your laptop key. We do operate a custodial node for you, but the actions you really care about take place on your laptop anyway.
Getting started
Please check out the Getting Started Guide.