Coolify
| License | FOSS problems | Maintenance | SSO | Users | Tested |
|---|---|---|---|---|---|
| Apache-2.0Permissive license. Like MIT, but each contributor grants users a patent licence covering their contribution, preventing later suits. | — | Active | ✅ | Unlimited | ✅ |
Description
Coolify is an open source platform for managing self-hosted services — a UI on top of Docker and Docker Compose that lets services be deployed, configured, and monitored without touching the command line for every change. Unlike Ansible, it's a running platform, not a CLI you invoke and walk away from — it stays up, holding the dashboard, the reverse proxy, and everything else that keeps every deployed service reachable.
Features
- UI & accounts — a single dashboard for all running services, their status, logs, environment variables, and domains. Multiple user accounts with role-based access, so team members get access without server credentials.
- Configuration management — environment variables edited through the UI, with team-level shared variables referenced across services so common values like SMTP credentials don't need duplicating.
- App deployment — pre-built templates for hundreds of common apps as Docker Compose definitions; picking a template, filling in a domain and a few variables, and deploying. Also deploys webapps and static sites directly from a git repository.
- Infrastructure management — reverse proxying via Traefik with automatic SSL via Let's Encrypt, Docker network management, terminal access to running containers, firewall-friendly port routing.
- Monitoring & backups — CPU, memory, and disk usage per container visible from the dashboard, plus scheduled database dumps with configurable retention and remote storage targets.
Usage patterns
- Single server — this project's actual usage: one Coolify instance managing everything running on one box.
- Multi-server / teams — servers can be assigned to teams, scoping access without giving everyone visibility into the whole platform; still the least mature part of Coolify (see Conclusion).
- Git-based deploys — for apps hosted as source rather than a pre-built template, deployed straight from a repository instead of picking from the template catalog.
The concrete install process and backup/restore steps live in Walkthrough → System → Coolify rather than here.
License and governance
Apache 2.0, genuinely open, no dual-licensing gate on core functionality. Maintained by Coollabs, a single company rather than a foundation — the same single-vendor shape flagged elsewhere in this catalog, though the permissive license means a future change wouldn't retroactively affect what's already released, the same protection (and the same limits of that protection) discussed on Terraform's and Pulumi's pages.
Conclusion
Why you would — solves the exact things that make self-hosting more than a couple of services tedious without it: one dashboard, template-based deploys, automatic SSL and routing, and built-in scheduled backups — real operational infrastructure, not just a deploy button, for one server or a handful.
Why you wouldn't — teams, RBAC, and multi-server features are the least mature part. On a single server, a team member with any access can still cause real damage, since fine-grained permission scoping isn't fully there yet.