Multiple servers
Run your app on multiple servers without Kubernetes.
You or your coding agent add the next server with one command. No quorum to keep alive, no control plane to babysit, no Kubernetes.
visitors → any online server
Caddy · https
- web
- web
Caddy · https
- web
Caddy · https
- web
- postgres+ volume
private WireGuard network between servers
web: 4 of 4 replicas serving. Any online server takes a request and hands it to one of them.
postgres: one replica, on server-3, where its volume is.
Add replicas, then take a server offline and see what keeps serving.
No load balancer to rent
Caddy runs on every server and hands each request to a healthy replica, on any server.
No server is the boss
No leader, no three-server minimum, no etcd. Every server is a peer, so losing one takes nothing else with it.
Services find each other
Your app reaches postgres.internal on any server, over the private WireGuard network.
Add a server with one command.
Paste it on any Linux server you rent, at any provider, or let your agent run ployz server add. The server joins your private WireGuard network, ready for builds, services and web traffic.

Up to 50 replicas.
Set Replicas and deploy. Each server gets one replica before any server gets a second.

Compared with the platforms.
| What you need | Heroku, Render, Railway, Fly.io | Ployz on your server |
|---|---|---|
| Cost per copy | Billed per dyno, instance or Machine | Nothing. Replicas share your servers |
| Three copies of a 512 MB app | Heroku $75, Render $21, Fly.io about $11 | Three Hetzner CX23 servers, about $21. Ployz is free |
| Where copies run | One region on Heroku and Render | Any server you add, at any provider |
| Copies with a disk | One copy on Render, Railway and Fly.io | One replica, on the volume's server |
| Scaling | Autoscaling on Heroku Performance dynos and Render Pro | You pick the servers and the replicas |
More numbers in Hosted platform pricing compared.
Good to know.
- When a server goes down, replicas on your other servers keep serving.
- A database lives on one server, with a restore point. Move it to another server with seconds of downtime.
- Draining a server waits for a person, whoever asked for it.
- Replicas spread on deploy, so deploy after you add a server.
- Metrics for every server and service, and searchable logs, in the same dashboard.
Questions
Can Docker Compose run across multiple servers?
No. Compose runs a stack on one Docker host. Spreading containers over servers needs Docker Swarm, Kubernetes, Nomad, or a tool like Ployz that places replicas and routes between servers.
Do I need Kubernetes to scale an app across servers?
No. Ployz runs plain Docker on each server, a WireGuard network between them and Caddy for https. Placement happens when you deploy, with no scheduler running in the background.
What happens when a server goes down?
Replicas on your other servers keep serving. Services that ran only there stay down until you redeploy them with the CLI.
Can I mix providers, like Hetzner and DigitalOcean?
Yes. Any Linux server with systemd, amd64 or arm64, can join, as long as your servers reach each other on UDP port 51820.
Can my coding agent add and remove servers?
It can add one with ployz server add. Draining a server waits for a person, and an agent connected through ployz mcp can't answer that approval.
What does it cost?
Nothing, on any number of servers, with unlimited replicas, projects and custom domains. You pay your provider for the servers.
Your servers. The whole platform. Free on your own servers.
Deploy your appFacts checked 2026-10-18.