Two apps on two servers, no load balancer
Two apps on two servers means two of everything: two groups, two balancers or two pools, two rehearsals. The two to three hours are mostly the balancers; the fit of 5 reflects that most of this work is on the customer’s side.
- Prerequisite work
- two Hetzner load balancers
- Time to set up
- 2–3 h
- Adapter
- Snapshot or webhook
- Fit
- 5/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
- 01One group per app
A group is one set of identical servers behind one load balancer. Two apps are two groups, and every plan includes as many groups as you need: what you pay follows the nodes the two groups run together, and Starter covers five.
- 02Two Hetzner load balancers
A Hetzner load balancer per app with TLS and DNS moved to it. Cloudflare Load Balancing with a pool per app is planned as a second traffic provider; until it ships, the two Hetzner balancers are the supported setup.
- 03Move state out of both
Databases, sessions and uploads off the servers; a node’s disk does not survive its removal.
- 04Connect, rehearse each group, go Live
The Observe trial reports per group. One Rehearsal per group, then Live with minimum 2 each.
FAQ for this case
Can the two apps share one load balancer?
No. One Hetzner load balancer serves one group. Cloudflare Load Balancing, where one balancer carries two pools, is planned and not yet supported.
Does a second group cost extra?
No. Groups are unlimited on every plan; the plan covers the nodes both groups run together, the seed server of each app included. Two groups at minimum 2 fit inside Starter’s nodes; Starter covers one Hetzner project, so with a project per app, as we recommend, it is Growth.