A · leads
kestra
96.5
30,249 stars · Apache-2.0
DevOps
kestra leads by 29.5 · decisive
A · leads
96.5
30,249 stars · Apache-2.0
B
67.0
17,080 stars · license n/a
kestra versus kubesphere is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. kestra is written mainly in Java; kubesphere is written mainly in Go. The composite score is 96.5 for kestra and 67.0 for kubesphere.
kestra has 30,249 GitHub stars to kubesphere's 17,080, a gap of 13,169 (1.77×). Forks are 3,538 for kestra and 2,752 for kubesphere. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 97.
Push history: kestra 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 651 for kestra (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.
kestra 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 kestra and 30 for kubesphere. This is a procurement signal, not legal advice.
Only kestra is marked self-hostable here (30,249 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: kestra is open source, kubesphere is unpriced in this catalog.
kestra is ahead on every scored dimension that is not level. Level dimensions: issue health. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is issue health at 0 points (70 vs 70).
kestra finishes ahead at 96.5 against kubesphere at 67.0, a 29.5 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 | kestra | kubesphere |
|---|---|---|
| GitHub stars | 30,249 | 17,080 |
| Forks | 3,538 | 2,752 |
| Open issues | 651 | 350 |
| Adoption | 100 | 94 |
| Activity | 100 | 36 |
| Community | 100 | 97 |
| Issue health | 70 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 96.5 | 67.0 |
Orchestrate everything, everywhere. The open-source control plane for workflows across data, infrastructure, business processes and AI agents. Declarative YAML, event-driven, any language, Git-versioned, scalable to millions of executions.
The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
kestra has more GitHub stars: 30,249 versus 17,080 for kubesphere. The gap is 13,169 stars.
kestra was pushed more recently: 17 November 2026 versus 15 July 2026 for kubesphere. That is 125 days apart.
Only kestra is marked self-hostable. kubesphere is not.
kestra 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.
kestra scores 96.5 and kubesphere scores 67.0. This page calls that a decisive lead for kestra.