Casino game aggregation: one integration, many studios
Aggregation is why a new casino can open with thousands of games instead of one. This explains what the aggregation layer owns, what it does not, and where RTP, jackpots and free spins are actually handled — which is rarely where operators expect.
- Technical founders
- Heads of casino
- Product managers
The problem it solves
Every game studio has its own API, its own session model, its own callback format and its own certification requirements. Integrating fifty studios directly means fifty integrations, fifty contracts and fifty things that can break independently — and each one has to be maintained forever.
An aggregator does that once. You integrate the aggregator; it integrates the studios. One contract, one technical surface, one place to look when a game misbehaves.
The trade is a layer of indirection between you and the content. You get breadth quickly and give up some directness — commercial terms are usually the aggregator's, and a studio-specific feature may arrive late or not at all.
What sits where
The boundary that matters is between the aggregator and the wallet. Bets and wins cross it, and that crossing is the seam to get right.
Who owns what
This division is worth knowing because it decides who you contact when something is wrong.
- RTP
- Set by the studio and certified per game, sometimes with several configurable variants. Neither the aggregator nor the operator changes it at runtime; picking a variant is a commercial decision made up front.
- Jackpots
- Usually the studio's, pooled across every operator running that game. That is why a network jackpot can be won on someone else's site.
- Free spins
- Granted through the studio's own mechanism via the aggregator, which is why free-spin support varies by studio rather than being a platform-wide feature.
- Game sessions
- The catalogue boundary starts, polls and ends a session and returns a launch URL. It does not implement wallet callbacks or balance logic — that separation is deliberate.
- Bets, wins and rollbacks
- These post to the wallet and its ledger. A rollback is a compensating entry rather than a deletion, so a disputed round remains readable afterwards.
Studios on the platform
172 studios are connected through the aggregation layer. These are the ones with counts visible in the launch wizard:
| Studio | Games | Type |
|---|---|---|
| Pragmatic | 2,301 | Slots |
| Evolution | 663 | Live Casino |
| Playtech | 646 | Slots |
| Pragmatic Live | 574 | Live Casino |
| Hacksaw | 345 | Slots |
| NetEnt | 220 | Slots |
| Netent Gaming | 217 | Slots |
Read from the Games and Sports step of the running product. The remaining studios are not enumerated here because this page only carries figures that can be checked.
Selecting content
Curated collections
Selecting a collection is usually a better starting point than switching on every studio, because lobby quality beats lobby size on conversion.
| Collection | What it contains |
|---|---|
| Top 100 Games | Best performing games overall |
| Most Popular | Most played by players |
| New Releases | Released in the last 30 days |
| High RTP | RTP higher than 96% |
| Live Casino | All live dealer games |
| Crash Games | All crash and instant games |
| Megaways | All Megaways games |
| Jackpot Games | Progressive jackpots |
Common questions
How many games do I get?
172 studios are connected, and how many titles you expose is your curation decision. Enabling everything is rarely the right answer — a focused lobby matched to the market converts better than an exhaustive one.
Can I change a game's RTP?
No. RTP is set and certified by the studio. Some games ship in several certified variants, and choosing among those is a commercial decision made when the game is enabled.
What happens if a round fails midway?
The round is reconciled against the aggregator and any correction posts to the ledger as a compensating entry. Posted entries are immutable, so the original and the correction are both readable afterwards.
Can I integrate a studio directly?
That is an integration conversation rather than a platform limitation. It is usually worth first checking what the aggregation layer already reaches, since a direct integration is a permanent maintenance commitment.
Pick a catalogue and see the lobby
Choose studios and collections in the builder and see the storefront that results, in the browser.