coollabsio/coolify

Adopt only if you explicitly want an old, unmodified Coolify snapshot to build on. For most users, upstream is the better choice because this fork adds nothing and is far behind current fixes and features.

Prefer upstream unless you specifically need a frozen snapshot. This fork adds no visible product value and is too far behind to be a good adoption target for production use.

Choose this fork if white-label branding and custom email/template workflows matter more than staying close to upstream. Avoid it if you want the newest Coolify features and fixes with minimal maintenance overhead.

Treat this as a stale snapshot of Coolify, not a differentiated fork. Choose it only if you specifically need the older baseline; otherwise upstream is the better default.

Choose upstream unless you specifically need this fork's older custom workflow changes. The fork is too stale and too divergent for most adopters, especially if you value current features, security, and compatibility.

Choose this fork only if you want an almost-vanilla Coolify copy. If you want the latest fixes and service updates, upstream is the better default.

Choose this fork only if you specifically need a pinned historical Coolify snapshot. For most adopters, upstream is the better choice because this fork is far behind and adds no visible capabilities.

This fork does not appear to add anything over upstream and is far behind it, so most adopters should prefer upstream Coolify unless they specifically want an older baseline to customize.

Choose this fork only if you explicitly want an old, unmodified Coolify snapshot. For almost everyone else, upstream is the better choice because this fork adds no visible value and is far behind current development.