Skip to content
DevUtils Online

DevOps

bunkerweb vs Coolify

Coolify leads by 15.4 · decisive

B · leads

Coolify

99.1

66,171 stars · Apache-2.0

bunkerweb versus Coolify is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bunkerweb is written mainly in Python; Coolify is written mainly in PHP. The composite score is 83.7 for bunkerweb and 99.1 for Coolify.

Coolify has 66,171 GitHub stars to bunkerweb's 11,277, a gap of 54,894 (5.87×). Forks are 674 for bunkerweb and 6,003 for Coolify. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 75 versus 100.

Push history: bunkerweb was last pushed on 17 November 2026 (0 days ago), and Coolify was last pushed on 17 November 2026 (0 days ago). Open issues stand at 183 for bunkerweb (0.016 per star) and 149 for Coolify (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.

bunkerweb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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. License scores in this pair are 52 for bunkerweb and 96 for Coolify. This is a procurement signal, not legal advice.

In DevOps, both bunkerweb (11,277 stars) and Coolify (66,171 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: bunkerweb is open source, Coolify is open source.

Coolify is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

Coolify finishes ahead at 99.1 against bunkerweb at 83.7, a 15.4 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

bunkerweb versus Coolify metrics
Signal bunkerweb Coolify
GitHub stars 11,277 66,171
Forks 674 6,003
Open issues 183 149
Adoption 84 100
Activity 100 100
Community 75 100
Issue health 84 96
License 52 96
Self-hosting 100 100
Composite 83.7 99.1

Coolify

Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, bunkerweb or Coolify?

Coolify has more GitHub stars: 66,171 versus 11,277 for bunkerweb. The gap is 54,894 stars.

Which was updated more recently, bunkerweb or Coolify?

Both were last pushed on 17 November 2026.

Can I self-host both bunkerweb and Coolify?

Yes. This catalog marks both bunkerweb and Coolify as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, bunkerweb or Coolify?

bunkerweb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the bunkerweb vs Coolify score?

Coolify scores 99.1 and bunkerweb scores 83.7. This page calls that a decisive lead for Coolify.

Related comparisons