A · leads
kestra
96.5
30,249 stars · Apache-2.0
DevOps
kestra leads by 5.6 · narrow
A · leads
96.5
30,249 stars · Apache-2.0
B
90.9
23,030 stars · Apache-2.0
kestra versus witr 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; witr is written mainly in Go. The composite score is 96.5 for kestra and 90.9 for witr.
kestra has 30,249 GitHub stars to witr's 23,030, a gap of 7,219 (1.31×). Forks are 3,538 for kestra and 811 for witr. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 82.
Push history: kestra was last pushed on 17 November 2026 (0 days ago), and witr was last pushed on 23 October 2026 (25 days ago). Open issues stand at 651 for kestra (0.022 per star) and 8 for witr (0.000 per star). Issue-health scores are 70 and 96; activity scores are 100 and 78.
Both kestra and witr are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both kestra (30,249 stars) and witr (23,030 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, witr is open source.
The lead is split. kestra is furthest ahead on recent activity (100 to 78), while witr is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
kestra finishes ahead at 96.5 against witr at 90.9, a 5.6 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 | witr |
|---|---|---|
| GitHub stars | 30,249 | 23,030 |
| Forks | 3,538 | 811 |
| Open issues | 651 | 8 |
| Adoption | 100 | 97 |
| Activity | 100 | 78 |
| Community | 100 | 82 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 90.9 |
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.
Why is this running? Trace any process, port, container, or file back to what started it - CLI + TUI.
kestra has more GitHub stars: 30,249 versus 23,030 for witr. The gap is 7,219 stars.
kestra was pushed more recently: 17 November 2026 versus 23 October 2026 for witr. That is 25 days apart.
Yes. This catalog marks both kestra and witr 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. witr 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
kestra scores 96.5 and witr scores 90.9. This page calls that a narrow lead for kestra.