A · leads
devops-exercises
71.9
86,874 stars · license n/a
DevOps
devops-exercises leads by 10.3 · clear
A · leads
71.9
86,874 stars · license n/a
B
61.6
17,080 stars · license n/a
devops-exercises versus kubesphere is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. devops-exercises is written mainly in Python; kubesphere is written mainly in Go. The composite score is 71.9 for devops-exercises and 61.6 for kubesphere.
devops-exercises has 86,874 GitHub stars to kubesphere's 17,080, a gap of 69,794 (5.09×). Forks are 20,674 for devops-exercises and 2,752 for kubesphere. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 80.
Push history: devops-exercises was last pushed on 27 December 2025 (325 days ago), and kubesphere was last pushed on 15 July 2026 (125 days ago). Open issues stand at 59 for devops-exercises (0.001 per star) and 350 for kubesphere (0.020 per star). Issue-health scores are 96 and 70; activity scores are 36 and 36.
devops-exercises 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. 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 30 for devops-exercises and 30 for kubesphere. This is a procurement signal, not legal advice.
Neither devops-exercises nor kubesphere is marked self-hostable in this catalog (86,874 and 17,080 stars). Deploy scores stay at 35 and 35. Treat both as hosted products until their own docs say you can run them. Pricing labels on file: devops-exercises is unpriced in this catalog, kubesphere is unpriced in this catalog.
devops-exercises is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 26 points (96 vs 70), and the tightest is self-hosting at 0 points (35 vs 35).
devops-exercises finishes ahead at 71.9 against kubesphere at 61.6, a 10.3 point clear 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 | devops-exercises | kubesphere |
|---|---|---|
| GitHub stars | 86,874 | 17,080 |
| Forks | 20,674 | 2,752 |
| Open issues | 59 | 350 |
| Adoption | 100 | 86 |
| Activity | 36 | 36 |
| Community | 100 | 80 |
| Issue health | 96 | 70 |
| License | 30 | 30 |
| Self-hosting | 35 | 35 |
| Composite | 71.9 | 61.6 |
Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions
The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
devops-exercises has more GitHub stars: 86,874 versus 17,080 for kubesphere. The gap is 69,794 stars.
kubesphere was pushed more recently: 15 July 2026 versus 27 December 2025 for devops-exercises. That is 200 days apart.
Neither devops-exercises nor kubesphere is marked self-hostable in this catalog.
devops-exercises 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. 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.
devops-exercises scores 71.9 and kubesphere scores 61.6. This page calls that a clear lead for devops-exercises.