Choosing a White Label Sportsbook Provider: Whose Licence, Whose Code
Every seller of a white label sportsbook shows you the same odds screen. What differs is who holds the gambling licence, who owns the source and the wallet, and what you keep if the relationship ends. Many turnkey offers run the operation under the provider's own licence and take a revenue share. Owning the software and holding your own licence is a separate arrangement. This page sets the routes side by side and lists the questions to put to each seller, including us.
Talk to Our Team →See the DeploymentRented Platform vs Script Vendor vs Custom Agency vs Miracuves
Four kinds of seller answer the same search. The gaps between them show up in the contract, not on the pricing page.
| Criteria | Rented or hosted platform | Script vendor | Custom agency | Miracuves |
|---|---|---|---|---|
| Whose licence the bets run under | Many turnkey offers trade under the provider's own licence | Yours to obtain | Yours to obtain | Yours to obtain. We supply software, never a licence |
| How you pay | Typically a revenue share on the provider's terms | One-time, roughly $250 to $1,500 | Six figures and up | $3,999 one-time, no revenue share to us |
| Source code | Usually stays with the provider | Some vendors withhold it from every published tier | Usually yours once paid in full | Yours in full, self-hosted |
| Who holds the wallet and player data | Typically the provider's systems | Whichever server you install it on | Yours | Your database, on infrastructure you control |
| Peer-to-peer exchange | Varies, so ask to see a partial fill | Often just an odds display and a feed | Possible, though usually the line that stretches the budget | Real order books, price-time priority, partial fills |
| Time to launch | Set by the provider's onboarding | Depends on how much you finish yourself | 6 - 9+ months | 6 days on our side |
| If the relationship ends | Read the exit terms, because the operation may stay with the provider | Little changes beyond support | Depends on the contract | Nothing to unwind. The code and data are already yours |
The central contrast is licence and ownership. Under a turnkey deal you trade on the provider's permission and share revenue with them. Here you hold your own licence and own the platform underneath the sportsbook clones outright. Neither arrangement is wrong, but they are not the same product. Whichever seller you pick, read the Platform Trust section below for the limits we state ourselves.
Questions Worth Asking Any Provider
Put these to every bidder in the same order and compare how the answers are worded. The vague ones are the answers.
Whose licence do the bets run under?
If the answer is the provider's, you are a brand on their operation, and their terms set your margin and your exit. If it is yours, ask exactly what they will and will not help with.
What do I pay after launch, and for how long?
A revenue share needs written terms: what it is charged on, whether it ever ends and what changes if you leave. A seller who will not put it in writing has answered already.
Who owns the source and the database?
Ask for the repository and the player records by name. A licence to use software is not ownership, and the difference shows the first time you want to change the cashier.
What happens if we stop working together?
Get the answer for the site, the player list and the wallet balances. On a platform you own and host, the answer is that you carry on. On a rented one, check before you sign.
Is the exchange a real order book?
Ask to watch two customers matched against each other, a partial fill and the remainder resting on the book. If all they can show is fixed odds, there is no exchange.
How is money stored, and can a balance be rebuilt?
Ask for the column type and for a balance derived from the ledger alone. Ours is numeric(18,8) with decimal.js, and each wallet change writes an append-only entry.
Who can void or reverse a market?
It should be a console action with a recorded actor and IP address, never a database update. Ask to see the audit entry it leaves behind.
What is unfinished, and what needs my own accounts?
Every platform has gaps and depends on outside contracts. Ask for both lists in writing. Ours names the data feed, casino providers, payments and notification accounts.
The Six-Step Delivery Process
What happens after you say yes, in order.
Scope and licence check
We agree which verticals and currencies you launch with and where your licence application stands. If it is not moving, we say so before you pay. Your licence, payment accounts, data feed and game contracts all start now, because they set the calendar.
Brand everything
Your name, logo and colors go across the customer web app, the iOS and Android apps and the operator console. The app names and store listings carry no supplier name.
Deploy to your infrastructure
The platform is installed on servers you control. Your Stripe account, sports data feed and any casino provider credentials are connected and tested from end to end.
Margins and risk desk
Overround is set per sport and market type and checked with the validation tool. The risk desk is shown exposure and large-bet flagging before any live wager exists.
Compliance walkthrough
The KYC queue, deposit and loss limits, session limits, self-exclusion and reality checks are shown to whoever will face your regulator. The audit log and ledger reconstruction are demonstrated too.
Source handover and support
The code, schema, migrations and documentation pass to you with full ownership. Technical support carries on after go-live, and you can take the source to any other team without asking us.
The deployment described below took seven weeks from brief to go-live. Six of those days were ours. The remainder went on licensing, payment approvals and provider contracts, which is how most betting launches actually run.
Red Flags That Mean Walk Away
What a Sportsbook Platform Has to Get Right
Six problems that never show up in a demo and hurt badly in production. Ask each seller how they cover every one.
| Area | How this platform covers it | What goes wrong otherwise |
|---|---|---|
| Moving money | Each wallet change sits inside a database transaction with row-level locking. Available balance is checked before a debit, and a ledger entry with balance-after is appended. | Two settlements landing together can credit a customer twice, and nobody notices until reconciliation. |
| Precision | numeric(18,8) columns and decimal.js maths, with fiat and crypto handled the same way. | Rounding errors on small crypto stakes leak value in fractions that testing never reveals. |
| A genuine exchange | Price-time priority, a validated ladder from 1.01 to 1000, partial fills that rest on the book and three persistence types at market close. | A counterfeit exchange collapses the first time a customer tests it. |
| Seeing exposure | The risk desk shows exchange liability and sportsbook exposure ahead of settlement, with large bets flagged. | A desk that reads yesterday's numbers is doing accounting, not risk management. |
| Reconstructing events | An audit log with admin identity and IP address, and voids and reversals run as console actions. | "Someone voided that market" is not an answer an auditor accepts. |
| Protecting players | Deposit, loss and session limits, self-exclusion with an end date and reality check reminders, enforced by the platform. | Controls bolted on after launch are harder to add than controls present from the start. |
Licence, Money and Player Protection: Where We Stand
Three questions matter most on a betting platform. Can money vanish, can an admin deny an action, and can an auditor rebuild what happened? The answers sit in the data model and not in a policy document.
The licence is yours, always
We supply software, never permission to operate. Obtaining and holding a licence in each market you accept customers from is your responsibility, along with age verification, responsible-gambling provision and local advertising limits. We do not advise on any of it, and any seller who says a licence comes bundled with the code is misleading you.
No silent balance changes
Wallet mutations run in a transaction under row-level locking, check available balance before a debit and append a ledger entry with direction, amount, balance after, source reference and description.
Exact decimal maths
Every amount is calculated with decimal.js over numeric(18,8) columns, so fiat and crypto share one precision and any balance can be rebuilt from the ledger.
Reviews with a name attached
Passport, licence, national ID and proof of address can be uploaded. An admin approves or rejects with a reason, status moves from pending to verified or rejected, and the reviewer's identity is stored for the compliance trail.
Limits that are enforced
Deposit caps by day, week and month, daily loss limits, session time limits, self-exclusion with an end date and reality check reminders on an interval you set. These are the controls an application usually asks to see, not a promise that any regulator will accept them.
Mapped to the OWASP Top 10
A dedicated compliance document maps the security posture: bcrypt at cost 12, 15-minute access tokens with 7-day refresh rotation and reuse detection, TOTP two-factor, login lockout, three-tier roles on every admin route and an audit log with admin identity and IP address.
Where that document rates an item Moderate or Configuration Required, we say so here. Input validation is Moderate because it is inline rather than schema-driven. A WAF, secrets management and monitoring are deployment hardening, and the data feed, casino games, payments and notification accounts are yours to arrange.
One Live Deployment, Described Within Its NDA
A licensed operator took this platform to market under its own licence. The client cleared the details below for publication, and we add nothing beyond them.
Exchange & Sportsbook Operator
A regional betting brand launched on this platform under its own licence, running a peer-to-peer exchange, fixed-odds sportsbook and casino from one wallet and one back office. Client identity withheld under NDA.
Challenges
- Running an exchange and a sportsbook from a single customer wallet
- KYC review and responsible gambling controls ready for the licence application
- Settlement, voiding and reversal handled in the back office rather than in the database
Goal
- Launch a multi-vertical betting brand without building a matching engine from zero
- Give the risk desk exposure monitoring and margin control on day one
- Earn from exchange commission, sportsbook margin and casino share at once
Solution by Miracuves
- In-memory order book with price-time priority matching
- Exchange commission, sportsbook overround and casino revenue share
- Six currencies across fiat and crypto
- Cash-out, accumulators, loyalty tiers and affiliate tools
- Node.js services with PostgreSQL, Redis and WebSocket
"The exchange is the part nobody else would quote us a sensible number for. Having it working on day one changed the whole plan."
Because of the NDA there is no client name, brand URL or app listing to link to. The operator held its own licence, which is the arrangement this page is about, and the software was the part we supplied.
Frequently Asked Questions
What separates a turnkey provider from owning the software?
Do I need a gambling licence to run this?
Can you show me a client I can actually contact?
How is customer money protected from software error?
What happens after the six days?
What if I need something the base build does not do?
Take the checklist to every seller
Start with whose licence the bets run under. We would rather answer these questions now than after you buy.
Explore White Label Sports Betting Software
Choose on the answers, not the demo reel
Six days to deploy, the source in your hands and the unfinished list in writing before you pay. The licence stays yours to obtain.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Bet365 or any other betting operator.
“White label sports betting software” describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.
We supply software, not permission to operate. Obtaining and holding a gambling licence in every market you accept customers from is your responsibility, as is age verification, responsible-gambling provision and any local advertising restriction. We do not advise on any of it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from any third-party betting website or application. All third-party names and marks belong to their respective owners.
