What Is an RGS in iGaming? Remote Gaming Server Explained

An RGS — remote gaming server — is the hosted system that runs a casino game, produces each result and settles it against the player’s wallet. The player sees reels or a table on screen; the outcome is calculated, recorded and audited on infrastructure the game supplier controls, not the operator’s.

For studios and operators entering iGaming, the choice of RGS shapes who is responsible for fairness, certification and settlement. This article explains what a remote gaming server does, how it differs from an aggregator and a game provider, and what to check before integrating one.

What a Remote Gaming Server Actually Does

Strip away the front end and an RGS performs four jobs in sequence: decide the result, move the money, record what happened, and prove the game behaves as certified. A weak link in any one of them stalls the launch.

Game logic and results

The game client sends a request: a spin, a bet, a bonus trigger. The RGS validates the session, applies the game’s mathematical model and returns the outcome the client displays. Because the maths lives server-side, the result cannot be predicted or altered from the browser or the app, and random number generation, paytable evaluation and feature state sit in one auditable place.

Wallet and settlement

An RGS does not hold player funds. It talks to the operator’s wallet through a wallet API to debit a stake, credit a win and confirm every transaction. Ordering matters: a debit must succeed before a result pays out, and each credit must trace back to a specific round. The RGS keeps round state so a dropped session does not become a free spin or a double payout.

Reporting

Every round produces a record: the player, the stake, the win and the game version that generated it. Operators need this for reconciliation and regulatory reporting; studios need it to see how titles perform. A useful RGS gives both sides a shared, exportable view of the same numbers, so discrepancies are resolved rather than argued.

Configuration for certification

Regulators do not certify a game idea; they certify a configuration. The RGS holds the parameters a test lab reviews — return-to-player settings, bet levels, volatility profiles, maximum win caps — tied to the version under test. When an operator needs a different RTP for a market, the RGS is where that variant is defined, locked and evidenced.

RGS vs Aggregator vs Game Provider

The three terms are often used interchangeably in sales conversations, and the confusion costs integration time. They describe different layers of the same supply chain.

Layer What it is What it owns
Remote gaming server Hosted engine that executes individual games Game logic, maths, results, per-round wallet calls
Aggregator Distribution layer connecting many suppliers to many operators Contracts, a single integration, catalogue access
Game provider The studio or company that originates the games Game design, maths ownership, certification, distribution

The layers can sit inside one company. HeronByte is a game provider based in Estonia, operating since 2018 and supplying mobile-first casino content to licensed operators and partners worldwide. Its game development platform bundles an RGS with a game SDK, maths and simulation, QA and certification support, a distribution network, analytics and revenue share. The same engine supports the operator side, where a casino game API and the RGS let an operator integrate once, then review, certify and publish games.

When You Need an RGS

If you are a game studio

You have the maths and the client, but not the server-side engine, the certification evidence or a route to operators. Building an RGS yourself is possible, and rarely the best use of a small team’s time: it is infrastructure, not differentiation. A platform that supplies an RGS with maths, simulation and certification support lets a studio launch with a licensed operator without hiring a backend team. If you intend to become a game provider, the RGS decision determines how quickly operators can connect.

If you are a casino operator

You need a way to add games without a months-long integration per supplier. That is why operator-side products are built around the casino game API plus the RGS: integrate once, then review, certify and publish titles that arrive through it. In the creator-led model described by HeronByte’s casino game SDK, community creators build and submit games, and the operator decides what goes live. The RGS keeps every new title on the same compliant rails instead of a bespoke connection for each one.

What to Look for When Choosing an RGS

Commercial terms can be compared later. These five areas decide whether the integration survives its first busy weekend.

  • Scalability. Ask for the latency budget per round, behaviour during a campaign spike, and where servers sit relative to players.
  • Maths configuration. RTP variants, bet level ladders and volatility profiles should live in configuration, not code, so a new market does not need a new build.
  • Certifications. Check whether the provider supplies test-ready configurations, simulation output and QA support to the labs you work with.
  • Wallet integration. Look for a documented API with idempotent calls, round state and defined behaviour when a credit times out; the failure path matters more than the happy path.
  • Reporting. Round-level exports and reconciliation reports should reach both the studio and the operator, not only the contract holder.

A provider that answers these questions with documentation rather than slides has usually run the integration before.

Frequently Asked Questions

What does RGS stand for in iGaming?

Remote gaming server. It is the hosted system that executes a game’s logic, generates each result and settles it with the operator’s wallet.

Is a remote gaming server the same as an aggregator?

No. An aggregator is a distribution and contracting layer that connects suppliers to operators. An RGS executes the game itself and handles the per-round wallet calls.

Does the RGS hold player money?

No. Player funds stay in the operator’s wallet. The RGS requests debits and credits through the wallet API and keeps round state so the balance stays consistent.

Do I need an RGS if I already have a game client?

Yes, if the game is to run with a licensed operator. The client draws the interface; the result must come from a server-side engine that operators and testing labs can audit.

If you would rather launch on an established remote gaming server than build and maintain your own, that is the faster route to licensed operators.

Whether you are a studio looking for a route to licensed operators or a casino assembling a creator-led catalogue, the RGS is the component that makes the model work. Get in touch to discuss your integration.