A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 28.0 · decisive
A · leads
99.1
66,171 stars · Apache-2.0
B
71.1
5,333 stars · Apache-2.0
Coolify versus ThreatMapper 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; ThreatMapper is written mainly in TypeScript. The composite score is 99.1 for Coolify and 71.1 for ThreatMapper.
Coolify has 66,171 GitHub stars to ThreatMapper's 5,333, a gap of 60,838 (12.41×). Forks are 6,003 for Coolify and 631 for ThreatMapper. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 74.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and ThreatMapper was last pushed on 01 June 2026 (169 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 144 for ThreatMapper (0.027 per star). Issue-health scores are 96 and 70; activity scores are 100 and 36.
Both Coolify and ThreatMapper 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 ThreatMapper (5,333 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, ThreatMapper is open source.
Coolify is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 64 points (100 vs 36), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against ThreatMapper at 71.1, a 28.0 point decisive 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 | ThreatMapper |
|---|---|---|
| GitHub stars | 66,171 | 5,333 |
| Forks | 6,003 | 631 |
| Open issues | 149 | 144 |
| Adoption | 100 | 77 |
| Activity | 100 | 36 |
| Community | 100 | 74 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 71.1 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Open Source Cloud Native Application Protection Platform (CNAPP)
Coolify has more GitHub stars: 66,171 versus 5,333 for ThreatMapper. The gap is 60,838 stars.
Coolify was pushed more recently: 17 November 2026 versus 01 June 2026 for ThreatMapper. That is 169 days apart.
Yes. This catalog marks both Coolify and ThreatMapper 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. ThreatMapper 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 ThreatMapper scores 71.1. This page calls that a decisive lead for Coolify.