Skip to content
DevUtils Online

DevOps

kestra vs wtf

kestra leads by 5.0 · narrow

A · leads

kestra

96.5

30,249 stars · Apache-2.0

B

wtf

91.5

17,154 stars · MPL-2.0

kestra versus wtf 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; wtf is written mainly in Go. The composite score is 96.5 for kestra and 91.5 for wtf.

kestra has 30,249 GitHub stars to wtf's 17,154, a gap of 13,095 (1.76×). Forks are 3,538 for kestra and 866 for wtf. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 83.

Push history: kestra was last pushed on 17 November 2026 (0 days ago), and wtf was last pushed on 14 November 2026 (3 days ago). Open issues stand at 651 for kestra (0.022 per star) and 107 for wtf (0.006 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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for kestra and 78 for wtf. This is a procurement signal, not legal advice.

In DevOps, both kestra (30,249 stars) and wtf (17,154 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, wtf is open source.

The lead is split. kestra is furthest ahead on license flexibility (96 to 78), while wtf is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.

kestra finishes ahead at 96.5 against wtf at 91.5, a 5.0 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

kestra versus wtf metrics
Signal kestra wtf
GitHub stars 30,249 17,154
Forks 3,538 866
Open issues 651 107
Adoption 100 94
Activity 100 100
Community 100 83
Issue health 70 84
License 96 78
Self-hosting 100 100
Composite 96.5 91.5

kestra

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, kestra or wtf?

kestra has more GitHub stars: 30,249 versus 17,154 for wtf. The gap is 13,095 stars.

Which was updated more recently, kestra or wtf?

kestra was pushed more recently: 17 November 2026 versus 14 November 2026 for wtf. That is 3 days apart.

Can I self-host both kestra and wtf?

Yes. This catalog marks both kestra and wtf as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, kestra or wtf?

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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the kestra vs wtf score?

kestra scores 96.5 and wtf scores 91.5. This page calls that a narrow lead for kestra.

Related comparisons