A · leads
kestra
94.6
30,249 stars · Apache-2.0
DevOps
kestra leads by 11.2 · clear
A · leads
94.6
30,249 stars · Apache-2.0
B
83.4
45,789 stars · license n/a
kestra versus sentry 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; sentry is written mainly in Python. The composite score is 94.6 for kestra and 83.4 for sentry.
sentry has 45,789 GitHub stars to kestra's 30,249, a gap of 15,540 (1.51×). Forks are 3,538 for kestra and 4,980 for sentry. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 96 versus 100.
Push history: kestra was last pushed on 17 November 2026 (0 days ago), and sentry was last pushed on 17 November 2026 (0 days ago). Open issues stand at 651 for kestra (0.022 per star) and 2,213 for sentry (0.048 per star). Issue-health scores are 70 and 70; 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. sentry 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. License scores in this pair are 96 for kestra and 30 for sentry. This is a procurement signal, not legal advice.
Only kestra is marked self-hostable here (30,249 stars, deploy score 100). sentry is not (45,789 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: kestra is open source, sentry is unpriced in this catalog.
The lead is split. kestra is furthest ahead on license flexibility (96 to 30), while sentry is furthest ahead on fork community (100 to 96). Choose the dimension a rollout cannot compromise on.
kestra finishes ahead at 94.6 against sentry at 83.4, a 11.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 | kestra | sentry |
|---|---|---|
| GitHub stars | 30,249 | 45,789 |
| Forks | 3,538 | 4,980 |
| Open issues | 651 | 2,213 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 94.6 | 83.4 |
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.
Developer-first error tracking and performance monitoring
sentry has more GitHub stars: 45,789 versus 30,249 for kestra. The gap is 15,540 stars.
Both were last pushed on 17 November 2026.
Only kestra is marked self-hostable. sentry is not.
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. sentry 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
kestra scores 94.6 and sentry scores 83.4. This page calls that a clear lead for kestra.