A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 12.0 · clear
A · leads
99.1
66,171 stars · Apache-2.0
B
87.1
12,143 stars · Apache-2.0
Coolify versus kubeshark 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; kubeshark is written mainly in Go. The composite score is 99.1 for Coolify and 87.1 for kubeshark.
Coolify has 66,171 GitHub stars to kubeshark's 12,143, a gap of 54,028 (5.45×). Forks are 6,003 for Coolify and 557 for kubeshark. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 73.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and kubeshark was last pushed on 10 November 2026 (7 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 145 for kubeshark (0.012 per star). Issue-health scores are 96 and 84; activity scores are 100 and 92.
Both Coolify and kubeshark 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 kubeshark (12,143 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, kubeshark is open source.
Coolify is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 27 points (100 vs 73), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against kubeshark at 87.1, a 12.0 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 | Coolify | kubeshark |
|---|---|---|
| GitHub stars | 66,171 | 12,143 |
| Forks | 6,003 | 557 |
| Open issues | 149 | 145 |
| Adoption | 100 | 85 |
| Activity | 100 | 92 |
| Community | 100 | 73 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 87.1 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
eBPF-powered network observability for Kubernetes. Indexes L4/L7 traffic with full K8s context, decrypts TLS without keys. Queryable by AI agents via MCP and humans via dashboard.
Coolify has more GitHub stars: 66,171 versus 12,143 for kubeshark. The gap is 54,028 stars.
Coolify was pushed more recently: 17 November 2026 versus 10 November 2026 for kubeshark. That is 7 days apart.
Yes. This catalog marks both Coolify and kubeshark 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. kubeshark 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 kubeshark scores 87.1. This page calls that a clear lead for Coolify.