Remote Game Server (RGS)
An RGS is the server that runs a game's math and logic remotely — the casino frontend just renders results delivered over an API.
What it means
A Remote Game Server hosts a game's core logic — the math model, the random number generator, win evaluation and the regulatory audit trail — on the studio's or aggregator's infrastructure rather than inside the casino platform. When a player spins, the operator's frontend calls the RGS over an API, the RGS resolves the round, and the result comes back along with the wallet transaction. One certified game build can then serve hundreds of operator sites without being re-deployed into each one.
Why it matters for operators
The RGS model is what makes modern content distribution work. Studios certify a game once per jurisdiction on their own RGS, and every integrated operator inherits that certification instead of hosting and re-certifying game code themselves. It also concentrates the integration question: what you actually connect to is either a studio's RGS or a game aggregator that fronts dozens of them through a single API. The trade-off is dependency — if a studio's RGS has latency or an outage, every operator running its games feels it at the same time.
Example
An operator adds a new studio through its aggregator. No game files are installed anywhere: the platform registers the studio's game list, players' bets route to the studio's RGS, and settled results post back to the operator's wallet — with the round history stored on both sides for dispute handling.