Game Server Orchestration
Game server orchestration is the automated layer that manages dedicated multiplayer game servers throughout their full lifecycle — from the moment a matchmaker decides players are ready, through regional placement, monitoring, and teardown when the match ends. The studio provides a containerised server binary; the orchestrator handles everything else.
For a full walkthrough — how session scheduling, scaling, and placement work in practice, and how to choose between a managed platform, Agones, or building your own — see What is game server orchestration? Managed vs Agones vs DIY.
What an orchestrator does
Every orchestrator performs five core functions: session scheduling (routing match requests to the best available machine in milliseconds), regional placement (selecting infrastructure closest to matched players), scaling (adding and releasing capacity in real time with demand), health monitoring and failover (redistributing sessions away from degraded nodes), and teardown (stopping the container and returning compute to the pool when a match ends).
Approaches: managed platform vs. Agones vs. DIY
| Approach | What you operate | Session start time | Team requirement |
|---|---|---|---|
| Managed platform (e.g. Gameye) | Nothing — API only | ~0.5s from warm pool | None |
| Kubernetes + Agones | Kubernetes cluster, node groups, Agones CRDs | Seconds–minutes | Dedicated DevOps |
| Build your own | Entire orchestration stack | Depends on implementation | Infrastructure team |
See also: Gameye vs. Agones · How Gameye works · Orchestrator