What You Get
The one-paragraph version
A working two-vertical gambling platform — casino and sportsbook — sharing a single multi-currency wallet, built on a double-entry ledger that audits itself every fifteen minutes and recomputes every balance from scratch nightly. A player site in five languages and an operator console, both complete enough to run a business from. Five game-provider adapters, two odds feeds, a fiat payment adapter and a testnet crypto cashier, a sportsbook with cash-out, same-game combos and one-tap quick bet, a page constructor for the home page and lobbies, a bonus engine with one benefits catalog, a loyalty layer (XP, tiers, mystery boxes, bet boosts, missions, a streak, standing perks, rakeback and a VIP club with hosts), saved player cohorts with email campaigns, a jackpot engine managed from the console, an operator bank that keeps player funds apart from profit, a self-serve affiliate program with its own partner portal, a read-only AI assistant for staff, and responsible-gaming controls that are actually enforced on every money path. About 1,500 test files, with the heaviest coverage exactly where money moves.
Where the engineering is genuinely strong
The money core. Double-entry with both sides named, positive amounts, derived balances computed atomically, mandatory unique idempotency keys with strict-conflict semantics, pinned decimal arithmetic, append-only corrections, and a scheduled invariant check that fails loudly. This is better than typical for a platform at this stage, and it is the part that is expensive to retrofit.
Failure recovery. The system assumes third parties will fail and plans for it. Half-settled casino rounds are recovered by asking the provider for truth, not by guessing. Deposits stranded by a lost webhook are reconciled on a schedule. A stale odds feed suspends its own markets at read time, with no database write, so the guard holds even when every background job is down.
Enforcement in the right places. Responsible-gaming guards run on bet placement, game launch, every provider callback, casino settlement and deposit initiation — under a row lock inside the money transaction, so concurrency cannot defeat them. Bonus max-bet declines the stake rather than clawing back winnings.
Player funds kept apart. The operator bank separates the client account holding player money from the operating account. Profit can only be taken from the surplus over what players are owed, payment-provider fees and rolling reserves are booked as they happen, and the Home page answers "are player funds covered?".
Currency safety. Operator terms — withdrawal limits, stake and payout ceilings, bonus amounts, affiliate CPA bands and tiers, player limits — are set once in USD and converted per currency. Rates are the median of several feeds, may be up to 12 hours stale, and are never guessed: a money action with no usable rate is refused. A sportsbook payout cap is frozen on each bet.
Integration seams. Five game providers and four sports sources sit behind interfaces that normalize everything to one internal shape. Adding another is one adapter, not a refactor. The Odds API poller gives live in-play betting without a push-feed contract, paced by viewers and remaining credits, and staff switch feeds from the console without a restart.
Retention built on one engine. Missions, promotions, the activity streak, XP and tiers, level-up prizes, mystery boxes, bet boosts, perks and rakeback all run on one reward engine with versioned rewards and no-double-payout retries. Players can follow leagues and teams; the sports lobby ranks a Trending view on real player activity, adapted to the player's region.
Operator tooling. A Home page answering "are we live, making money, set up, healthy", a ⌘K command center that also finds tabs and cards inside pages, a page constructor and ranking console for the lobbies, an all-limits overview, analytics pages, a searchable audit log, and an AI assistant that watches jobs, rounds, payments and the sports catalog, files findings to an inbox, and answers questions — reading only this documentation, never writing, behind a kill switch and USD spend caps.
Test discipline. About 1,500 test files with CI running the full suite against real PostgreSQL and Redis, plus a from-scratch migration apply on every change.
The operator surface
Configurable from the console, without a developer:
Game visibility, tags, ordering and artwork · generated site art per image family · home page, lobbies and navigation in the page constructor · ranking levers · sportsbook catalog visibility and ordering · the market catalog · cash-out, quick bet and same-game combo switches · adding and activating odds feeds · jackpots and their tiers · the operator bank, provider fees and reserves · stake, 24-hour and payout ceilings by scope · USD-based withdrawal limits and the payout review threshold · promotions, bonus money terms and wagering rules · XP rates, tier ladder, rewards catalog, missions, streak, perks, rakeback and the VIP club · per-region access rules and blocked countries · exchange-rate feeds and quorum · affiliate campaign terms, bills, landing pages and traffic sources · job schedules, pausing and manual runs · staff roles with per-area access · the benefits catalog · player cohorts and email campaigns · adding OnlyPlay and qooob game providers · player status, verification status and manual adjustments · bonus defaults and the public wins threshold · the AI assistant's switch and spend caps.