Dependency removed: Central authorities, single providers, and bottleneck services - a decentralized system has no single point of control or failure.
Decentralization is both a technical architecture and a governance philosophy. Technically, it means distributing services so no single node is essential. Politically, it means distributing control so no single entity can shut down, censor, or surveil the whole system.
Decentralized systems are more resilient by design: there is nothing to seize, nothing to block, and no single administrator to coerce.
- Peer-to-peer systems - BitTorrent for file sharing; Syncthing for sync without a server; IPFS for content-addressed storage
- Federation - Matrix for messaging; ActivityPub for social; Gitea federation; each instance is independent and interoperable
- Distributed storage - Ceph, MinIO clusters; IPFS; content-addressed storage with redundancy across nodes
- Consensus systems - how distributed systems agree on state without a central coordinator
- Community ownership - infrastructure owned and operated by the community it serves; no single commercial dependency
- Shared infrastructure - cost and maintenance burden shared across participants; governance and access policies
- Cooperative hosting - member-owned hosting cooperatives; accountability structures; democratic governance
- Volunteer networks - Tor relays; Freenet; distributed infrastructure powered by volunteer contribution
| Technology |
Use Case |
Dependency Removed |
| Syncthing |
File sync |
Cloud sync provider |
| Matrix (self-hosted) |
Messaging |
Discord, WhatsApp, Slack |
| Gitea (federated) |
Code hosting |
GitHub, GitLab |
| IPFS |
Content hosting |
Web hosting providers |
| Meshtastic |
Communications |
Cellular carriers |
| Tor |
Anonymous networking |
ISP-visible browsing |