A
awless
65.1
4,957 stars · Apache-2.0
DevOps
Coolify leads by 34.0 · decisive
A
65.1
4,957 stars · Apache-2.0
B · leads
99.1
66,171 stars · Apache-2.0
awless versus Coolify is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. awless is written mainly in Go; Coolify is written mainly in PHP. The composite score is 65.1 for awless and 99.1 for Coolify.
Coolify has 66,171 GitHub stars to awless's 4,957, a gap of 61,214 (13.35×). Forks are 257 for awless and 6,003 for Coolify. On the log scale used inside this pair, adoption is 77 versus 100, and the fork community is 64 versus 100.
Push history: awless was last pushed on 02 August 2022 (1568 days ago), and Coolify was last pushed on 17 November 2026 (0 days ago). Open issues stand at 120 for awless (0.024 per star) and 149 for Coolify (0.002 per star). Issue-health scores are 70 and 96; activity scores are 16 and 100.
Both awless and Coolify 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 awless (4,957 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: awless is open source, Coolify 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 84 points (16 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against awless at 65.1, a 34.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 | awless | Coolify |
|---|---|---|
| GitHub stars | 4,957 | 66,171 |
| Forks | 257 | 6,003 |
| Open issues | 120 | 149 |
| Adoption | 77 | 100 |
| Activity | 16 | 100 |
| Community | 64 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 65.1 | 99.1 |
A Mighty CLI for AWS
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
Coolify has more GitHub stars: 66,171 versus 4,957 for awless. The gap is 61,214 stars.
Coolify was pushed more recently: 17 November 2026 versus 02 August 2022 for awless. That is 1568 days apart.
Yes. This catalog marks both awless and Coolify as self-hostable. Confirm each project's deploy docs before you plan a migration.
awless 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. 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.
Coolify scores 99.1 and awless scores 65.1. This page calls that a decisive lead for Coolify.