A
kubesphere
68.3
17,080 stars · license n/a
DevOps
lens leads by 6.8 · narrow
A
68.3
17,080 stars · license n/a
B · leads
75.1
23,248 stars · MIT
kubesphere versus lens is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. kubesphere is written mainly in Go; lens is written mainly in an unspecified language. The composite score is 68.3 for kubesphere and 75.1 for lens.
lens has 23,248 GitHub stars to kubesphere's 17,080, a gap of 6,168 (1.36×). Forks are 2,752 for kubesphere and 1,466 for lens. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 100 versus 92.
Push history: kubesphere was last pushed on 15 July 2026 (125 days ago), and lens was last pushed on 11 February 2025 (644 days ago). Open issues stand at 350 for kubesphere (0.020 per star) and 1,165 for lens (0.050 per star). Issue-health scores are 70 and 52; activity scores are 36 and 16.
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. lens 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 30 for kubesphere and 96 for lens. This is a procurement signal, not legal advice.
Only lens is marked self-hostable here (23,248 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: kubesphere is unpriced in this catalog, lens is open source.
The lead is split. kubesphere is furthest ahead on recent activity (36 to 16), while lens is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
lens finishes ahead at 75.1 against kubesphere at 68.3, a 6.8 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 | kubesphere | lens |
|---|---|---|
| GitHub stars | 17,080 | 23,248 |
| Forks | 2,752 | 1,466 |
| Open issues | 350 | 1,165 |
| Adoption | 97 | 100 |
| Activity | 36 | 16 |
| Community | 100 | 92 |
| Issue health | 70 | 52 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 68.3 | 75.1 |
The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
Lens - The way the world runs Kubernetes
lens has more GitHub stars: 23,248 versus 17,080 for kubesphere. The gap is 6,168 stars.
kubesphere was pushed more recently: 15 July 2026 versus 11 February 2025 for lens. That is 519 days apart.
Only lens is marked self-hostable. kubesphere is not.
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. lens 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.
lens scores 75.1 and kubesphere scores 68.3. This page calls that a narrow lead for lens.