MultiConnectCloud › Server Deployments
1. What a server deployment is
A server deployment runs your server process in containers. Each container runs one copy of your build and has its own public IP address and port. Players connect to a container directly. There is no load balancer in front, because a game session lives on one machine.
| Term | Meaning |
|---|---|
| Container | One running copy of your server, with its own public address |
| Region | Where containers run. Choose the regions closest to your players |
| Plan | The CPU, memory and storage each container gets, and its hourly rate. The form shows the price of each plan |
| Build | A .zip of your built server, not your source code |
| Generation | One set of containers. A redeploy or plan change brings up a new generation next to the old one |
| Grace period | How long an old generation keeps serving the players already on it after a redeploy |
Because containers are replaced over time, their addresses change. Never hard-code a server address in a client. Section 9 explains how clients find a server.

