Use case · Gaming
Game backends
A game backend is the online services behind a game — player accounts, matchmaking, progression and inventory persistence, leaderboards, and in-game economy. It is a scalable application-and-database backend that must handle the player base, stay reliable, and often absorb launch spikes. Dedicated, EU-hosted infrastructure gives it performance, scalability, and European sovereignty over player data.
Key points
- A game backend is the online services behind a game, distinct from the real-time game servers.
- It handles accounts, matchmaking, progression, inventory, leaderboards, and in-game economy.
- It's an application-and-database backend that must persist player data reliably.
- It scales with the player base and must absorb launch and event spikes.
- EU hosting keeps player data under European sovereignty.
What is a game backend, and what does it need?
A game backend is the set of online services that support a game around the actual play — player accounts, matchmaking, saving progression and inventory, leaderboards, in-game purchases, and social features — as distinct from the real-time game servers that run the matches. Where the game servers run the live simulation of a match, the backend handles the persistent, online parts of the game: who the players are, how they are matched, what they have earned and own, how they rank, and how they interact. This backend is essential to a modern online game, and it is a different kind of workload from the real-time game servers, closer to an application-and-database backend.
What a game backend needs, therefore, is what a scalable application backend needs, applied to a game: compute to run its services, databases to persist player data reliably, the ability to scale with the player base, and reliability so the services players depend on stay available. It must handle the load of the player base, keep players' data safe, and stay up. This page focuses on the game backend; the real-time game servers are covered on the game server hosting page, while what follows attends to the online services a game backend provides and what hosting them requires.
Player accounts, authentication, and profiles
A game backend handles player accounts, authenticating players and holding their profiles, which is foundational since almost everything else depends on knowing who the player is. Players have accounts they sign into, and the backend authenticates them and holds their profile — their identity, settings, and the data tied to them — so that the game knows who each player is and can associate their progression, purchases, and social connections with them. This account and identity handling is the foundation of the backend, underpinning the personalised, persistent experience online games provide.
Handling accounts well means the backend authenticating players securely and holding their profile data reliably, at the scale of the player base. Authentication must be secure, since accounts hold players' data and sometimes purchases; and the profile data must be held reliably and served responsively as players sign in and play. This is an application-and-database workload, run on the backend's infrastructure. We provide the infrastructure a game backend's account and profile handling needs — compute for the authentication and account services, and databases to hold player profiles reliably — so that the foundation of the backend, knowing and authenticating the players, runs securely and reliably at the scale the game reaches.
Matchmaking
Matchmaking — pairing players into matches — is a key game backend service, bringing players together into games and connecting them to the game servers that will run those matches. When players want to play, the backend's matchmaking gathers suitable players together, based on the game's criteria such as skill or region, and arranges the match, then directs the players to a game server to play it. This matchmaking is part of the backend rather than the game server, since it operates across the player base to form matches before the real-time play begins on a game server.
Matchmaking connects the backend to the game servers, forming matches and handing them off to be played, which requires it to work across the players seeking games and coordinate with the game server capacity. Good matchmaking pairs players well and quickly, drawing on data about players and the available game servers, so the infrastructure must support the matchmaking service and its coordination. We provide the infrastructure a game backend's matchmaking needs — compute to run the matchmaking, and the coordination with the game servers matches are handed to — so that players are matched into games and connected to servers, which is a central backend service linking the player base to the game servers where matches are played.
Player data and progression
A game backend persists players' progression, inventory, and the data that makes up their ongoing experience, which must be held reliably since losing it would lose players' accumulated progress. Players in modern games accumulate progression — levels, achievements, earned content — and inventory or possessions, and this data must be saved and available whenever they play, across sessions and devices. Losing it would be losing what players have earned and built, which is unacceptable, so persisting this data reliably is a critical backend responsibility, resting on dependable databases.
This makes the backend's data persistence, and the databases behind it, central to a game backend, needing reliability and the capacity for the player base's data. The databases holding players' progression and inventory must be reliable and durable, so the data is not lost, and performant, so it is served responsively as players play; and they must scale with the player base. We provide well-resourced, reliable database infrastructure for a game backend's player data — holding progression, inventory, and the players' ongoing state durably and serving it responsively — so that players' accumulated progress and possessions are persisted safely and available whenever they play, which is fundamental to the experience a game backend supports.
Leaderboards, stats, and social features
Game backends often provide leaderboards, statistics, and social features — rankings, player stats, friends, and interactions — which add to the backend's workload with data-heavy, sometimes real-time services. Leaderboards rank players, requiring the backend to track and order players' standings, sometimes across large player bases; statistics record and present players' performance; and social features connect players as friends and let them interact. These features, expected of modern online games, are backend services drawing on player data, some needing fast updates or real-time behaviour, adding to what the backend does.
Supporting these means the backend having the compute and data services they need, including fast data handling for leaderboards and social features. Leaderboards over large player bases, frequently updated, benefit from fast data stores; social features connect players and handle their interactions; and statistics accumulate and are queried. These draw on the backend's databases and sometimes fast in-memory data stores. We provide the infrastructure a game backend's leaderboards, stats, and social features need — the compute and data services, including fast data handling where leaderboards and social features require it — so that these features, expected of online games, run well as part of the backend, drawing on player data at the scale the game reaches.
Scaling with the player base and launches
A game backend must scale with the player base, and handle the sharp spikes that game launches and events bring, which can be dramatic. As a game gains players, the backend's load — accounts, matchmaking, data persistence, and the rest — rises, so it must scale to handle the growing player base. And games famously see enormous spikes at launch, when many players arrive at once, and around events, which the backend must absorb or fail at the worst moment, since a backend overwhelmed at launch gives players a poor first experience precisely when it matters most.
Supporting this means a backend that scales — application services across more servers, databases scaled to the load — and is provisioned for the peaks launches and events bring. The application tier scales horizontally to handle more players; the databases scale to persist and serve more data; and provisioning for launch peaks, which can far exceed steady load, prepares for them. We provide infrastructure that scales a game backend with its player base and for its peaks — compute and databases sized to grow, with capacity for the spikes launches and events bring — so that the backend handles the players it has and the surges games famously face, rather than being overwhelmed when a launch or event brings players in at once.
Reliability, sovereignty, and where we fit
A game backend must be reliable, since players depend on its services to play, and it holds player data — including the personal data of European players — so its reliability and sovereignty both matter. When the backend is down, players cannot sign in, match, or access their progression, disrupting the game, so the backend's reliability is important to players being able to play at all. And the player data it holds, including personal data, makes where it runs a sovereignty consideration. VV Internet Hosting is incorporated in the Netherlands, within the EU, so a game backend hosted with us runs under European jurisdiction and outside the direct reach of the US CLOUD Act, keeping player data under European law.
We host dedicated infrastructure for game backends: compute for the backend services — accounts, matchmaking, leaderboards, and the rest — well-resourced reliable databases to persist player data, fast data stores where leaderboards and social features need them, and the scalability to grow with the player base and absorb launch spikes, in EU datacenters under European jurisdiction. This suits games that want a performant, scalable, reliable, sovereign backend they control. We are clear about our limits: we provide the dedicated infrastructure the backend runs on, not the game or backend software itself, nor a managed game-backend platform. We are the dedicated, sovereign infrastructure on which a game's backend runs — and if that fits your game, we can host it well.
Related use cases
See also
Questions
Game backends, answered plainly
Common questions about hosting for Game backends.
How is a game backend different from a game server?
A game server runs the real-time simulation of a match — latency-critical live play. A game backend is the online services around the play: player accounts, matchmaking, saving progression and inventory, leaderboards, in-game economy, and social features. The backend handles the persistent, online parts of the game and is closer to an application-and-database backend than to the real-time game servers.
Why is data persistence so important for a game backend?
Because players accumulate progression — levels, achievements, earned content — and inventory that must be saved and available whenever they play, across sessions and devices. Losing it would lose what players have earned and built, which is unacceptable. So persisting this data reliably, on dependable and durable databases, is a critical backend responsibility.
Why do game backends need to handle spikes?
Because games famously see enormous spikes at launch, when many players arrive at once, and around events. A backend overwhelmed at launch gives players a poor first experience precisely when it matters most. So the backend must scale — application services and databases — and be provisioned for peaks that can far exceed steady load, to absorb the surges games face.
Planning Game backends infrastructure?
We host dedicated, EU-sovereign infrastructure sized to your workload — and we will tell you plainly when something else fits better. Tell us what you're building.