A · leads
apisix
96.2
17,333 stars · Apache-2.0
DevOps
apisix leads by 27.1 · decisive
A · leads
96.2
17,333 stars · Apache-2.0
B
69.1
17,080 stars · license n/a
apisix versus kubesphere is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. apisix is written mainly in Lua; kubesphere is written mainly in Go. The composite score is 96.2 for apisix and 69.1 for kubesphere.
apisix has 17,333 GitHub stars to kubesphere's 17,080, a gap of 253 (1.01×). Forks are 3,004 for apisix and 2,752 for kubesphere. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 99.
Push history: apisix was last pushed on 13 November 2026 (4 days ago), and kubesphere was last pushed on 15 July 2026 (125 days ago). Open issues stand at 230 for apisix (0.013 per star) and 350 for kubesphere (0.020 per star). Issue-health scores are 84 and 70; activity scores are 92 and 36.
apisix 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 apisix and 30 for kubesphere. This is a procurement signal, not legal advice.
Only apisix is marked self-hostable here (17,333 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: apisix is open source, kubesphere is unpriced in this catalog.
apisix 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 adoption at 0 points (100 vs 100).
apisix finishes ahead at 96.2 against kubesphere at 69.1, a 27.1 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 | apisix | kubesphere |
|---|---|---|
| GitHub stars | 17,333 | 17,080 |
| Forks | 3,004 | 2,752 |
| Open issues | 230 | 350 |
| Adoption | 100 | 100 |
| Activity | 92 | 36 |
| Community | 100 | 99 |
| Issue health | 84 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 96.2 | 69.1 |
The Cloud-Native API Gateway and AI Gateway
The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
apisix has more GitHub stars: 17,333 versus 17,080 for kubesphere. The gap is 253 stars.
apisix was pushed more recently: 13 November 2026 versus 15 July 2026 for kubesphere. That is 121 days apart.
Only apisix is marked self-hostable. kubesphere is not.
apisix 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.
apisix scores 96.2 and kubesphere scores 69.1. This page calls that a decisive lead for apisix.