A · level
Gitea
96.5
59,134 stars · MIT
DevOps
Too close to call · 96.5 to 96.5
A · level
96.5
59,134 stars · MIT
B · level
96.5
44,388 stars · Apache-2.0
Gitea versus kong 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; kong is written mainly in Lua. The composite score is 96.5 for Gitea and 96.5 for kong.
Gitea has 59,134 GitHub stars to kong's 44,388, a gap of 14,746 (1.33×). Forks are 7,414 for Gitea and 5,242 for kong. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 96.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 233 for kong (0.005 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. kong 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 kong. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and kong (44,388 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, kong is open source.
The lead is split. Gitea is furthest ahead on fork community (100 to 96), while kong is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Composite score: Gitea 96.5, kong 96.5. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | kong |
|---|---|---|
| GitHub stars | 59,134 | 44,388 |
| Forks | 7,414 | 5,242 |
| Open issues | 2,172 | 233 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 96.5 |
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.
🦍 The API and AI Gateway
Gitea has more GitHub stars: 59,134 versus 44,388 for kong. The gap is 14,746 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Gitea and kong 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. kong 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.
Neither tool clears a one-point margin. Gitea scores 96.5 and kong scores 96.5.