A · leads
kestra
96.5
30,249 stars · Apache-2.0
DevOps
kestra leads by 7.4 · clear
A · leads
96.5
30,249 stars · Apache-2.0
B
89.1
14,330 stars · AGPL-3.0
kestra versus unleash 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; unleash is written mainly in TypeScript. The composite score is 96.5 for kestra and 89.1 for unleash.
kestra has 30,249 GitHub stars to unleash's 14,330, a gap of 15,919 (2.11×). Forks are 3,538 for kestra and 935 for unleash. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 84.
Push history: kestra was last pushed on 17 November 2026 (0 days ago), and unleash was last pushed on 17 November 2026 (0 days ago). Open issues stand at 651 for kestra (0.022 per star) and 48 for unleash (0.003 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
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. unleash is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for kestra and 52 for unleash. This is a procurement signal, not legal advice.
In DevOps, both kestra (30,249 stars) and unleash (14,330 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: kestra is open source, unleash is open source.
The lead is split. kestra is furthest ahead on license flexibility (96 to 52), while unleash is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
kestra finishes ahead at 96.5 against unleash at 89.1, a 7.4 point clear 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 | unleash |
|---|---|---|
| GitHub stars | 30,249 | 14,330 |
| Forks | 3,538 | 935 |
| Open issues | 651 | 48 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 84 |
| Issue health | 70 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 89.1 |
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.
Open-source feature management platform
kestra has more GitHub stars: 30,249 versus 14,330 for unleash. The gap is 15,919 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both kestra and unleash as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. unleash is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
kestra scores 96.5 and unleash scores 89.1. This page calls that a clear lead for kestra.