MultiConnectCloud › Server Deployments
2. Choose a layout
You make two choices when you create a deployment. Neither can be changed afterwards. To switch, create a new deployment.
Mode
| Mode | What runs | Pick it when |
|---|---|---|
| Combined | Every container is a complete server that players connect to directly. One build. Exactly one container in each region you choose | Most games. Each region has one server that runs all its matches |
| Master–Worker | Two builds. Masters (for example a lobby or matchmaker) hand players out to workers that run the matches. One master per master region, and workers in the regions you choose | You need many match servers behind one entry point, or workers that scale with load |
In Master–Worker mode each worker region reports to one master region, which can be in a different region. The platform tells every worker where its master is.
Game servers (Master–Worker only)
| Choice | What happens | Pick it when |
|---|---|---|
| Always ready | A pool of workers keeps running in each region. Each region has a minimum (always running, always billed) and a maximum. With Auto Scaling on, workers are added and removed with load between the two | Matches start all the time |
| On demand | No workers run until one is needed. Your master starts a game server for each match, and it stops when the match ends, so you pay only while it runs | Matches come and go, and idle servers would cost more than they earn |
With MultiConnectSDK either choice works with nothing to set up: on demand starts one server per match by itself. Without the SDK, your master starts and stops servers through the instance API. See Section 12.

