A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 3.2 · narrow
A · leads
96.5
59,134 stars · MIT
B
93.3
30,249 stars · Apache-2.0
Gitea versus kestra 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; kestra is written mainly in Java. The composite score is 96.5 for Gitea and 93.3 for kestra.
Gitea has 59,134 GitHub stars to kestra's 30,249, a gap of 28,885 (1.95×). Forks are 7,414 for Gitea and 3,538 for kestra. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 92.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and kestra was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 651 for kestra (0.022 per star). Issue-health scores are 70 and 70; 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. kestra 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 kestra. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and kestra (30,249 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, kestra is open source.
Gitea is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 8 points (100 vs 92), and the tightest is self-hosting at 0 points (100 vs 100).
Gitea finishes ahead at 96.5 against kestra at 93.3, a 3.2 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 | Gitea | kestra |
|---|---|---|
| GitHub stars | 59,134 | 30,249 |
| Forks | 7,414 | 3,538 |
| Open issues | 2,172 | 651 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 92 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 93.3 |
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.
Orchestrate everything, everywhere. The open-source control plane for workflows across data, infrastructure, business processes and AI agents. Declarative YAML, event-driven, any language, Git-versioned, scalable to millions of executions.
Gitea has more GitHub stars: 59,134 versus 30,249 for kestra. The gap is 28,885 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Gitea and kestra 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. kestra 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 kestra scores 93.3. This page calls that a narrow lead for Gitea.