A
encore
88.3
12,720 stars · MPL-2.0
DevOps
kestra leads by 8.2 · clear
A
88.3
12,720 stars · MPL-2.0
B · leads
96.5
30,249 stars · Apache-2.0
encore versus kestra is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. encore is written mainly in Go; kestra is written mainly in Java. The composite score is 88.3 for encore and 96.5 for kestra.
kestra has 30,249 GitHub stars to encore's 12,720, a gap of 17,529 (2.38×). Forks are 660 for encore and 3,538 for kestra. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 80 versus 100.
Push history: encore was last pushed on 13 November 2026 (4 days ago), and kestra was last pushed on 17 November 2026 (0 days ago). Open issues stand at 154 for encore (0.012 per star) and 651 for kestra (0.022 per star). Issue-health scores are 84 and 70; activity scores are 92 and 100.
encore 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. 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 78 for encore and 96 for kestra. This is a procurement signal, not legal advice.
In DevOps, both encore (12,720 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: encore is open source, kestra is open source.
The lead is split. encore is furthest ahead on issue health (84 to 70), while kestra is furthest ahead on fork community (100 to 80). Choose the dimension a rollout cannot compromise on.
kestra finishes ahead at 96.5 against encore at 88.3, a 8.2 point clear 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 | encore | kestra |
|---|---|---|
| GitHub stars | 12,720 | 30,249 |
| Forks | 660 | 3,538 |
| Open issues | 154 | 651 |
| Adoption | 92 | 100 |
| Activity | 92 | 100 |
| Community | 80 | 100 |
| Issue health | 84 | 70 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.3 | 96.5 |
Infrastructure orchestration from local to your 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 12,720 for encore. The gap is 17,529 stars.
kestra was pushed more recently: 17 November 2026 versus 13 November 2026 for encore. That is 4 days apart.
Yes. This catalog marks both encore and kestra as self-hostable. Confirm each project's deploy docs before you plan a migration.
encore 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. 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 encore scores 88.3. This page calls that a clear lead for kestra.