A · leads
kong
97.9
44,388 stars · Apache-2.0
DevOps
kong leads by 32.7 · decisive
A · leads
97.9
44,388 stars · Apache-2.0
B
65.2
17,080 stars · license n/a
kong versus kubesphere is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. kong is written mainly in Lua; kubesphere is written mainly in Go. The composite score is 97.9 for kong and 65.2 for kubesphere.
kong has 44,388 GitHub stars to kubesphere's 17,080, a gap of 27,308 (2.60×). Forks are 5,242 for kong and 2,752 for kubesphere. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 92.
Push history: kong 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 233 for kong (0.005 per star) and 350 for kubesphere (0.020 per star). Issue-health scores are 84 and 70; activity scores are 100 and 36.
kong 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. 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 kong and 30 for kubesphere. This is a procurement signal, not legal advice.
Only kong is marked self-hostable here (44,388 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: kong is open source, kubesphere is unpriced in this catalog.
kong is ahead on every scored dimension that is not level. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is fork community at 8 points (100 vs 92).
kong finishes ahead at 97.9 against kubesphere at 65.2, a 32.7 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 | kong | kubesphere |
|---|---|---|
| GitHub stars | 44,388 | 17,080 |
| Forks | 5,242 | 2,752 |
| Open issues | 233 | 350 |
| Adoption | 100 | 91 |
| Activity | 100 | 36 |
| Community | 100 | 92 |
| Issue health | 84 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 97.9 | 65.2 |
🦍 The API and AI Gateway
The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
kong has more GitHub stars: 44,388 versus 17,080 for kubesphere. The gap is 27,308 stars.
kong was pushed more recently: 17 November 2026 versus 15 July 2026 for kubesphere. That is 125 days apart.
Only kong is marked self-hostable. kubesphere is not.
kong 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. 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.
kong scores 97.9 and kubesphere scores 65.2. This page calls that a decisive lead for kong.