A · leads
Coolify
98.8
66,171 stars · Apache-2.0
DevOps
Coolify leads by 2.6 · narrow
A · leads
98.8
66,171 stars · Apache-2.0
B
96.2
59,134 stars · MIT
Coolify versus Gitea is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Coolify is written mainly in PHP; Gitea is written mainly in Go. The composite score is 98.8 for Coolify and 96.2 for Gitea.
Coolify has 66,171 GitHub stars to Gitea's 59,134, a gap of 7,037 (1.12×). Forks are 6,003 for Coolify and 7,414 for Gitea. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 98 versus 100.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and Gitea was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 2,172 for Gitea (0.037 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
Coolify 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. 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. License scores in this pair are 96 for Coolify and 96 for Gitea. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and Gitea (59,134 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: Coolify is open source, Gitea is open source.
The lead is split. Coolify is furthest ahead on issue health (96 to 70), while Gitea is furthest ahead on fork community (100 to 98). Choose the dimension a rollout cannot compromise on.
Coolify finishes ahead at 98.8 against Gitea at 96.2, a 2.6 point narrow 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 | Coolify | Gitea |
|---|---|---|
| GitHub stars | 66,171 | 59,134 |
| Forks | 6,003 | 7,414 |
| Open issues | 149 | 2,172 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 98 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.8 | 96.2 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
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.
Coolify has more GitHub stars: 66,171 versus 59,134 for Gitea. The gap is 7,037 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and Gitea as self-hostable. Confirm each project's deploy docs before you plan a migration.
Coolify 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Coolify scores 98.8 and Gitea scores 96.2. This page calls that a narrow lead for Coolify.