KEY TAKEAWAYS
CONTENTS
What a Game Aggregator Does
A game aggregator is a technical service that connects an online gambling platform to games made by many different studios through a single integration. Without one, a platform would have to build and maintain a separate connection to every studio, each with its own rules for logging in players, moving money and reporting results. With one, the platform connects once, and the aggregator handles the many connections behind it.
That is the plain-language answer. The more interesting part is what happens when a player taps a game. The game itself usually does not run inside the platform. It runs on a remote game server, a computer operated by the studio or the aggregator that holds the game logic, produces the result and sends the picture and sound back to the player’s screen. The platform keeps the player account and the money.
This article follows that arrangement piece by piece: what each part does, how a single game round passes between them, where the game result is decided, and how designs differ. It is a general explanation. Real systems vary by supplier, platform and state, and none is named here.
How the Pieces Fit Together
Four parts take part in almost every round of an online casino game. Knowing their jobs makes the rest of the topic easy to follow.
The platform is the operator-side system that holds the player account, the balance, the limits and the rules about who may play. A fuller map appears in the guide to how an online gambling platform works, and the account piece is covered in what a player account management system is.
The game studio designs the game: its rules, graphics, sounds and the mathematics that set the payouts. The studio’s game logic normally runs on its own servers, which is why the term remote game server exists.
The aggregator sits between platform and studios. It offers the platform one standard interface, often called an application programming interface (API), an agreed set of messages that two computer systems use to talk. It translates between that standard and each studio’s own format.
The player’s device runs an app or web page that shows the game. It collects taps and clicks and draws what the server sends. It is a display and an input device, not the place where results are decided.
Because the money lives in one place and the game logic in another, the two must stay in step. That is the central design problem, and the next section shows how it is usually solved.
Under the Hood: Wallet Calls, Sessions and Results
Two ideas carry most of the engineering: a seamless wallet and a game session.
In a seamless wallet design, the balance stays on the platform. Each time the game needs to take a stake or pay a win, the game server sends a request to the platform, and the platform approves or refuses it and updates the balance. The alternative, a transfer wallet, moves a sum of money into a separate game balance and moves what is left back afterwards. Both exist, and which one is used depends on the suppliers and the platform.
A game session is the period during which one player is connected to one game. The platform asks the aggregator to launch a game for a player, and the aggregator returns a link or token that opens the game with the right account attached. The token usually carries no passwords or card details; it is a short-lived pass that proves the request came from the platform.
Standards describe who decides the result. GLI-19, the interactive gaming standard published by the independent test laboratory Gaming Laboratories International (version 3.0, July 2020), says player software must not contain logic used to generate the result of any game, and that all critical functions, including generating any game outcome, are performed by the gaming platform and are independent of the remote player device. In other words, the screen shows the answer; it does not work it out.
The same standard recognises that parts of a system may be built separately. It states that the components of an interactive gaming system may be constructed in a modular fashion but are designed to work seamlessly together, and that the final configuration depends on options chosen by the operator. Regulators address third-party game software too: the UK Gambling Commission, for example, publishes a dedicated technical standard on the use of third-party software (RTS 16).
Where the random number generator (RNG) sits is explained in how casino RNGs work. In an aggregated design it typically runs on the studio’s server, alongside the game logic.
Walkthrough: One Game Round, Step by Step
The following is a typical, hypothetical flow for a slot-style game on a generic platform. Real flows differ in detail.
- The player opens the game. The platform checks the account is allowed to play and asks the aggregator to start a session.
- The aggregator launches the game. It forwards the request to the studio’s remote game server, which returns a game link carrying a session token.
- The player places a stake. The device sends the choice to the game server, not to the platform.
- The game server asks the wallet. It calls the platform to reserve the stake. The platform checks the balance and limits and replies yes or no.
- The game server decides the result. Its RNG and game logic produce the outcome and calculate any win.
- The wallet is updated. The game server reports the result and the platform adds any win to the balance.
- The device draws the outcome. Animations are shown after the result already exists on the server.
- The round is recorded. Each party keeps a record, so a disputed round can be traced afterwards.
Variations: Aggregators, Direct Integrations and Platform Models
Not every platform uses an aggregator, and aggregators themselves differ. The table compares typical setups; these are general patterns, not rules.
| Setup | How games are connected | Typical trade-off |
|---|---|---|
| Aggregator integration | One API connection to many studios | Fast to add games; one more party in the chain |
| Direct studio integration | One connection per studio | More control over each game; more engineering work |
| Platform-owned games | Games run on the platform’s own servers | Tight integration; narrower catalogue |
| Land-based server-based gaming | Games downloaded to cabinets from a central server | Different environment; covered under casino technology |
Turnkey and white-label platforms often bundle an aggregator with the player account system, while a custom-built platform may connect to aggregators and studios separately. Live dealer games add another layer, because the game is a video stream from a physical studio; see how live dealer studios work. State rules can also limit which games and suppliers a platform may offer, so the same technology is configured differently from one state to the next. A platform that adds a new studio usually has to test the connection, confirm that the game meets local technical rules and then release it, which is one reason catalogues change gradually rather than overnight.
Myths and Limits
Myth: the game runs on the player’s phone. In real-money games the result is generated on the server side. The device draws what it is told, and GLI-19 states that player software must not generate game results.
Myth: the aggregator decides who wins. An aggregator is a connection and translation layer. In the typical design it passes messages between platform and studio rather than producing results, though the exact split depends on the supplier.
Myth: more games means fairer games. The size of a catalogue says nothing about fairness. Fairness comes from how each game’s RNG and payout maths are built and tested, which is a separate question.
A real limit: an aggregator adds a link to the chain. If a connection fails mid-round, the systems need rules for finishing or voiding the round. Standards cover interrupted games for that reason, and platforms record rounds so they can be reviewed.
Key Facts to Take Away
| Question | Short answer |
|---|---|
| What is an aggregator? | One integration that reaches many game studios |
| Where does the game run? | Typically on a remote game server |
| Who holds the balance? | Typically the platform’s wallet |
| Who decides the result? | The gaming system’s server side, not the device |
| What can a player do? | Nothing to change this; the game’s help page shows its rules and payout information |
A reader who wants to understand a game that fails to load can usually take only legitimate steps: refresh the app, check the connection, update the app, or contact the platform’s support. When a round is interrupted, the platform’s records are what let support review what happened, so keeping the app’s round history or a screenshot of the error is useful. Most aggregated games also show a round or transaction number, and quoting it to support speeds up any review.
Related Concepts and Next Step
Game aggregation is one layer of the platform. The natural next reads are the overview of how online gambling platforms work for the full picture, the explanation of player account management for the system that holds identity and balances, and the RNG guide for how a result is produced once a stake is placed. Readers curious about the land-based side can also see how slot machines work inside the cabinet, where games are delivered to machines in a casino rather than to phones. Comparing the two shows how much of the same logic, a wallet, a game engine and a record of every round, appears in both settings.
Frequently Asked Questions
