PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

White-label

Sports betting software, white-labelled for you

Customizable sportsbook software for licensed operators. Original code, finished under your branding, scoped in writing before any build starts.

What it typically includes

How white-labelling works

Related reading

Scope areas for this kind of build

Overview

An Immutable Ledger Under Every Bet

  • Wallet movements are append-only entries each carrying their own reference, so exposure, settlement and payout can be reconstructed months later for a regulator or an auditor.
  • Skip the brochure. We hand over a customer login and an operator login to the running platform: place a back and a lay, build an accumulator, launch a casino game, then settle the market from the other side.

Betting Surface - Your Brand, Your Domain

  • What the customer sees: sport and competition browsing, the exchange order book with back and lay, the fixed-odds bet slip with accumulators, live in-play markets and cash-out.

Games, Balances & Loyalty

  • The rest of the account: the casino catalog with category and provider filters, a multi-currency wallet with its ledger view, loyalty tiers and rewards, promotions and the affiliate dashboard.

Settlement, Risk & Compliance

  • Running it day to day: KPI dashboard, user management with KYC review, transaction oversight, market settlement and voiding, the risk desk, margin configuration and the audit log.
  • Try: admin@mxbetfair.com | Admin@1234

What Is White Label Sports Betting Software?

Not a Sportsbook Skin

  • This is not a sportsbook with an exchange tab. Per-runner order books, price-time priority, partial fills, a validated ladder and cash-out with a hedging formula all work - and that engine is precisely why the category is expensive to build.

Not a Rental Platform

  • Handover, not access: the source, the Drizzle schema and the migrations, self-hosted on infrastructure you control. No per-seat fee, no dependency on our roadmap, standard PostgreSQL underneath.

What Does White Label Ownership Mean Here?

  • Peer-to-peer exchange with a live order book
  • Fixed-odds sportsbook with accumulators and cash-out
  • Casino catalog with provider game launch
  • Six currencies across fiat and cryptocurrency

Platform Features - Exchange, Sportsbook, Casino, Wallet & Back Office

Identity & Two-Factor

  • Registration captures country and currency, followed by email verification, password reset and optional TOTP two-factor, over a three-tier role model that middleware enforces on every admin route.
  • Country and currency chosen at registration
  • Email verification plus password reset
  • TOTP two-factor, enrolment through verification

Responsible Gambling

  • Deposit caps set daily, weekly and monthly; daily loss limits; session time limits; self-exclusion with an end date; and reality check reminders. These are the controls a licence application asks to see.
  • Deposit caps set daily, weekly and monthly
  • Daily loss caps alongside session time caps
  • Self-exclusion carrying an end date

Multi-Currency Wallet

  • Six currencies across fiat and crypto, each carrying total, available and reserved balances, so funds lock against open orders without ever leaving the customer balance.
  • Total, available and reserved held as three balances
  • Append-only ledger carrying balance-after snapshots
  • Conversion between wallets built in

Immutable Ledger

  • Each movement is an append-only entry carrying direction, amount, balance after, source reference and description, written inside an ACID transaction with row-level locking.
  • Stripe handles card deposits and withdrawals
  • Bank transfer and crypto rails need configuring
  • Saved methods stored as provider tokens only

Exchange Matching Engine

  • Per-runner order books with price-time priority, partial fills, a validated ladder from 1.01 to 1000, three persistence types, and commission taken on net winnings.
  • Hierarchy runs sport, competition, event, market, runner
  • Back and lay placed against the order book
  • Ladder validated across 1.01 to 1000

Cash-Out Engine

  • Quotes come live off current market odds through a position-hedging formula, with a platform margin applied, a ten second validity window, and execution as an opposing order.
  • Three persistence types governing market close
  • Position tracking carrying profit and loss
  • Cash-out quotes holding for ten seconds

Fixed-Odds Sportsbook

  • Pre-match and in-play pricing across single, accumulator and system bets, a full bet slip, cash-out on unsettled bets, and odds shown as decimal, fractional or American.
  • Fixed odds shown pre-match and in-play
  • Singles, accumulators and system bets
  • Bet slip offering cash-out on anything unsettled

