Jackpots
Contribution from every qualifying round, growth of the pot, triggering and payout.
Game engine
One core, every game type.
The engine runs the server-side cycle of a game: sessions, accepting bets and rounds, storing game state, logging every game event, and the random-number generator. Different types of game logic run on top of that core: slots, roulette, card, crash and bingo games.
- Slots
- Roulette
- Card games
- Crash
- Bingo
One round, end to end
From session to audit record.
The player sees the game. The operator sees the reports. Everything in between is the server side: it takes the bet, draws the outcome, calculates the payout and leaves a trail for the audit. Here is the full cycle of a single round in our architecture.
0 ms · Authentication
The session opens
The player opens the game through the operator platform. The engine creates a session from the platform's authentication token.
9 ms · Bet
The money is reserved
The engine checks fund availability with the platform, then reserves and debits the bet amount.
31 ms · Draw
The outcome is determined
The random-number generator determines the outcome of the round. The result is written to the game event log.
58 ms · Calculation
The payout is calculated
The engine turns the outcome into a payout by the rules of the game type: winning lines, multipliers, bonus triggers.
112 ms · Payout
The winnings are credited
The winnings are credited to the player's balance through the platform API.
240 ms · Round closed
The trail remains
Round events go to the log and to reporting; jackpot and bonus counters are updated. The round history stays available in the system.
Bonus module
Bonus mechanics.
Bonus mechanics hook into the round lifecycle without slowing it down. The engine feeds jackpot and bonus counters as rounds close, and every bonus payout stays traceable in the event log and reconcilable in reporting.
Bonus systems
Bonus mechanics tied to the round lifecycle: triggers on the outcome, awards on top of the payout.
Loyalty integration
Points and rewards handed over to the operator's external loyalty systems over a stable contract.
Compliance
Every action leaves a record.
To operate in regulated jurisdictions the system keeps integrity control over its components, a log of every configuration change, an audit trail of user actions and the history of game rounds.
- 14:02:04AUDITconfig_changedgame=bingo · table limits updated · by compliance@operator
- 14:02:05INFOaudit_loggedaction #48 112 · user=compliance@operator
- 14:02:25AUDITaccess_grantedrole=auditor · scope=history · by compliance@operator
- 14:02:28INFOaudit_loggedaction #48 113 · user=compliance@operator
- 14:03:04INFOsession_openeduser=compliance@operator · ip=10.4.13.182 · mfa=ok
- 14:03:39INFOsession_openeduser=compliance@operator · ip=10.4.1.167 · mfa=ok
- 14:04:22INFOrounds_archivedrounds=722 000 · storage=cold · retention=5y
- 14:04:30OKintegrity_checkcomponents 24/24 · checksums verified
- 14:04:38AUDIThistory_exportrounds 10.07–21.07 · by auditor
- 14:04:41INFOaudit_loggedaction #48 114 · user=ops@operator
Operator panel
The operator's side of the engine.
Everything the engine records has to reach a person. The panel is where the operator works with the running system, and the reporting module turns what the engine logged into data the operator can take out of it.
Control panel
player activity monitoring
game configuration management
integrations with operators and external platforms
Reporting
financial reporting by operator
game analytics and player-level reports
operational data export
Reliability
A component failure does not stop the game.
System components are redundant and data goes to backup storage. From the outside, the system is covered by fraud protection and DDoS protection.