Introduction
This is the product documentation for a complete iGaming platform: a real-money online casino and sportsbook, with the player-facing site, the operator console, and the accounting engine underneath both.
It is written for someone evaluating the platform as a turnkey purchase — you want to know what the software actually does, how the business logic behaves, what you can configure without a developer, and what work remains between here and taking real bets.
What this documentation promises
It tells you what is built, and what is not. Every chapter ends with a Scope & Roadmap section that states plainly which parts are implemented, which are partial, and which are absent. There is a whole chapter — What You Still Need — devoted to the gaps.
This is deliberate. A turnkey platform is only worth what it saves you, and you cannot price that without knowing where the work stops. Every claim here was checked against the source code.
How to read it
If you are evaluating, read Platform at a Glance, then What You Get and What You Still Need. Those three answer "is this the right base to build on?"
If you are planning operations, the Backoffice Console, Money & Reporting and Scheduled Jobs & Automation chapters describe the day-to-day job.
If you are assessing risk or compliance, read Money Core: The Ledger, Responsible Gaming and KYC & Identity Verification.
The shape of the product
Three things ship together:
| Piece | Who uses it |
|---|---|
| Player site | Your customers. Casino lobby, sportsbook, wallet, account settings, responsible-gaming controls. |
| Backoffice console | Your staff. Players, money and the operator bank, catalog, page constructor, promotions and VIP, affiliates, sportsbook trading, jobs, AI assistant. |
| Platform API | Both of the above, plus every third-party integration — game providers, odds feeds, payment providers, identity verification. |
Underneath all three sits a double-entry ledger. Every stake, win, deposit, withdrawal, bonus and commission is a balanced movement between two accounts, and the system checks its own books every fifteen minutes. That design decision shapes most of what follows, so it has its own chapter.