A
apisix
94.0
17,333 stars · Apache-2.0
DevOps
kestra leads by 2.5 · narrow
A
94.0
17,333 stars · Apache-2.0
B · leads
96.5
30,249 stars · Apache-2.0
apisix versus kestra is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. apisix is written mainly in Lua; kestra is written mainly in Java. The composite score is 94.0 for apisix and 96.5 for kestra.
kestra has 30,249 GitHub stars to apisix's 17,333, a gap of 12,916 (1.75×). Forks are 3,004 for apisix and 3,538 for kestra. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 98 versus 100.
Push history: apisix 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 230 for apisix (0.013 per star) and 651 for kestra (0.022 per star). Issue-health scores are 84 and 70; activity scores are 92 and 100.
Both apisix and kestra 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 apisix (17,333 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: apisix is open source, kestra is open source.
The lead is split. apisix is furthest ahead on issue health (84 to 70), while kestra is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
kestra finishes ahead at 96.5 against apisix at 94.0, a 2.5 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 | apisix | kestra |
|---|---|---|
| GitHub stars | 17,333 | 30,249 |
| Forks | 3,004 | 3,538 |
| Open issues | 230 | 651 |
| Adoption | 95 | 100 |
| Activity | 92 | 100 |
| Community | 98 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.0 | 96.5 |
The Cloud-Native API Gateway and AI Gateway
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 17,333 for apisix. The gap is 12,916 stars.
kestra was pushed more recently: 17 November 2026 versus 13 November 2026 for apisix. That is 4 days apart.
Yes. This catalog marks both apisix and kestra as self-hostable. Confirm each project's deploy docs before you plan a migration.
apisix 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. 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 apisix scores 94.0. This page calls that a narrow lead for kestra.