Skip to content
DevUtils Online

DevOps

dokploy vs kestra

kestra leads by 7.3 · clear

A

dokploy

88.4

38,560 stars · license n/a

B · leads

kestra

95.7

30,249 stars · Apache-2.0

dokploy versus kestra is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dokploy is written mainly in TypeScript; kestra is written mainly in Java. The composite score is 88.4 for dokploy and 95.7 for kestra.

dokploy has 38,560 GitHub stars to kestra's 30,249, a gap of 8,311 (1.27×). Forks are 3,180 for dokploy and 3,538 for kestra. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 99 versus 100.

Push history: dokploy 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 833 for dokploy (0.022 per star) and 651 for kestra (0.022 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.

dokploy is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. License scores in this pair are 30 for dokploy and 96 for kestra. This is a procurement signal, not legal advice.

In DevOps, both dokploy (38,560 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: dokploy is unpriced in this catalog, kestra is open source.

The lead is split. dokploy is furthest ahead on adoption (100 to 98), while kestra is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

kestra finishes ahead at 95.7 against dokploy at 88.4, a 7.3 point clear 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.

dokploy versus kestra metrics
Signal dokploy kestra
GitHub stars 38,560 30,249
Forks 3,180 3,538
Open issues 833 651
Adoption 100 98
Activity 100 100
Community 99 100
Issue health 70 70
License 30 96
Self-hosting 100 100
Composite 88.4 95.7

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, dokploy or kestra?

dokploy has more GitHub stars: 38,560 versus 30,249 for kestra. The gap is 8,311 stars.

Which was updated more recently, dokploy or kestra?

Both were last pushed on 17 November 2026.

Can I self-host both dokploy and kestra?

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

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

dokploy is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.

Who wins the dokploy vs kestra score?

kestra scores 95.7 and dokploy scores 88.4. This page calls that a clear lead for kestra.

Related comparisons