Casino & Tournaments

  • Six game categories with provider and featured filters, launch through the provider API, session tracking, bonuses with wagering progress, and freeroll, buy-in and VIP tournaments across the tournament engine.
  • Catalog spans six game categories
  • Filter by provider or featured, with search
  • Games launch through the provider API

Promotions & Loyalty

  • Seven promotion types carrying opt-in and progress tracking, four loyalty tiers carrying points and a rewards catalog, plus free bets with restrictions, price boosts and cashback.
  • Seven promotion types carrying opt-in and progress
  • Four loyalty tiers on points, with a rewards catalog
  • Free bets restricted by market, sport and odds

Revenue Models - Commission, Margin, Casino Share & Affiliates

Revenue arrives from four directions at once here, and each is modelled as its own lever so an operator can tune one lever without disturbing the others.

Exchange Commission

  • A configurable percentage of net winnings, charged at settlement. The exchange never takes the other side, so this is revenue earned from matching two customers rather than from carrying risk.

Sportsbook Margin

  • Overround is built into fixed-odds pricing and configured per sport and per market type, with a validation tool checking each market against its band before it goes live.

Casino Revenue Share

  • Gross gaming revenue shared with game providers on whatever terms you negotiate, monetizing the customers that sports betting brought through the door.

Affiliate Acquisition

  • Four commission tiers across net loss, deposit and wager calculations turn marketing spend into a variable cost tied to what a customer is actually worth.

Free Bets as Acquisition

  • Free bets are issued by an admin or triggered by a promotion, carrying market, sport and minimum-odds restrictions, which keeps acquisition cost bounded and measurable.

White-Label Licensing

  • Branding, theme, currencies, margins and commission are configuration rather than code, so the same deployment can be licensed onward to another operator under their own identity.
  • Exchange commission and sportsbook margin carry most operators, because they monetize the same customer two different ways depending on which price is better at that moment, because they monetize the same customer in two different ways depending on which price is better at that moment.

Operator Console - Users, Settlement, Risk & Margins

A betting business is run from the back office, not the front end. Every admin route is protected at the router level by authentication and a role check, and every action lands in an audit log with the admin identity, the resource, a JSON payload of the change and an IP address.

KPI Dashboard

  • Total and active users, bet volume and revenue across 24 hours, 7 days and 30 days, plus pending KYC, pending withdrawals and deposit volumes - with the queries issued in parallel.

User Management

  • A searchable, filterable user list; a detail view carrying wallets and balances; status management; and a per-user activity log for support and investigation.

Transaction Oversight

  • Deposits and withdrawals filter by type, status and user, and carry provider references so they reconcile against the payment processor.

Market Settlement

  • Settle one market or batch settle a whole event, void a market and refund stakes, or reverse a settlement when a result is corrected after the fact.

Risk Desk

  • Exchange liability from unmatched lay orders sits next to sportsbook exposure from unsettled returns, with large bet and order flagging and velocity-based detection of suspicious accounts.

Margin Configuration

  • Overround minimum and maximum, odds range, maximum stake and commission percentage, all set per sport and market type, with a reset to defaults and a validation tool.

Reporting

  • Revenue by period, deposits by date range, user growth, and betting statistics per sport covering stakes, payouts and realized margin.

Audit Log

  • Admin actions are recorded with actor, action type, resource, JSON detail and IP address, filterable by action, user, resource type and date range.
  • Revenue reported daily, weekly and monthly
  • Deposits aggregated across a date range
  • Growth tracked by registration date

System & Sync

  • Health checks across every service, sports data sync triggering with provider health monitoring, live event seeding for demonstrations, and system settings management.
  • Audit log filters on action, user and resource
  • Health visible across every service
  • Sync control for sports data, with provider health

What an engagement can include

Delivery here is a handover, not access. You receive the application source, the schema behind it, and the documentation a technical buyer and a licence consultant will both ask for. Everything transfers with full ownership and is self-hosted on your own infrastructure.

Full Source Code

  • Three codebases transfer: the Next.js (version confirmed in writing) web application, the Expo React Native mobile app and the Node.js and Express backend, TypeScript throughout, yours to modify, rebrand and redeploy.
  • Web application on Next.js (version confirmed in writing), TypeScript throughout
  • Expo React Native covering iOS and Android
  • Backend on Node.js and Express, also TypeScript

