A · leads
jenkins
92.9
26,788 stars · MIT
DevOps
jenkins leads by 27.0 · decisive
A · leads
92.9
26,788 stars · MIT
B
65.9
17,080 stars · license n/a
jenkins versus kubesphere is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. jenkins is written mainly in Java; kubesphere is written mainly in Go. The composite score is 92.9 for jenkins and 65.9 for kubesphere.
jenkins has 26,788 GitHub stars to kubesphere's 17,080, a gap of 9,708 (1.57×). Forks are 9,837 for jenkins and 2,752 for kubesphere. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 86.
Push history: jenkins 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 3,618 for jenkins (0.135 per star) and 350 for kubesphere (0.020 per star). Issue-health scores are 34 and 70; activity scores are 100 and 36.
jenkins 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 jenkins and 30 for kubesphere. This is a procurement signal, not legal advice.
Only jenkins is marked self-hostable here (26,788 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: jenkins is open source, kubesphere is unpriced in this catalog.
The lead is split. jenkins is furthest ahead on license flexibility (96 to 30), while kubesphere is furthest ahead on issue health (70 to 34). Choose the dimension a rollout cannot compromise on.
jenkins finishes ahead at 92.9 against kubesphere at 65.9, a 27.0 point decisive 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 | jenkins | kubesphere |
|---|---|---|
| GitHub stars | 26,788 | 17,080 |
| Forks | 9,837 | 2,752 |
| Open issues | 3,618 | 350 |
| Adoption | 100 | 96 |
| Activity | 100 | 36 |
| Community | 100 | 86 |
| Issue health | 34 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 92.9 | 65.9 |
Jenkins automation server
The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
jenkins has more GitHub stars: 26,788 versus 17,080 for kubesphere. The gap is 9,708 stars.
jenkins was pushed more recently: 17 November 2026 versus 15 July 2026 for kubesphere. That is 125 days apart.
Only jenkins is marked self-hostable. kubesphere is not.
jenkins 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.
jenkins scores 92.9 and kubesphere scores 65.9. This page calls that a decisive lead for jenkins.