A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 10.6 · clear
A · leads
96.5
59,134 stars · MIT
B
85.9
4,737 stars · Apache-2.0
Gitea versus werf 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 85.9 for werf.
Gitea has 59,134 GitHub stars to werf's 4,737, a gap of 54,397 (12.48×). Forks are 7,414 for Gitea and 241 for werf. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 62.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and werf was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 10 for werf (0.002 per star). Issue-health scores are 70 and 96; 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. werf 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 werf. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and werf (4,737 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, werf is open source.
The lead is split. Gitea is furthest ahead on fork community (100 to 62), while werf is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against werf at 85.9, a 10.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 | werf |
|---|---|---|
| GitHub stars | 59,134 | 4,737 |
| Forks | 7,414 | 241 |
| Open issues | 2,172 | 10 |
| Adoption | 100 | 77 |
| Activity | 100 | 100 |
| Community | 100 | 62 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 85.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.
A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
Gitea has more GitHub stars: 59,134 versus 4,737 for werf. The gap is 54,397 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Gitea and werf 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. werf 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 werf scores 85.9. This page calls that a clear lead for Gitea.