The studio that builds a slot is almost never the company that holds your money, verifies your identity or answers your complaint. The studio makes the game, the operator runs the account and the payments around it, and an aggregator often sits in the middle, passing the game from one to the other. Once you separate those three jobs, a lot of confusing player experiences stop being confusing.
The three roles, defined by what each one controls
The studio: the game itself
A B2B studio designs and builds the game. That means the maths model (how symbols are weighted, what the paytable returns, how bonus features trigger), the art and sound, the random number generator integration, and the rules screen you see inside the game window. The studio typically submits its finished product to an independent testing laboratory and keeps a version history so a specific build can be traced later.
What the studio does not normally control is who plays, where, or with what money. It does not hold your balance. It usually never learns your name. From its side of the wall, a session is a stream of events: a stake was placed, a spin resolved, a win was credited to a wallet it cannot see into.
The operator: the account, the money and the rules around play
The operator is the company you sign up with. It runs registration, identity and age checks, deposits and withdrawals, bonus terms, responsible-gambling tools such as deposit limits and self-exclusion, and customer support. It is also the party that holds the licence permitting it to offer gambling to people in particular places. When you ask where your withdrawal is, why a bonus was removed or how to close an account, you are asking the operator, whatever logo is on the game.
This is why the same slot can feel different in two places even though the studio’s code is identical. One operator may offer a lower-volatility bonus structure around it, process withdrawals within hours, or restrict certain features in certain regions. The game’s core behaviour is the studio’s; the experience wrapped around it is the operator’s.
The aggregator: the connecting layer
An aggregator is an intermediary that integrates hundreds of games from many studios once, then lets an operator plug into the whole catalogue through a single connection. For the operator it saves the work of building dozens of separate integrations. For the studio it opens a distribution channel it could not easily reach alone.
The aggregator typically handles the technical traffic between systems: launching the game, passing bets and results, reconciling balances between the operator’s wallet and the game server, and sometimes adding promotional tools like tournaments or free-spin campaigns across studios. It is plumbing, and like plumbing it is mostly invisible until something leaks.
Why the split matters when you read a game’s numbers
Return-to-player figures illustrate the division well. An RTP percentage describes the long-run share of total stakes a game’s maths model pays back as gross returns across a huge number of spins. Gross return means everything paid out to the player; it says nothing about whether any individual person ends up ahead. Net profit is what you actually keep: total returns minus total stakes, plus or minus any deposits and withdrawals considered separately.
A hypothetical makes the difference concrete. Suppose a game’s model returns 96 percent in the long run and a player stakes a total of 1,000 over a month of play. The expected gross return is 960, so the expected net result is a loss of 40. But “expected” is doing heavy lifting: in any real month the outcome could be a net profit of several hundred or a loss of nearly the whole 1,000, because short-run variance swamps the long-run average. The 96 percent figure is a property of the studio’s maths; whether you finish a given month above or below zero depends on luck in that sample.
Here the roles diverge again. Some studios publish multiple RTP configurations of the same game, and an operator may select which configuration to run, within what the studio offers and the licence allows. So the studio defines the possible versions, while the operator decides which one you meet. This is a good reason to check the game’s information screen on the specific site you play rather than assuming a figure quoted elsewhere applies. I am not citing any current RTP here; the point is that the number is configuration-dependent and the place to read it is inside the game you are actually launching.
Support and dispute scenarios: who answers, and why
Consider three invented but realistic situations.
First, a spin freezes mid-bonus after your connection drops. The studio’s server recorded the round state and will usually complete or resolve the round on its side. But the studio cannot see your account, so the operator’s support team has to request the round record, often via the aggregator, before they can tell you what was credited. Contacting the studio directly typically goes nowhere, because it has no customer relationship with you.
Second, a withdrawal is pending for days. Nothing about the game is involved. This is entirely the operator’s verification and payment process, and the aggregator and studio have no say in it. A player who blames the game provider here is addressing the wrong party and losing time.
Third, you believe a bonus feature paid less than the rules screen implied. This one genuinely spans roles. The rules screen is the studio’s text, the payout figure is a game-server result, and the credit to your balance is the operator’s ledger entry. A sensible complaint names the game, the approximate time, the stake and the round identifier if the history shows one, and goes first to the operator, who can escalate to the aggregator or studio. Keeping that chain in mind explains why a good answer sometimes takes a few days: three companies may each need to check their own logs.
Licences have a jurisdiction and a scope
A licence is not a general certificate of virtue. It is permission granted by a particular regulator, covering particular activities, in particular territories, under particular conditions. Studios often hold their own supplier licences or certifications, which cover making and supplying games; operators hold licences covering offering gambling to players. Those are different permissions attached to different companies, and one does not substitute for the other.
Scope matters in practice. An operator licensed in one jurisdiction is not thereby authorised to serve players in another, and the protections attached to a licence, such as complaint procedures or segregation rules for player funds, are defined by the issuing regulator and apply on its terms. Reading that a site is “licensed” tells you little until you know who issued it, which legal entity holds it, and whether it covers your location. Location and identity checks exist because of this structure, and they are not something to work around; if a site asks for them, that is the licence conditions operating as designed.
A recognisable brand does not prove a trustworthy operator
Because games from well-known studios appear on thousands of sites, their logos are a poor guide to who is running your account. A respected studio’s name on a lobby tells you the game’s maths likely came from that studio, assuming the site is genuinely using licensed content. It tells you nothing about how that operator handles withdrawals, whether it honours its own bonus terms, or whether it answers complaints.
The reverse also holds: a modest operator can run reputable games well. What actually informs trust is operator-level evidence: the licensing entity named in the footer and whether it can be matched to a regulator’s own register, clear terms that apply the same way to everyone, consistent and documented payment handling, and a complaint route that leads somewhere. Those are properties of the company holding your balance, which is why the question to ask about any site is not “whose games are these?” but “who is the operator, under which licence, and what happens when something goes wrong?”
Keep the division in mind and the product makes more sense: the studio decides how the game behaves, the aggregator decides how it reaches the operator, and the operator decides everything about your account, your money and your recourse.