A · leads
kestra
96.5
30,249 stars · Apache-2.0
DevOps
kestra leads by 5.9 · narrow
A · leads
96.5
30,249 stars · Apache-2.0
B
90.6
14,420 stars · MIT
kestra versus semaphore 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; semaphore is written mainly in Go. The composite score is 96.5 for kestra and 90.6 for semaphore.
kestra has 30,249 GitHub stars to semaphore's 14,420, a gap of 15,829 (2.10×). Forks are 3,538 for kestra and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 88.
Push history: kestra was last pushed on 17 November 2026 (0 days ago), and semaphore was last pushed on 17 November 2026 (0 days ago). Open issues stand at 651 for kestra (0.022 per star) and 1,075 for semaphore (0.075 per star). Issue-health scores are 70 and 52; 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. semaphore is listed as MIT, 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 96 for kestra and 96 for semaphore. This is a procurement signal, not legal advice.
In DevOps, both kestra (30,249 stars) and semaphore (14,420 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, semaphore is open source.
kestra is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 18 points (70 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
kestra finishes ahead at 96.5 against semaphore at 90.6, a 5.9 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 | kestra | semaphore |
|---|---|---|
| GitHub stars | 30,249 | 14,420 |
| Forks | 3,538 | 1,353 |
| Open issues | 651 | 1,075 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 90.6 |
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.
Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools.
kestra has more GitHub stars: 30,249 versus 14,420 for semaphore. The gap is 15,829 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both kestra and semaphore as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. semaphore is listed as MIT, 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 semaphore scores 90.6. This page calls that a narrow lead for kestra.