A · leads
kestra
96.5
30,249 stars · Apache-2.0
DevOps
kestra leads by 2.9 · narrow
A · leads
96.5
30,249 stars · Apache-2.0
B
93.6
16,362 stars · MIT
kestra versus task 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; task is written mainly in Go. The composite score is 96.5 for kestra and 93.6 for task.
kestra has 30,249 GitHub stars to task's 16,362, a gap of 13,887 (1.85×). Forks are 3,538 for kestra and 945 for task. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 84.
Push history: kestra was last pushed on 17 November 2026 (0 days ago), and task was last pushed on 17 November 2026 (0 days ago). Open issues stand at 651 for kestra (0.022 per star) and 195 for task (0.012 per star). Issue-health scores are 70 and 84; 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. task is listed as MIT, 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. License scores in this pair are 96 for kestra and 96 for task. This is a procurement signal, not legal advice.
In DevOps, both kestra (30,249 stars) and task (16,362 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, task is open source.
The lead is split. kestra is furthest ahead on fork community (100 to 84), while task is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
kestra finishes ahead at 96.5 against task at 93.6, a 2.9 point narrow 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 | task |
|---|---|---|
| GitHub stars | 30,249 | 16,362 |
| Forks | 3,538 | 945 |
| Open issues | 651 | 195 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 84 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 93.6 |
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.
A fast, cross-platform build tool inspired by Make, designed for modern workflows.
kestra has more GitHub stars: 30,249 versus 16,362 for task. The gap is 13,887 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both kestra and task 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. task is listed as MIT, 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
kestra scores 96.5 and task scores 93.6. This page calls that a narrow lead for kestra.