35 Table Schema

  • PostgreSQL 16 under Drizzle ORM: 40 enums and around 60 indexes across 13 domains, with cascade rules on user-child tables and deliberately no cascade on financial records.
  • 35 PostgreSQL tables carrying 40 enums
  • Drizzle ORM giving type-safe queries and migrations
  • Roughly 60 B-tree indexes across the hot paths

Exchange Engine

  • In-memory per-runner order books, price-time priority matching, partial fills, three persistence types, position tracking, and a cash-out calculation with quote expiry.
  • Exchange engine keeping order books in memory
  • Matching on price-time priority, partial fills included
  • Ladder validated across 1.01 to 1000

Sportsbook & Casino

  • Fixed-odds pricing across single, accumulator and system bets with cash-out, alongside a casino catalog carrying provider launch, sessions, bonuses and tournaments.
  • Sportsbook covering singles, accumulators and system bets
  • Casino catalog carrying provider launch and sessions
  • Live and in-play carrying scores and match minute

Wallet & Ledger

  • Six currencies, three-balance accounting, an append-only ledger with balance snapshots, decimal.js money maths, and ACID mutations under row-level locking.
  • Wallet spanning all six currencies
  • Immutable ledger holding balance-after snapshots
  • decimal.js arithmetic, no float rounding anywhere

Real-Time Layer

  • A WebSocket hub riding Redis pub/sub carries odds updates, order status, match executions, balance changes and live scores on per-user and per-market channels.
  • WebSocket hub riding Redis pub/sub
  • Odds, order status, matches and balances all live
  • Score broadcasting with a heartbeat

Operator Console

  • Dashboard, users and KYC, transactions, settlement covering void and reverse, the risk desk, margin configuration, reporting, the audit log and system health.
  • Operator console covering settlement and risk
  • KYC review beside the audit log and reporting
  • Margin configuration, validation tool included

Technical Documentation

  • Entity relationship document and schema reference
  • Full API collection spanning 11 services
  • Developer, security and deployment handbooks
  • VAPT posture alongside the PRD and feature catalog

Who Is This White Label Betting Platform Built For?

This fits operators who want more than a sportsbook skin, and who understand that the exchange engine and the back office are what separate a real betting business from a front end.

Renting a betting platform means paying a licence fee forever to the company that holds your order book, your wallet and your compliance evidence. Owning it changes all three. If your business turns on customer deposits, on pricing risk correctly, or on proving to a regulator that your controls actually work, the platform stops being an operating expense and starts being an asset you can defend.

Use Cases - Exchange, Sportsbook, Casino & Crypto Betting

Which vertical leads changes with the operator; the codebase does not. An exchange-first brand leans on the matching engine and commission; a sportsbook-first brand leans on margin configuration and the risk desk. Each is configuration rather than a fork.

Customers set their own prices and the platform earns commission on net winnings, never taking a position on the outcome and the platform earns commission on net winnings without ever taking a position on the outcome.

Technology options we may propose

Behind the screen, three things have to hold: a matching engine fast enough to fill in milliseconds, a wallet that cannot lose money under concurrency, and a real-time layer that keeps every screen honest. Here is what sits behind the odds.

Next.js (version confirmed in writing) App Router TypeScript

How the Platform Works - Register, Fund, Bet, Match & Settle

From the outside this looks like odds and a bet slip. Underneath it is a tightly sequenced identity, funding, matching and settlement pipeline. Here is the path from registration to a settled market and a paid customer.

Customer Journey, From Signup to Settled Position

  • A customer signs up with country and currency, then proves who they are before the withdrawal limits open up. This is the gate a regulator inspects first.
  • Registration with country, currency and date of birth
  • Email verification and optional TOTP two-factor
  • KYC upload across passport, licence, ID and address

How we would approach the architecture

One Express server consolidates routing while 11 service packages carry the domain logic, so you can start on a single process and split the busy services out later.

Two Parallel Event Hierarchies

  • Exchange and sportsbook share sports and competitions but split at market level, because peer-to-peer matching and house pricing genuinely need different models.

