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
- Coolify
- Fit
- 8/10
Prerequisites, time and fit are the ADR-0028 row for this case. Hetscale's own setup is about 15 minutes in every case; the rest is work on your side.
Steps
- 01Confirm the preflight list
Registry image, all state external, same CPU architecture across the group, TLS at the load balancer with the Coolify proxy set to “None” or an HTTP FQDN, and Coolify not running on a node of the group. Preflight refuses the group otherwise.
- 02Create the Coolify token
Read, write and deploy scopes only; never root or read:sensitive. Hetscale never touches Coolify’s database or its Livewire endpoints.
- 03Connect read-only
The 14-day Observe trial with a read-only Hetzner token; the day-0 report ranges the capacity and the cost.
- 04Rehearse, then go Live
One node is created with Coolify’s SSH key, registered and validated in Coolify, deployed, 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 it with its ownership labels and registers it in Coolify afterwards. Coolify’s own Hetzner integration is not used, so the Hetzner token lives in one place.
Which Coolify versions are supported?
A compatibility matrix lists them; an unsupported version pauses the group instead of guessing.