// the find
agones-dev/agones
Dedicated Game Server Hosting and Scaling for Multiplayer Games on Kubernetes
Agones is a Kubernetes controller and SDK for running dedicated game servers at scale. It adds GameServer and Fleet CRDs to your cluster so matchmakers and ops tooling can provision, track, and drain game server processes using standard Kubernetes primitives. Built and maintained by Google, used in production by several major studios.
Native Kubernetes integration is done right — GameServer and Fleet are first-class CRDs, so `kubectl` and your existing Helm/Terraform/GitOps pipelines all just work without a custom control plane. SDK surface is broad (Go, C++, C#, Rust, Node, Python, REST) and the sidecar pattern means your game binary only needs a few health/ready calls rather than deep platform coupling. The Wasm-based custom autoscaler is a genuinely good idea: ship autoscaling logic as a plugin without rebuilding the controller. Fleet autoscaling integrates with Kubernetes node autoscaling, so you can scale cloud VM capacity alongside game server count.
The Kubernetes dependency is not soft — if you're not already on GKE or a well-maintained managed cluster, the operational cost to run this safely (upgrades, node pools, cert management for the allocator mTLS) is substantial before you write a line of game logic. No matchmaking is included or abstracted; Agones only handles allocation once a matchmaker tells it to, so you're stitching in OpenMatch or building your own. The sidecar SDK server adds a local gRPC hop for every health check — not a problem at rest, but worth knowing if you're running thousands of short-lived servers and the sidecar startup time matters. Build tooling is heavily GCP-specific (cloudbuild.yaml scattered everywhere, Terraform modules assume GKE), which makes local development setup legitimately painful without following the Makefile exactly.