Money Moves Inside Transactions

  • Every wallet mutation runs inside a database transaction with row-level locking and writes a ledger entry, so a crash mid-settlement cannot leave a balance wrong.

State Machines Everywhere

  • Events, markets, orders, transactions, KYC and bonuses each follow an explicit enum lifecycle, which is what makes settlement and reporting deterministic rather than best-effort.

Redis as the Nervous System

  • Rate limiting, FX caching, session state and the pub/sub behind the WebSocket hub all run through Redis, which keeps the API stateless where it matters.

Audit as a First-Class Table

  • Admin actions write to an audit log carrying actor, resource, JSON detail and IP, with a Redis-indexed service alongside it for fast filtered retrieval.

How we would design for scale

Matching Speed and Its Trade-Off

  • Holding order books in memory makes a fill sub-millisecond rather than a database round trip. That choice is what makes the exchange usable, and it is also the honest limit of the design.
  • Per-runner books ordered by price-time priority
  • Partial fills leaving the remainder resting on book
  • Sequential processing per market, parallel across markets

Financial Correctness Under Concurrency

  • Two customers hitting the same wallet in the same instant is what quietly corrupts betting platforms, so it is handled at the database rather than in application code.
  • Row-level locking on the wallet during mutation
  • Available balance checked before any debit
  • decimal.js arithmetic with no floating point rounding

Read Paths That Stay Cheap

  • Odds pages, bet history and the operator dashboard take the read load, so the schema is indexed for exactly those filters.
  • Around 60 B-tree indexes on foreign keys and status columns
  • Timestamp indexes for date-range reporting queries
  • Dashboard aggregates issued in parallel rather than in series

Real-Time Without a Broadcast Storm

  • A liquid market reprices constantly, and naive broadcasting is exactly how a WebSocket layer falls over.
  • Redis pub/sub between the engine and the socket hub
  • Per-market and per-user channels rather than global fan-out
  • Heartbeat detection to drop stale connections

Sub-Millisecond Matching

  • Keeping order books in memory takes the database round trip out of the fill path, which is what holds order placement inside the documented 100 millisecond target.

Stateless Everywhere Else

  • Auth, user, wallet, sportsbook, casino, payment, notification and admin all run stateless and scale out horizontally behind a load balancer.

Indexed for the Real Queries

  • Around 60 B-tree indexes cover foreign keys, status columns and timestamps - the three filters betting and reporting workloads actually hit.

Parallel Dashboard Aggregates

  • The operator dashboard fires its queries concurrently rather than one after another, which is what holds load time down as the data grows.

Documented Bottlenecks

  • Engine memory, order table write pressure and WebSocket broadcast volume are each named with a mitigation in the documentation, rather than discovered under load.

Security and privacy requirements we can design for

Money Cannot Silently Move

  • No balance moves silently. Every wallet mutation runs inside a transaction with row-level locking and writes an append-only ledger entry carrying a balance-after snapshot, so any balance can be reconstructed from first principles.

Precision Without Rounding

  • Monetary maths runs on decimal.js over numeric(18,8) columns: eight decimal places for crypto, exact arithmetic for fiat, and no floating point drift anywhere.

Session Security

  • A 15 minute access token against a 7 day refresh, one-time refresh use, reuse detection that revokes the entire chain, and hashed refresh storage in the database.
  • bcrypt at cost 12, an eight character minimum requiring uppercase, number and special character, and a lockout after five failed attempts for fifteen minutes.

Admin Accountability

  • Administrative actions write an audit row carrying actor, action type, resource, a JSON payload of the change and the originating IP, filterable by action, user, resource and date.

Player Protection

  • Deposit caps set daily, weekly and monthly, loss limits, session limits, self-exclusion with an end date and reality checks - enforced by the platform rather than merely displayed to the customer.
  • What is built is genuinely strong: bcrypt at cost 12, refresh token rotation with reuse detection, TOTP two-factor, ACID wallet mutations with row-level locking, an append-only ledger, and an audit log carrying the admin identity and IP address. Where the documentation rates something Moderate or Configuration Required, this page says so.

Add-Ons - Compliance, Providers, Monitoring & Enterprise

