A community can run its own infrastructure.
Self-hosted CI. Local-first deployment. Source that copies between nodes without a forge. Payments that prove a service was delivered. Each project comes with its protocol, its evidence model, and a playbook you can fork. Any community can adopt it, audit it, or replace it.
// no premine · no roadmap · no issuer · no censorship
The thesis
Most “decentralized” projects still lean on a central forge for source, a hosted CI for tests, a SaaS dashboard for deployment, and a custodial platform for money. Each handoff is a chokepoint. A community that depends on those handoffs isn’t running its own infrastructure. It’s renting it.
The projects below pull each layer back into the community. Source copies over Radicle. CI builds locally and writes signed test results to disk. Deployment ties approved bytes to a hash, then checks the hash on install. Service payments are gated by evidence and settled off-chain. Every protocol is versioned, language-agnostic, and forkable.
The projects
poor-mans-ci
Self-hosted CI for communities that control their own code. Runs tests and builds without GitHub Actions or any central provider. Writes signed test results and artifact hashes to disk. The evidence on disk is the contract.
poor-mans-cd
Local-first deployment. Each release names the exact bytes you want to install. The deploy host checks the sha256 first and refuses to install if it doesn’t match. Every install writes a receipt to disk. The dashboard rebuilds itself from those receipts.
radicle-seed-kit
Tools to run an always-on Radicle seed node. Keeps private repos copied between machines. Helps collaborators behind a NAT mirror their work without sharing keys. This is the layer that makes the rest of the suite reachable.
radicle-priorities
The backlog protocol. BDD .feature files are the
source of truth. Radicle issues are where the team talks. The
backlog ships with the code.
(See extremebdd.com for the
methodology site.)
ecsc
Evidence-coupled service channels. Two operators share one Lightning channel and pay each other only when PMCI/PMCD evidence matches the claim. The rule: no signed payment state exists without valid service evidence. Live today on Bitcoin regtest, not mainnet.
What’s queued next
More projects in the same family are queued and will land here as their protocols lock. If you want ECSC promoted from live regtest to public testnet or mainnet, the boundary is disclosed in the demo’s closing card — the code is here today.