Platform at a Glance
Two verticals, one wallet
The platform runs a casino and a sportsbook side by side. A player has a single wallet per currency and moves between the two without transferring funds. Both verticals post into the same ledger, so revenue reporting, bonus wagering, affiliate commission and responsible-gaming limits all see one combined picture of a player.
┌──────────────┐
Casino games ────────►│ │
│ One wallet │◄──── Deposits (PSP)
Sports bets ────────►│ per │
│ currency │────► Withdrawals (PSP)
Bonuses ────────►│ │
└──────┬───────┘
│
Double-entry ledger
(every movement, both sides)
The actors
| Actor | What they are |
|---|---|
| Operator | You — the tenant that owns everything below. Players, staff, integrations and settings all belong to exactly one operator. |
| Player | Your customer. Registers, deposits, plays, bets, withdraws. |
| Staff | Your team, working in the backoffice console. |
| Affiliate | A marketing partner who sends you players and earns commission. |
| Game provider | A third party whose casino games you offer. |
| Odds provider | A third party whose sports fixtures and prices you trade on. |
| Payment provider | A third party that moves real money in and out. |
Where money comes from and goes
Every movement names both sides, so the platform always knows the counterparty:
| The player… | Money moves |
|---|---|
| Deposits | External payment provider → player wallet |
| Places a bet or spins | Player wallet → house stakes |
| Wins | House wins → player wallet |
| Receives a bonus | House bonus → player bonus wallet |
| Wins a jackpot | House jackpot → player wallet |
| Withdraws | Player wallet → external payment provider |
| Gets a manual correction | House adjustments ↔ player wallet |
The house side of each of those is a real account with a real balance, which is what makes revenue reporting fall out of the ledger rather than being computed separately and hoped to agree.
What an operator controls without a developer
Everything in this list is editable from the backoffice console at runtime:
- Which games are visible, how they are tagged and ordered, and their artwork, and adding OnlyPlay or qooob as a game provider
- The home page, casino lobby, sports lobby and navigation, composed from sections in the page constructor, and how lobbies rank content
- Which sports, competitions and events appear in the sportsbook, and in what order
- The market catalog — which market types players see, their names and event-page tabs — and the cash-out, quick bet and same-game combo switches
- Which odds feed is live — including adding a supported feed as a provider
- Stake, 24-hour stake and payout ceilings — globally, by sport, competition, market type or player — set once in USD with optional per-currency overrides
- Withdrawal minimums, maximums, daily caps and the review threshold, set once in USD for every fiat and crypto currency, with per-currency overrides
- Promotions, bonus money terms (set in USD, converted when issued) and wagering rules, and jackpots — their tiers, eligible games and the live switch
- The loyalty layer — XP rates, the tier ladder, level-up prizes, the rewards catalog, missions, the activity streak, standing perks (including rakeback and raised limits) and the VIP club with its hosts
- The Benefits catalog — free bets, boosts, bonus money, cash rewards and the rest, defined once and reused by every promotion, reward and grant
- Player cohorts and email campaigns — saved player groups, measured grants to them, and marketing email with consent and unsubscribe built in
- Access rules per region — which actions need verification, and the list of blocked countries
- Staff roles — which areas of the console each role can view or manage, which sensitive powers it holds, and whether it must sign in with a second factor
- Exchange-rate feeds, their quorum and deviation band
- The operator bank — client and operating accounts, payment-provider fees and reserves, and taking profit only from the surplus over player funds
- The affiliate program — campaign terms, bills, landing pages, banners and traffic sources
- Scheduled job timings — including pausing a job entirely
- Player status (suspend, reinstate), KYC status, and manual balance adjustments
- The public "big wins" threshold, and bonus defaults
- The AI assistant — on or off, and its daily and monthly spend caps
Scope & Roadmap
Implemented. Both verticals, the shared wallet, the double-entry ledger, the loyalty and reward engine, the backoffice console with its read-only AI assistant, and the operator-configurable surface above. The player site adapts to a phone with a bottom navigation bar, a docked search and slip pill and, on Android, haptic feedback; players choose among six themes and their odds notation, and can close their own account. Balances can be shown to players in USD or EUR, and every cross-currency decision refuses rather than guesses when an exchange rate is missing.
Partial. The sportsbook trades on one live feed at a time — switchable from the backoffice without a restart — but multi-provider failover and line-shopping across bookmakers are not built. Backoffice charts need the optional ClickHouse analytics store. Player-prop markets arrive hidden and are settled by hand. The operator bank ships with a simulated bank only.
Not built. See What You Still Need for the complete list.