Licensing & Regulatory Support

  • The compliance tooling a licence application expects is already here. Obtaining the licence itself, and adding whatever jurisdiction-specific controls your regulator asks for, is scoped work alongside your own legal advisors.

Sports Data Feed

  • Fixtures, live scores and results arrive from an external provider. The sync management and provider health screens exist; the feed subscription is yours to arrange.

Extended Table Migration

  • Core tables are migrated already. Notifications, promotions, loyalty, affiliates and tournaments sit in the schema and want a second migration snapshot before production.

Search & Export

  • Search is pattern matching rather than a full-text index, and reporting is API-first with no CSV or JSON export. Both are contained pieces of work once volume justifies them.

Industries We Serve

Any operator selling regulated wagering or gaming is running the same shape of business underneath. Startup operators launch a first brand with all three verticals live from day one. Established sportsbooks bolt on peer-to-peer exchange trading to compete on price rather than on marketing spend. Crypto and gaming companies enter betting with Bitcoin, Ethereum and USDT running alongside fiat. Emerging-market brands go mobile-first with native apps and local payment rails. Multi-country groups run several licensed brands on one consistent compliance posture. Media owners monetize an existing sports audience with a branded product and affiliate tracking. Casino-led operators cross-sell into sports betting from a player base they already hold. Fantasy and skill-gaming businesses reuse the exchange model for peer-to-peer contests. For the wider sector view, see our betting and gaming platform development page. For custom work beyond this product, see our custom software development service.

Everything here is exchange-first, because the order book is the hard part and every other vertical attaches to it. Any wagering model can sit on top, self-hosted on your infrastructure and branded entirely as yours. The gambling licence for your market remains yours to obtain we build the software, not the permission to operate it.

Typical scoping questions

Is the betting exchange real, or just a sportsbook?

  • Real. There are per-runner order books with price-time priority matching, partial fills where the remainder rests on the book, a validated price ladder from 1.01 to 1000, three persistence types governing behaviour at market close, position tracking with profit and loss, and cash-out calculated from live market odds with a ten second quote validity. The platform earns commission on net winnings and never takes the other side of the bet.

Why run an exchange and a sportsbook together?

  • Liquidity, and nothing else. A pure exchange cannot function until enough customers are trading against each other, which is a slow and unforgiving start for a new brand. Fixed odds running alongside guarantees a price on screen from day one while the exchange builds depth. Both share the same customer account and wallet, so nothing gets duplicated.

What exactly gets rebranded?

  • Everything a customer or a regulator can see. The domain, the logo and colour system across the betting surface, the casino lobby and the operator console; the app name, icon, splash screen and store listing; the bet slip, the cashier and the account statements; the sender name and templates on transactional email; the terms, privacy and responsible-gambling pages, which point at your licensed entity rather than ours; and the descriptor that appears on a customer s card statement. Inside the codebase, package identifiers and bundle IDs are set to your namespace before the apps are compiled. What does not change is the engineering underneath the order book, the settlement engine, the wallet ledger and the KYC pipeline because that is the part you are actually buying.

How is customer money protected from software error?

  • Every wallet mutation runs inside a database transaction with row-level locking, checks available balance before any debit, and writes an append-only ledger entry recording direction, amount, balance after the movement, the source reference and a description. Monetary arithmetic runs on decimal.js over numeric(18,8) columns, so there is no floating point rounding anywhere. Any balance can be reconstructed from the ledger alone.

Can the exchange handle real volume?

  • Order books live in memory, which is what delivers the documented sub-100 millisecond order placement at the 95th percentile. The same choice means the engine scales vertically rather than horizontally, and it is the one component carrying that limit every other service is stateless and scales out behind a load balancer. The documentation names engine memory, order table write pressure and WebSocket broadcast volume as the three bottlenecks, each with a stated mitigation.

Do I get the source code?

  • Yes, in full: the Next.js (version confirmed in writing) web application, the Expo React Native covering iOS and Android, the Node.js and Express backend across 11 service packages, the PostgreSQL schema with its 35 tables and Drizzle migrations, and the seed script. Ownership transfers with them modify, rebrand and extend and the platform is self-hosted on your own infrastructure.

Describe your Sports betting software

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com

More pages on this build

4 pages describing this proposed build.