A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 5.8 · narrow
A · leads
99.1
66,171 stars · Apache-2.0
B
93.3
30,249 stars · Apache-2.0
Coolify versus kestra is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Coolify is written mainly in PHP; kestra is written mainly in Java. The composite score is 99.1 for Coolify and 93.3 for kestra.
Coolify has 66,171 GitHub stars to kestra's 30,249, a gap of 35,922 (2.19×). Forks are 6,003 for Coolify and 3,538 for kestra. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 94.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and kestra was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 651 for kestra (0.022 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
Both Coolify 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 Coolify (66,171 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: Coolify is open source, kestra is open source.
Coolify 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 26 points (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against kestra at 93.3, a 5.8 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 | Coolify | kestra |
|---|---|---|
| GitHub stars | 66,171 | 30,249 |
| Forks | 6,003 | 3,538 |
| Open issues | 149 | 651 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 94 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 93.3 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
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.
Coolify has more GitHub stars: 66,171 versus 30,249 for kestra. The gap is 35,922 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and kestra as self-hostable. Confirm each project's deploy docs before you plan a migration.
Coolify 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.
Coolify scores 99.1 and kestra scores 93.3. This page calls that a narrow lead for Coolify.