Game providers

What a studio name on a game stands for

Every game in a lobby carries two names: the casino that shows it and the studio that built it. The second one is the fixed part. A studio writes the game's mathematics, draws it, decides how the features pay and declares the return figure for the version it releases. A casino licenses the finished game; it does not rewrite the reels.

That split decides where an answer lives. The operator controls which titles appear, which currencies are shown, what the bonus terms say and how a withdrawal is handled — questions that belong on /casinos/ and /payments/. The studio controls what happens between the moment a round starts and the moment it resolves: volatility, hit frequency, feature triggers and paytables, described in the game's own help screens for the build that is running.

A provider name is therefore a claim about software, not about an operator.

RTP, and where the figure comes from

Return to player is the share of all stakes a game's model gives back over a very long run of rounds. A declared RTP of 96% means the design is built to return 96 units for every 100 staked across millions of simulated spins. It describes the mathematics, not a schedule: it says nothing about one session or one evening.

The studio declares the figure and prints it inside the game itself, usually behind an information or rules button in the game window. That panel is the primary source: it belongs to the file loaded in front of you. Lobby tiles, promotional pages and third-party tables copy the number from elsewhere, and copies age.

When a copy and the panel disagree, the panel describes the software that is running. Related terms are defined in /glossary/.

The RNG certificate and the laboratory behind it

A random number generator produces the outcomes a slot then dresses up as spinning reels. An independent testing laboratory is a company outside both the studio and the casino, accredited by a regulator, that checks the generator and the finished game against that regulator's technical standard and issues a certificate when the build passes.

What such a review normally covers:

• the generator's algorithm, its seeding, and the absence of predictable patterns in its output
• statistical testing over sample sizes far larger than any session produces
• whether the paytable and feature behaviour match the return the studio declares
• how the game resolves an interrupted round after a disconnection or a restart
• that the build submitted for testing is the build shipped, identified by a checksum

The certificate is issued to that build, not to a casino, so it travels with the game: the same certified file in another lobby is the same certified file. It also stops there. A certificate says nothing about whether an operator pays out, what a bonus requires, or which licence covers your country — separate matters, described on /bonuses/ and /faq/.

Why one game exists in several builds

Studios frequently release a title in more than one configuration. The artwork, the name and the features stay identical while the paytable is tuned so that the declared return differs. Each configuration is certified separately and prints its own number in its own information panel. Which one a lobby serves is an operator's choice, sometimes narrowed by the jurisdiction it is licensed in.

Nothing visible from outside distinguishes them: same tile, same title. As an arithmetic example only, a build declaring 96% and one declaring 94% differ by two units per hundred staked in the model's long run — invisible within any session, and readable in the information panel in a second.

So a return figure quoted outside the game window describes some build of that title, not necessarily the one your account was served.

Three kinds of name in a provider list

Provider filters mix companies that do quite different work.

The distinction matters when a list looks long. Where an aggregator appears, several studio names beside it may arrive through the same pipe, and whether the filter shows the route or the makers changes how large the catalogue looks. A live section often comes from one supplier even when the slot shelf comes from many.

Why the list says more than the game count

A total number of games is the easiest figure to publish and the least informative to read. Back catalogues arrive in bulk, several builds of one title can be counted twice, and demo-only entries may sit in the same total as playable ones.

A provider list is harder to inflate: every name in it stands for a contract.

Reading it is comparison rather than judgement: which names recur across the lobbies in front of you, which appear once, whether the live section names anyone at all. Catalogues by studio sit on /providers/, individual titles on /games/.

How this directory records providers

Provider names on a casino card come from that casino's own lobby, filter menu or footer. Where a casino names no providers, the field stays empty: a blank means nothing was found, not that nothing exists. Studios are not inferred from a thumbnail's style, and an aggregator is not expanded into the studios behind it.

Return-to-player figures on game and studio pages come from a compiled list of titles, not from each studio's information panel. A game ships in several builds, so the figure inside the game you open is the one that applies to it.

Nobody writing here played at these casinos, so no verdict and no player rating is attached to any name, and studios carry no score at all — the six fields it is worked out from are casino fields. The site shows what operators publish about themselves and, for studios, what a compiled directory lists; the method is set out in /about/.