Skip to content
DevUtils Online

DevOps

Gitea vs kubesphere

Gitea leads by 32.6 · decisive

A · leads

Gitea

96.5

59,134 stars · MIT

Gitea versus kubesphere 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 63.9 for kubesphere.

Gitea has 59,134 GitHub stars to kubesphere's 17,080, a gap of 42,054 (3.46×). Forks are 7,414 for Gitea and 2,752 for kubesphere. On the log scale used inside this pair, adoption is 100 versus 89, and the fork community is 100 versus 89.

Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and kubesphere was last pushed on 15 July 2026 (125 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 350 for kubesphere (0.020 per star). Issue-health scores are 70 and 70; activity scores are 100 and 36.

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. kubesphere is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for Gitea and 30 for kubesphere. This is a procurement signal, not legal advice.

Only Gitea is marked self-hostable here (59,134 stars, deploy score 100). kubesphere is not (17,080 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: Gitea is open source, kubesphere is unpriced in this catalog.

Gitea is ahead on every scored dimension that is not level. Level dimensions: issue health. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is issue health at 0 points (70 vs 70).

Gitea finishes ahead at 96.5 against kubesphere at 63.9, a 32.6 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

Gitea versus kubesphere metrics
Signal Gitea kubesphere
GitHub stars 59,134 17,080
Forks 7,414 2,752
Open issues 2,172 350
Adoption 100 89
Activity 100 36
Community 100 89
Issue health 70 70
License 96 30
Self-hosting 100 35
Composite 96.5 63.9

Gitea

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.

Project site · GitHub · Full profile

kubesphere

The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Gitea or kubesphere?

Gitea has more GitHub stars: 59,134 versus 17,080 for kubesphere. The gap is 42,054 stars.

Which was updated more recently, Gitea or kubesphere?

Gitea was pushed more recently: 17 November 2026 versus 15 July 2026 for kubesphere. That is 125 days apart.

Can I self-host both Gitea and kubesphere?

Only Gitea is marked self-hostable. kubesphere is not.

Which license is easier to embed in a commercial product, Gitea or kubesphere?

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. kubesphere is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the Gitea vs kubesphere score?

Gitea scores 96.5 and kubesphere scores 63.9. This page calls that a decisive lead for Gitea.

Related comparisons