Forgejo vs Gitea vs Radicle vs Tangled
All four host Git collaboration without GitHub, but Forgejo and Gitea are self-hosted servers you run, while Radicle replicates repos between peer nodes and Tangled federates over AT Protocol. The real choice is how much central server you want to operate.
How to choose
Decision axis: Server forge or federated network
Pick Forgejo if you want a GitHub-like forge on your own server, with community governance under a non-profit and a documented migration path from Gitea.
Pick Gitea if you want a self-hosted forge with a built-in package registry and Gitea Actions, so existing GitHub Actions workflows can be reused, plus the option of a managed Gitea Cloud instance.
Pick Radicle if you want no central host at all, with repos replicated across peer nodes, signed issues and patches stored in Git, and work that continues offline.
Pick Tangled if you want federated collaboration on AT Protocol with stacked pull requests, Jujutsu-native stacking, and CI on spindles you can self-host.
| Attribute | ||||
|---|---|---|---|---|
| Summary | Self Hosted Git Forge Platform | Self Hosted Git Platform | Peer to Peer Git Code Forge | Federated Git Hosting on AT Protocol |
| Community Score | 0/100 | 0/100 | 0/100 | 0/100 |
| Pricing | ✓ Open Source | ✓ Open Source | ✓ Open Source | ✓ Public Benchmark |
| View pricing → | View pricing → | View pricing → | View pricing → | |
| Platform | WINDOWS, MACOS, LINUX, Web, API | WINDOWS, MACOS, LINUX, Web, API, CLI | LINUX, MACOS, CLI, Web | WINDOWS, Web, API, CLI |
| API / SDK | API + SDK | API + SDK | SDK | API |
| Docs / Source | ||||
| Developer | Forgejo | CommitGo, Inc. | Radicle | Tangled Labs Oy |
| Features |
|
|
|
|
| Integrations |
|
|
|
|
| Use Case Fit |
|
|
|
|
| System Requirements |
|
|
|
|
| Data refreshed |



