Home / Architecture

Platform

Client to ledger in five layers.

Enterprise delivery is the whole stack, not a zip of Unity scenes. Each layer has a documented boundary so your team can reskin, rehost, or extend without rewriting math.

1. ClientHTML5 game shell
2. APIHTTPS + WS session
3. EngineDeterministic spin
4. DatabasePlayers & ledger
5. AdminConfig & reports

Shared slot engine

Reel construction, line and ways evaluation, scatter/bonus state machines, configurable RTP profiles, and seeded RNG with audit replay. New titles plug into the same engine contract.

Backend & API

Player session, wallet debit/credit, spin request/response, bonus awards, and idempotent transaction IDs. Sample OpenAPI fragment lives on the docs page.

Web admin

Players, KYC flags you attach, game enablement, RTP/paytable versions, GGR views, and raw transaction search. Built for operators, not only developers.

Database

PostgreSQL schema for accounts, wallets, bets, wins, game rounds, config versions, and append-only logs. Migrations ship with the repo.

Deployment pack

Environment templates, process layout, and a reference docker-compose for staging. Production hardening stays with the buyer’s infra team.

What we do not sell

A gaming license, payment acquiring, traffic, or a hosted casino. Those remain the operator’s responsibility in every market they enter.

Admin overview

Admin console

RTP, players, and the ledger in one desk.

  • Live and historical GGR
  • Per-game RTP target vs. observed
  • Paytable versioning
  • Player search and wallet adjustment with reason codes
  • Exportable transaction logs for reconciliation