Overview
A remote gaming server hosts the game logic and delivers outcomes to operators. Regulators need to know it does so correctly, securely and consistently, whichever operator a player arrives through.
We test the RGS as a system: how sessions start and end, how outcomes are generated and recorded, how games are recalled for disputes, and what happens when something fails.
What we test
- Session management and authentication with operators
- Outcome generation, logging and audit trail
- Game recall and history for player disputes
- Recovery of interrupted rounds and failed transactions
- Configuration control of game versions and RTP variants
- Critical file identification and integrity checks
- Logging, time synchronisation and reporting
What you submit
- System architecture and data flow documentation
- Test environment access
- Critical file list and hashes
- Operator integration specification
What you receive
- System evaluation report
- Certificate per jurisdiction
- Findings report, where needed
Timeline and pricing
Both depend on the scope of the product and the number of markets. We agree a fixed quote and a timeline at scoping, before any work starts, and you can follow progress throughout.