Must have
Hard prerequisites
- Coolify lists 2 CPU cores, 2 GB RAM, and 10 GB free disk as its minimum self-hosted hardware starting point.
Application hosting
Hosting Coolify
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.
- Min vCPU
- 2
- Min memory
- Depends on workload
- Min storage
- Depends on workload
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
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.
Official instructions -
Choose automated or manual setup
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.
Official instructions -
Separate deployment capacity where needed
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.
Official instructions
Security
Before you go public
- Create the administrator account as soon as installation completes and keep generated installation secrets backed up securely.
- Review required firewall ports before installation; do not expose management access more widely than necessary.
- Treat the Coolify host and any connected deployment server as privileged infrastructure.
Cost
Beyond the server price
- Coolify software is self-hosted; budget the control-plane server and separate deployment capacity if required.
- Include Docker images, persistent data, backups, traffic, and any managed services in the total operating cost.
Matching plans
Plans with published evidence
DigitalOcean
CPU-Optimized Regular Droplet · 2 vCPU / 4 GiB
2vCPU
4 GiBRAM
25 GiBStorage
4 TBTransfer
Compatibility unclear from published plan data
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.
DigitalOcean
General Purpose Droplet · 2 Dedicated vCPU / 8 GB
2vCPU
8 GBRAM
25 GBStorage
4 TBTransfer
Compatibility unclear from published plan data
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.
Compatibility unclear from published plan data
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.
Compatibility unclear from published plan data
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.
Compatibility unclear from published plan data
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.
Compatibility unclear from published plan data
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.
Compatibility unclear from published plan data
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.
Compatibility unclear from published plan data
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.
Hetzner Cloud
Hetzner Cloud CCX53 (Germany and Finland)
32vCPU
128 GBRAM
600 GBStorage
50 TBTransfer
Compatibility unclear from published plan data
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.
Hetzner Cloud
Hetzner Cloud CCX63 (Germany and Finland)
48vCPU
192 GBRAM
960 GBStorage
60 TBTransfer
Compatibility unclear from published plan data
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.
Compatibility unclear from published plan data
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.
Compatibility unclear from published plan data
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.
Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.