Start with the runtime responsibilities: game execution, random-number generation, sessions, wallet transactions and round recovery. Establish which parts of the engine you bring and which are provided by the RGS. A hosted server, a development kit and an aggregation layer are related but different deliverables.

Test the operator and studio interfaces, retry handling, reconciliation, interrupted rounds and audit records with the intended architecture. Confirm who controls game versions, math configurations, deployments, credentials and regional restrictions. Request hosting, monitoring, backup and incident-response commitments for the purchased plan.

Separate platform certification from approval of each game and its configuration. A technical connection to an operator or aggregator does not provide a commercial content agreement. Compare subscription fees, transaction definitions, minimums, support, implementation work and source-code rights before selecting a delivery model.

What to compare

Product role

Which game-serving and operational responsibilities does the RGS cover?

Game-engine scope

Can you bring an engine, use a provided engine, or combine both?

Operator and studio integration

Which APIs, wallet flows, retries and round-recovery behaviours are supported?

Reporting and control

What game, transaction, version and operational records are available?

Certification responsibilities

Which platform components are certified and which game approvals remain required?

Deployment and support

How are hosting, release control, monitoring, service levels and recovery managed?

Commercial model

How are subscription, usage, integration, support and source-code rights priced?

Buyer questions, answered

Is an RGS the same as a player account platform?

No. An RGS focuses on game-serving infrastructure. Hizi’s terms, for example, explicitly exclude player account management.

Source

Does access to an RGS grant rights to third-party games?

No. The published Hizi aggregation deployment separates technical software from the operator’s own content agreements.

Source

Does platform certification approve every game automatically?

No. Hizi’s engine announcement distinguishes certified platform components from the individual game submitted to a test house.

Source