A
dagger
93.7
16,623 stars · Apache-2.0
DevOps
kestra leads by 2.8 · narrow
A
93.7
16,623 stars · Apache-2.0
B · leads
96.5
30,249 stars · Apache-2.0
dagger versus kestra is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dagger is written mainly in Go; kestra is written mainly in Java. The composite score is 93.7 for dagger and 96.5 for kestra.
kestra has 30,249 GitHub stars to dagger's 16,623, a gap of 13,626 (1.82×). Forks are 960 for dagger and 3,538 for kestra. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 84 versus 100.
Push history: dagger was last pushed on 17 November 2026 (0 days ago), and kestra was last pushed on 17 November 2026 (0 days ago). Open issues stand at 266 for dagger (0.016 per star) and 651 for kestra (0.022 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
Both dagger and kestra 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 dagger (16,623 stars) and kestra (30,249 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: dagger is open source, kestra is open source.
The lead is split. dagger is furthest ahead on issue health (84 to 70), while kestra is furthest ahead on fork community (100 to 84). Choose the dimension a rollout cannot compromise on.
kestra finishes ahead at 96.5 against dagger at 93.7, a 2.8 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 | dagger | kestra |
|---|---|---|
| GitHub stars | 16,623 | 30,249 |
| Forks | 960 | 3,538 |
| Open issues | 266 | 651 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 84 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.7 | 96.5 |
Automation engine to build, test and ship any codebase. Runs locally, in CI, or directly in the cloud
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.
kestra has more GitHub stars: 30,249 versus 16,623 for dagger. The gap is 13,626 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dagger and kestra as self-hostable. Confirm each project's deploy docs before you plan a migration.
dagger 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
kestra scores 96.5 and dagger scores 93.7. This page calls that a narrow lead for kestra.