Coolify is a self-hosted platform for deploying and managing applications, databases, and services on Linux servers. Its documented paths include repository-based builds and container images. Coolify recommends a fresh server for automated setup because installation can change Docker and networking configuration.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.
Recommended
Documented guidance
No further general recommendations are published for this version.
Published starting requirements
The source states RAM and disk in GB, while these comparison tiles use GiB, so the numeric fields remain unset. Running applications, databases, Docker images, and backups need additional capacity.
We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.
Deploy with
Supported paths
Automated installation on a Linux server
Manual installation for existing Docker, non-root, or custom setups
Deploy applications from Git repositories or container images
The host must provide
Runtime
Operating system
Linux; the guide lists Ubuntu and Debian among supported distributions
Architecture
amd64 or arm64; 64-bit ARM is required for Raspberry Pi OS
Container runtime
Docker Engine; follow the current install path for the target system
Access
SSH and root or sudo access for the automated installation
Storage
Persistent data
The 10 GB free-disk figure is an installation minimum, not an application-data budget. Docker images, persistent volumes, repository clones, and backups consume more; the Coolify documentation recommends planning additional space.
Step by step
Plan a Coolify installation
Choose a suitable host
Meet the stated minimum, check the supported Linux distribution, and account for the resources and disk needed by the workloads you will manage.
Use the automated path for a compatible clean host. Review the manual path when Docker already exists or the server needs custom networking and storage.
A self-hosted install can deploy onto its localhost, but application workloads then share resources with the Coolify control panel. Add a deployment server when that separation is needed.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.This prerequisite has no comparable published plan field.