Source: https://gameye.com/glossary/game-server-orchestration/

---
title: "What Is Game Server Orchestration? How It Works and Key Tools"
description: "Game server orchestration automates dedicated server management — session scheduling, regional placement, scaling, health monitoring, and teardown."
---

# 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](https://gameye.com/blog/what-is-game-server-orchestration/).

## 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](https://gameye.com/glossary/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 managed orchestration platform](https://gameye.com/game-server-orchestration/) · [Gameye vs. Agones](https://gameye.com/gameye-vs-agones/) · [How Gameye works](https://gameye.com/how-it-works/) · [Orchestrator](https://gameye.com/glossary/orchestrator/)

Building a multiplayer game? Gameye hosts dedicated game servers: ship your server as a Docker container and start one per match with a single API call, in a region near your players.

[See how it works →](https://gameye.com/how-it-works/)

[Back to Glossary](https://gameye.com/glossary/)

## Related terms

- ### Orchestrator

An orchestrator automates game server lifecycle — starting sessions on demand, placing them in the optimal region, and shutting them down when matches end. [Read more](https://gameye.com/glossary/orchestrator/)
- ### Session hosting

Session hosting is when a server, or computer, runs your game’s matches. Each match, with a set group of people, is considered a session. [Read more](https://gameye.com/glossary/session-hosting/)
- ### Containers

A container is a packaged, portable software unit. For game servers, it’s your entire server build — easy to deploy, replicate, and roll back. [Read more](https://gameye.com/glossary/containers/)
- ### Auto scaling

Auto scaling starts new game server instances as player load rises and releases them when demand drops — no manual intervention required. [Read more](https://gameye.com/glossary/auto-scaling/)
- ### Matchmaker

A matchmaker groups players into sessions by running player data — location, skill, latency — through a set of rules to find the best possible match. [Read more](https://gameye.com/glossary/matchmaker/)
- ### Bare-metal servers

A bare-metal server is a physical machine which lives inside a data centre. It’s a place where you’ll host your games matches and sessions. [Read more](https://gameye.com/glossary/bare-metal-servers/)