More hosts than you can edit by hand
Frontends, backends and certificates live in one database. A deploy renders each host's whole config from it, so the fleet cannot drift into per-host snowflakes.
Manage frontends, backends, load balancers and TLS certificates in one place — then push the result to every host, validated and reversible.
haproxy.cfg over SSH, this replaces that loopFrontends, backends and certificates live in one database. A deploy renders each host's whole config from it, so the fleet cannot drift into per-host snowflakes.
Preview the exact diff before it leaves the panel. The host validates the new config and restores the old one if it will not load, and every push is kept so a rollback is a re-push rather than a reconstruction.
Load balancers can share a host, split by Host header on the same :80 and :443 with their certificates served from a crt-list — instead of one machine per site.
Editing anything in the panel changes desired state only. Nothing reaches a managed host until you deploy — and a deploy renders each server's entire configuration from scratch.
edit in panel → preview diff → deploy → validated & reloaded on the host
↓ on failure
previous config restoredConfiguration is validated and reloaded on the host in one operation. If it fails, the previous config is restored.
The panel stores a hash of what it last pushed, so it can tell you when a host stopped matching what you deployed.
Every deploy stores the text it pushed. Rolling back is re-pushing an earlier one — not reconstructing it.
Several load balancers can live on one entry server, routed apart by Host header on shared :80 and :443 with certificates served from a crt-list.
One origin down out of several is reduced capacity; all of them is an outage. The panel reports the difference and names the failing origin.
Point the panel at a fresh Ubuntu host with an SSH password. It installs HAProxy and the Data Plane API, verifies its own key, and registers the server.