Coolify, multi-server ready
If Coolify already deploys to several servers behind a load balancer, the prerequisite list is empty. The 20 to 30 minutes are the tokens, the preflight and one Rehearsal.
- Prerequisite work
- none
- Time to set up
- 20–30 min
- Adapter
- Snapshot today; native Coolify mode planned
- Fit
- 8/10
Prerequisites, time and fit are this case's row in the onboarding cases table. Hetscale's own setup is about 15 minutes in every case; the rest is work on your side.
Steps
- 01Check the seed’s conditions
All state external, TLS at the load balancer with the Coolify proxy set to “None” or an HTTP FQDN, and Coolify itself on a server outside the group. The new servers need no registry image and no Coolify server slot: they are copies of the seed.
- 02Connect read-only, answer “Coolify”, pick the seed
The 14-day Observe trial with a read-only Hetzner token; the day-0 report ranges the capacity and the cost. You pick one of the servers Coolify deploys to as the seed; the others behind the load balancer join the group protected, counted as capacity and never deleted. Hetscale asks for no Coolify token and calls no Coolify API.
- 03Rehearse, then go Live
When you take release v1, you also confirm that Coolify runs on another server than the seed. One node boots from the seed’s snapshot, without Coolify’s Sentinel container, and is health-checked at the load balancer, drained and deleted while you watch. Then set the range and go Live.
FAQ for this case
Who owns the server, Hetscale or Coolify?
Hetscale creates each new server from the seed’s snapshot with its ownership labels, and Coolify never sees it. The servers Coolify deploys to stay yours: counted as capacity, never deleted. Coolify’s own Hetzner integration is not used, so the Hetzner token lives in one place.
Which Coolify versions are supported?
Hetscale calls no Coolify API, so there is no API version to match; the path was proven live on Coolify 4.4.3. Per-server deploys through Coolify are planned for setups that meet Coolify’s multi-server rules, like this one, once a Coolify release carries them.
How do I deploy a new version?
Deploy in Coolify as you do today. When the deployment has finished, take a new release on the group’s Deployment tab, then replace the older servers. New servers boot from the current release, never from Coolify.