A · leads
dokploy
88.6
38,560 stars · license n/a
DevOps
dokploy leads by 22.1 · decisive
A · leads
88.6
38,560 stars · license n/a
B
66.5
17,080 stars · license n/a
dokploy versus kubesphere is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dokploy is written mainly in TypeScript; kubesphere is written mainly in Go. The composite score is 88.6 for dokploy and 66.5 for kubesphere.
dokploy has 38,560 GitHub stars to kubesphere's 17,080, a gap of 21,480 (2.26×). Forks are 3,180 for dokploy and 2,752 for kubesphere. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 98.
Push history: dokploy 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 833 for dokploy (0.022 per star) and 350 for kubesphere (0.020 per star). Issue-health scores are 70 and 70; activity scores are 100 and 36.
dokploy 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 dokploy and 30 for kubesphere. This is a procurement signal, not legal advice.
Only dokploy is marked self-hostable here (38,560 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: dokploy is unpriced in this catalog, kubesphere is unpriced in this catalog.
dokploy is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility. The widest gap is self-hosting at 65 points (100 vs 35), and the tightest is license flexibility at 0 points (30 vs 30).
dokploy finishes ahead at 88.6 against kubesphere at 66.5, a 22.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 | dokploy | kubesphere |
|---|---|---|
| GitHub stars | 38,560 | 17,080 |
| Forks | 3,180 | 2,752 |
| Open issues | 833 | 350 |
| Adoption | 100 | 92 |
| Activity | 100 | 36 |
| Community | 100 | 98 |
| Issue health | 70 | 70 |
| License | 30 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 88.6 | 66.5 |
Open Source Alternative to Vercel, Netlify and Heroku.
The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
dokploy has more GitHub stars: 38,560 versus 17,080 for kubesphere. The gap is 21,480 stars.
dokploy was pushed more recently: 17 November 2026 versus 15 July 2026 for kubesphere. That is 125 days apart.
Only dokploy is marked self-hostable. kubesphere is not.
dokploy 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.
dokploy scores 88.6 and kubesphere scores 66.5. This page calls that a decisive lead for dokploy.