Remote game server (RGS)

The system that runs the round. Worth separating from the system that holds the balance, because suppliers sell both under one word.

Definition

A remote game server is the system that runs a game round: it receives the launch, executes the title's mathematics, decides the outcome and reports the result back. It belongs to the studio that built the title, or to an aggregator distributing that studio's content.

The distinction that matters

An RGS names one boundary and a wallet names another, and suppliers sell both under the word platform. Where a round is executed and where a balance is changed are separate questions with separate answers, and an integration conversation that has not separated them will produce a surprise later.

Nothing on our side executes a round. Every round executes on the studio's or aggregator's own server. We supply the catalogue and the launch layer; nothing of ours decides an outcome. The certificate behind a title belongs to the studio too, which is worth knowing when a supplier is asked who holds it — the studio archetypes page is where that question is set out.

The wallet boundary is the one that moves between our two routes, and it is covered by the seamless wallet reference. Knowing which system is authoritative for a balance settles most reconciliation arguments before they start.

Where it comes up

In due diligence, where the useful question is not whether a supplier has an RGS but whose it is. In incident triage, where a round that did not resolve has left evidence in two systems rather than one, and the logs have to be read together. And in latency work, where the round trip crosses a boundary you do not own.

Reviewed . Corrections are made visibly rather than silently.

A definition here is short on purpose. Where a term has a page behind it, the page is the better answer and the entry points at it.