Turkey (Turkish)
Germany (German)
Worldwide (English)
Minimum CPU recommendation in Coolify documentation.
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
This updates the existing `coolify-vps-kurulumu` URL. The goal is not merely to run an installer, but to design the server Coolify manages over SSH together with DNS, firewall, persistent data and recovery.
Do not treat the Coolify panel and deployed applications as the same trust boundary. Compromise of the panel can threaten SSH access to connected servers; protect management access separately.
Coolify officially lists a baseline around 2 CPU cores, 2 GB RAM and 30 GB free space; production capacity must also include application and database workloads. Coolify manages servers over SSH and deploys with Docker.
Coolify officially lists a baseline around 2 CPU cores, 2 GB RAM and 30 GB free space; production capacity must also include application and database workloads. Coolify manages servers over SSH and deploys with Docker.
Install Coolify on a clean Ubuntu VPS with a production mindset: SSH, resource sizing, Docker, wildcard domain, firewall, first deploy, backups and updates.
Minimum CPU recommendation in Coolify documentation.
Baseline for the platform; app/database usage is additional.
Monitor image, build-cache and log growth separately.
Coolify manages remote servers over SSH.
Builds can spike CPU/RAM while databases and persistent services consume resources continuously. Do not confuse minimums with production sizing.
| Profile | Starting point | Note |
|---|---|---|
| Panel + 1 small app | 2 vCPU / 4 GB | Watch build spikes |
| 3-5 apps + DB | 4 vCPU / 8 GB | Account for DB/cache |
| Heavy CI/deploy | 8+ vCPU / 16+ GB | Builder can be separate |
Checking hostname, DNS records, time synchronization and disk/inode state before installation prevents many later SSL/build failures.
hostnamectltimedatectl statusdf -hdf -igetent hosts panel.example.comcurl -4 ifconfig.mePrefer key-only authentication, source restrictions or VPN and a controlled admin identity rather than broad public root SSH. Grant only the management privileges Coolify needs.
sshd -T | grep -E "passwordauthentication|permitrootlogin|pubkeyauthentication"ss -lntp | grep :22ufw status verboseA responding web panel is not enough; Docker daemon, container health and restart policies must also be healthy.
docker versiondocker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"docker system dfsystemctl status docker --no-pagerWildcard DNS is useful for preview/temporary domains; explicit per-application DNS is often easier to troubleshoot for production domains.
Before adding database migrations or persistent volumes, validate Git webhook, build, health check, domain and rollback with a simple stateless app.
Protect Coolify configuration, but also give PostgreSQL/MySQL data, object storage and application volumes their own RPO/RTO policy.
| Asset | Backup method |
|---|---|
| Coolify platform | Platform backup/export |
| Database | Logical dump + PITR/physical as needed |
| Volume | Snapshot/file backup |
| Secrets | Separate secret escrow |
Plan CPU, RAM and NVMe for the Coolify control plane, application builds and databases together on an Eka Sunucu VPS.
Primary documentation and technical references used by this guide.
Continue with related infrastructure and implementation guides.
Coolify VPS
It is an official baseline, not a universal production target. Builds, databases and services require additional memory.
Yes. It uses Docker for application and service deployment. Monitor Docker health and disk usage on the host too.
Yes. DNS/proxy mode, origin reachability and SSL/TLS mode must be aligned. A separate guide covers that workflow.
Prefer restricting management access with VPN, allow lists or SSO because the panel holds powerful authority over connected servers.