A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 11.7 · clear
A · leads
96.5
59,134 stars · MIT
B
84.8
5,620 stars · Apache-2.0
Gitea versus uncloud is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 96.5 for Gitea and 84.8 for uncloud.
Gitea has 59,134 GitHub stars to uncloud's 5,620, a gap of 53,514 (10.52×). Forks are 7,414 for Gitea and 184 for uncloud. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 59.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and uncloud was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 92 for uncloud (0.016 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
Gitea is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. uncloud is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for Gitea and 96 for uncloud. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and uncloud (5,620 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Gitea is open source, uncloud is open source.
The lead is split. Gitea is furthest ahead on fork community (100 to 59), while uncloud is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against uncloud at 84.8, a 11.7 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Gitea | uncloud |
|---|---|---|
| GitHub stars | 59,134 | 5,620 |
| Forks | 7,414 | 184 |
| Open issues | 2,172 | 92 |
| Adoption | 100 | 79 |
| Activity | 100 | 100 |
| Community | 100 | 59 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 84.8 |
Gitea is a lightweight self-hosted Git service with issues, pull requests, and actions. It is the usual choice when a team wants a small forge they can run themselves.
A lightweight tool for deploying and managing containerised applications across a network of Docker hosts. Bridging the gap between Docker and Kubernetes ✨
Gitea has more GitHub stars: 59,134 versus 5,620 for uncloud. The gap is 53,514 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Gitea and uncloud as self-hostable. Confirm each project's deploy docs before you plan a migration.
Gitea is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. uncloud is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Gitea scores 96.5 and uncloud scores 84.8. This page calls that a clear lead for Gitea.