Swarm Zones

A Swarm Zone is a deployment target that groups one or more Swarm Hosts. When you launch a game server to a zone, the scheduler chooses an eligible host based on availability, CPU, memory, and storage health.

Swarm Zones are not relay registration records. Relays are platform-operated infrastructure and are managed separately by Swarm Hosts. Operators can assign a static platform relay to a demo Swarm Zone from the admin app; user-owned zones continue to choose network paths at launch.

Operators can also set a demo-only CPU overcommit ratio from the admin app. A 2x ratio doubles CPU scheduling capacity for that demo Swarm Zone while memory capacity remains bound to the hosts' normal memory limits.

User-Owned Zone Setup

Use this path when you want deployments to run on hardware you control.

  1. Register one or more Swarm Hosts from Profile > Agent download.
  2. Open Swarm Zones and create a zone with a name, description, and any registered hosts that are not already part of another Swarm Zone.
  3. Confirm the zone detail page shows the assigned hosts and zone status.
  4. Use the zone detail page to add more unassigned hosts later.
  5. Launch a game server and choose the Swarm Zone as the deployment target.

Deployments sent to a Swarm Zone are placed automatically. Users do not choose the individual host during launch.

Scheduling Notes

The scheduler only considers hosts that are online, assigned to the zone, and healthy enough for the requested deployment. It checks available CPU, memory, and storage before placing the game server.

If no host has enough available capacity, the launch will fail or queue depending on the deployment workflow.

Demo Regions

Demo Regions use the same Deployment Target model, but they are platform-owned and public to registered users. Only admins can create or manage Demo Regions. Admins can pin a managed relay and choose the CPU overcommit multiplier for each Demo Region.

Registered users only see Demo Regions during launch. They cannot inspect demo hosts, relay internals, or other users' deployments.