Both are free. The second server is where they differ.
Coolify and Ployz both cost $0 on one server: you pay for the server and nothing else. From two, Coolify's docs tell you to put a load balancer in front, such as Hetzner's LB11 at $8.49 a month with its IPv4 address. Ployz stays free, and every server serves https itself. Move the slider to see both bills.
- Server cost (Hetzner CX23 + IPv4)
- $14.18
- Load balancer to rent with Coolify
- Hetzner LB11 with its IPv4, $8.49
- Coolify, self-hosted$23/mo
Dashboard runs on one of your servers (it asks for 2 GB of RAM). From two servers, a Hetzner LB11 to spread traffic, as Coolify's docs advise.
- Coolify Cloud$28/mo
$5 includes 2 servers, then $3 per server. Same load balancer from two servers.
- Your own servers + Ployz$14/mo
Ployz is free on any number of servers, custom domains included, with the dashboard hosted on Ployz Cloud. Every server serves https itself, so there's no load balancer to rent.
At two servers, self-hosted Coolify with that load balancer comes to $22.67 a month and Ployz to $14.18, so the gap is the load balancer, $8.49 a month. Coolify Cloud adds $5 a month for two servers and $3 for each extra one. If each app lives on one server and nothing needs spreading, Coolify skips the load balancer and both cost what the servers cost.
The amounts are small, so what happens when you add a server matters more than the bill.
Server prices are Hetzner's CX23 in Europe ($6.49 plus $0.60 IPv4). In the US, Netcup's Manassas datacenter or a DigitalOcean Droplet is the cheaper option; my first pick in Europe is Netcup's VPS 500 at €8.26 a month incl. VAT.
What changes when you move
- When a server goes down. Replicas on other servers keep serving, and you redeploy stateless services onto the others from the CLI.
- Monitoring. Ployz shows metrics for every service and server, with searchable logs next to your deploys.
- GitLab. Ployz deploys from GitHub, or from any Docker image.
If Compose files, templates or scheduled backups to S3 matter more than spreading traffic across servers, stay on Coolify.
Moving from Coolify
I'd put Ployz on a new server rather than next to Coolify, since both want ports 80 and 443. Keep Coolify serving while you move one app at a time, then switch DNS.
$ curl -fsSL https://ployz.sh | sh
Installs the ployz CLI on macOS or Linux.
$ ployz login
Signs in to Ployz Cloud in your browser.
$ ployz up --server root@your-server
Installs Ployz on the server, builds this directory and gives it an HTTPS address.
Or paste Read ployz.dev/agents.md and deploy this repo to my server. into your coding agent and it does the same.
Then recreate each container from your Coolify app or Compose file as its own service, add Postgres or Redis from the dashboard, copy your environment variables across, and restore a pg_dump from Coolify's database before you switch DNS. Scaling and multiple servers covers replicas and what happens when a server goes down.