Tooling access
Our internal Slots Automaker workspace checks project membership and permissions for art, math, and specification workflows.
Security in our software
Our casino, RGS, and internal production tooling include access controls and mechanisms for keeping game state and operational records consistent.
RGS authentication
Operator credentials and deployment configuration control access to the RGS. Requests are checked against the operator’s enabled games.
Game state & transaction integrity
The RGS records game execution and separates state across operator and player contexts.
Isolated progress
Saved progress is scoped by operator, player, currency, game, and configuration variant, so switching context does not reuse another context’s state.
Retry handling
Transaction identifiers and stored round records support repeat-request handling and help prevent duplicate game processing.
Deployment boundaries
The casino application and RGS are separate services, with their own configuration and data responsibilities.
Internal game service
The deployment templates keep the RGS on an internal service connection behind the casino application.
Versioned releases
The RGS uses versioned game packages and a separate container build. Integration tests cover game contracts, state handling, and failure scenarios.
Technical review
Contact us to discuss access boundaries, deployment requirements, and the technical details relevant to your integration.