A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 9.6 · clear
A · leads
96.5
59,134 stars · MIT
B
86.9
6,504 stars · MIT
Gitea versus server-survival is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Gitea is written mainly in Go; server-survival is written mainly in JavaScript. The composite score is 96.5 for Gitea and 86.9 for server-survival.
Gitea has 59,134 GitHub stars to server-survival's 6,504, a gap of 52,630 (9.09×). Forks are 7,414 for Gitea and 720 for server-survival. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 74.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and server-survival was last pushed on 04 November 2026 (13 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 21 for server-survival (0.003 per star). Issue-health scores are 70 and 96; activity scores are 100 and 92.
Both Gitea and server-survival are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and server-survival (6,504 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, server-survival is open source.
The lead is split. Gitea is furthest ahead on fork community (100 to 74), while server-survival is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against server-survival at 86.9, a 9.6 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 | server-survival |
|---|---|---|
| GitHub stars | 59,134 | 6,504 |
| Forks | 7,414 | 720 |
| Open issues | 2,172 | 21 |
| Adoption | 100 | 80 |
| Activity | 100 | 92 |
| Community | 100 | 74 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 86.9 |
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.
Tower defense game that teaches cloud architecture. Build infrastructure, survive traffic, learn scaling.
Gitea has more GitHub stars: 59,134 versus 6,504 for server-survival. The gap is 52,630 stars.
Gitea was pushed more recently: 17 November 2026 versus 04 November 2026 for server-survival. That is 13 days apart.
Yes. This catalog marks both Gitea and server-survival 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. server-survival 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Gitea scores 96.5 and server-survival scores 86.9. This page calls that a clear lead for Gitea.