Skip to content
DevUtils Online

DevOps

kestra vs opensre

kestra leads by 1.3 · narrow

A · leads

kestra

96.5

30,249 stars · Apache-2.0

B

opensre

95.2

12,838 stars · Apache-2.0

kestra versus opensre 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; opensre is written mainly in Python. The composite score is 96.5 for kestra and 95.2 for opensre.

kestra has 30,249 GitHub stars to opensre's 12,838, a gap of 17,411 (2.36×). Forks are 3,538 for kestra and 1,884 for opensre. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 92.

Push history: kestra was last pushed on 17 November 2026 (0 days ago), and opensre was last pushed on 17 November 2026 (0 days ago). Open issues stand at 651 for kestra (0.022 per star) and 11 for opensre (0.001 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.

Both kestra and opensre 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 opensre (12,838 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, opensre is open source.

The lead is split. kestra is furthest ahead on adoption (100 to 92), while opensre is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.

kestra finishes ahead at 96.5 against opensre at 95.2, a 1.3 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 opensre metrics
Signal kestra opensre
GitHub stars 30,249 12,838
Forks 3,538 1,884
Open issues 651 11
Adoption 100 92
Activity 100 100
Community 100 92
Issue health 70 96
License 96 96
Self-hosting 100 100
Composite 96.5 95.2

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 opensre?

kestra has more GitHub stars: 30,249 versus 12,838 for opensre. The gap is 17,411 stars.

Which was updated more recently, kestra or opensre?

Both were last pushed on 17 November 2026.

Can I self-host both kestra and opensre?

Yes. This catalog marks both kestra and opensre 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 opensre?

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. opensre 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 kestra vs opensre score?

kestra scores 96.5 and opensre scores 95.2. This page calls that a narrow lead for kestra.

Related comparisons