Skip to content
DevUtils Online

DevOps

Coolify vs oneuptime

Coolify leads by 29.8 · decisive

A · leads

Coolify

99.1

66,171 stars · Apache-2.0

B

oneuptime

69.3

7,826 stars · license n/a

Coolify versus oneuptime 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; oneuptime is written mainly in TypeScript. The composite score is 99.1 for Coolify and 69.3 for oneuptime.

Coolify has 66,171 GitHub stars to oneuptime's 7,826, a gap of 58,345 (8.46×). Forks are 6,003 for Coolify and 495 for oneuptime. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 71.

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

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. oneuptime is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for Coolify and 30 for oneuptime. This is a procurement signal, not legal advice.

Only Coolify is marked self-hostable here (66,171 stars, deploy score 100). oneuptime is not (7,826 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: Coolify is open source, oneuptime is unpriced in this catalog.

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

Coolify finishes ahead at 99.1 against oneuptime at 69.3, a 29.8 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.

Coolify versus oneuptime metrics
Signal Coolify oneuptime
GitHub stars 66,171 7,826
Forks 6,003 495
Open issues 149 1,124
Adoption 100 81
Activity 100 100
Community 100 71
Issue health 96 34
License 96 30
Self-hosting 100 35
Composite 99.1 69.3

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, Coolify or oneuptime?

Coolify has more GitHub stars: 66,171 versus 7,826 for oneuptime. The gap is 58,345 stars.

Which was updated more recently, Coolify or oneuptime?

Both were last pushed on 17 November 2026.

Can I self-host both Coolify and oneuptime?

Only Coolify is marked self-hostable. oneuptime is not.

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

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. oneuptime is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the Coolify vs oneuptime score?

Coolify scores 99.1 and oneuptime scores 69.3. This page calls that a decisive lead for Coolify.

Related comparisons