Two buyers use this path. A Web3 or crypto founder who does not yet have a player account system, and needs a lobby, a wallet model and a lawful first market. And an operator that already runs a sportsbook or PAM, and wants a white label casino on the same player ID without rebuilding accounts. If the piece does not help one of those decisions, it is the wrong brief.
What does the operator need before any lobby goes live?
The casino is the visible layer. The launch fails on the layer underneath it. Before templates and game tiles, the operator needs a market, a licence path for that market and period, a brand, a payments route, and a player account model. Sirplay’s FAQ states that a configured white-label stack can go live in about 10 working days after assets and market scope are clear, and that licensing in the target country sits with the operator. Read both lines. Configuration time is not a licence.
Assets means more than a logo. Languages, currencies, domain, cashier rules, responsible-gambling limits and the list of studios you are allowed to switch on in that market. A lobby that shows a game the local licence does not cover is a compliance problem, not a content win. Sirplay’s casino pages describe custom lobbies and catalog control so availability can be tailored to the market. That control is only useful if someone on the operator side owns the list.
Payments sit with the operator or its payment partners. Sirplay’s platform terms say player funds, wallets and payment-institution duties are not the website’s. Fiat, vouchers and crypto can all appear in a product scope. None of them moves the duty. A crypto casino, in Sirplay’s wording, accepts coins into a custodial wallet. A Web3 casino may connect an external wallet. Wallet type is a product choice. It is not a regulatory status.
White label, turnkey or iframe: which casino path fits?
Sirplay’s split is the same for casino as for sportsbook. Turnkey is a full site. White label is the branded package you operate. An iframe drops the casino into an existing PAM without a rebuild. An API is the fourth path, when the lobby and the pages must live on the operator’s templates.
A founder without a PAM is not buying an embed. The founder is buying a white label casino solution or a turnkey site: domain, brand, lobby, slots, live casino and a wallet. An operator that already has accounts, KYC files and a sportsbook should start from iframe or API. Replacing the PAM to match a new storefront is a migration, not a casino launch.
Live casino can use the same paths. Sirplay’s live casino notes describe provider activation, lobby games such as roulette, baccarat and blackjack, reporting, player management and API or managed integration. Some of that content is also described as available for land-based casinos. Treat studio hours, table limits and stream quality as demo items. Do not treat a lobby menu as proof the table is certified for your market.
Does the software choice decide the licence?
No. Online casino software, a white label skin, an iframe and an API are delivery shapes. Sirplay’s terms put gambling, payment and corporate licences in each target market on the operator, with geo-blocking, age-gating and responsible-gambling configuration. The homepage FAQ repeats the point: licensing in the target country sits with the operator.
In Great Britain, the Gambling Commission’s page on third-party responsibilities, updated 8 November 2024, says compliance of operating websites, including white-label sites, sits with the licence holder and cannot be transferred. A brand partner cannot offer gambling facilities unless it holds a relevant licence. That is a British position for that period. It is not a world rule. Highly supervised markets typically want the local operator approved. A supplier licence elsewhere does not open them. This article is not legal advice. Confirm market and date with counsel before a term sheet.
Optional No-KYC modules are a product capability on Sirplay’s terms. They are not an instruction to bypass AML where the operator’s regulator requires checks. Marketing and consumer-facing terms also stay with the operator.
What should the casino scope include?
A white label casino is a catalogue and a lobby, not a single game. Sirplay describes slots and live casino from providers, custom lobbies and real-time catalog management. The operator decides which tiles are on for which market, and whether players can save favourites. Studio commercial terms, aggregation and content certification are separate from the platform fee. Ask for them in the schedule.
Sportsbook and add-ons are optional, not automatic. A bookmaker adding casino keeps one player ID across sportsbook, casino and live casino, or bonus and limits fragment. Virtual games, e-sports and poker are further modules. Sirplay’s additional-services pages present them as items to check for availability and activation, not as a default bundle. Poker is often a network, not a table the operator liquidity-seeds alone. Virtuals extend a schedule. They are not a substitute for a casino licence.
Reporting is part of the scope. Live casino materials list history, game visualisation, player management and affiliate tools. Use the demo to see the reports the board will actually open: game performance, failed rounds, bonus cost, and the limit breaches responsible-gambling rules care about. No report guarantees revenue.
How the launch choices compare
Six rows are enough. Vendor price blogs are not in the table. They are not your contract.
| Choice | What you take | Who already has a PAM | Watch-out |
|---|---|---|---|
| White label casino | Branded lobby, slots, live casino, catalog tools | No PAM required | Player-data exit must be in the contract |
| Turnkey site | Full site around that package | No | Still not a licence |
| Iframe | Casino dropped into the current account system | Yes | One player ID with sportsbook and wallet |
| API | Casino engines on your own front end | Yes, plus engineering | Longer path than a frame |
| Crypto or Web3 wallet | Custodial coins or an external wallet | Either | Does not replace AML or the gambling licence |
What Sirplay does, and what the operator must do
This split follows Sirplay’s published platform terms. Sirplay supplies sportsbook, casino, Web3 and crypto modules, optional No-KYC capabilities, integration and related B2B services. It does not accept player bets and it does not operate a consumer brand on sirplay.com. Platform IP stays with Sirplay, except brand assets the client supplies. The homepage describes a white label casino with live casino, provider integration and management tools, and launch support on the provider side. Live casino pages add reporting, configurations and an independent-lab claim on gaming math. Ask for the certificate scope and date if a regulator will ask.
The operator holds and maintains gambling, payment and corporate licences in each target market. The operator configures geo-blocking, age-gating and responsible gambling. KYC and AML sit with the operator where that regulator requires them. Marketing and consumer terms sit with the operator. Player funds, wallets and payment-institution duties sit with the operator or its payment partners. A No-KYC module does not move those duties. “You own the brand and the players” is a Sirplay FAQ line. Write ownership, export format and notice into the schedule.
Ignore any line that promises risk-free launch, guaranteed GGR, or the widest catalogue as a fact. Studio range depends on contracts and on the market. A configured stack in about 10 working days is a Sirplay window after assets and market scope are clear. Licensing, payments and content approvals can sit outside it.
What to put in the demo
Sirplay’s demo page is a request, not a booked slot. The team contacts the operator to agree date, time and scope. Use it on the casino you will actually open.
- Name the path: white label, turnkey site, iframe or API.
- Name the first market and who will hold the licence there.
- If a PAM or sportsbook exists, show the player ID, wallet events and limits the casino must share.
- List lobby scope: slots, live casino tables, languages, currencies, and any sportsbook, virtuals, e-sports or poker module.
- Ask which studios and tables are in production for that market, and which certificate covers the math.
- Ask what the ten-working-day window includes, and what the data exit looks like.
A sportsbook demo is not a casino demo. If both products are in the plan, say so. Casino catalog rules and live-table limits are not visible from an odds screen.
Questions that change the build
Can an existing bookmaker add only the casino?
Yes, if the contract allows an iframe or API into the current PAM. Identity, wallet and responsible-gambling limits still have to match the sportsbook. A second login is a failed integration.
Is a crypto casino the same as a Web3 casino?
Not in Sirplay’s FAQ. A crypto casino accepts coins into a custodial wallet. A Web3 setup may connect wallets such as those the operator chooses to support. Neither removes the licence or the AML duty.
Does live casino need its own licence?
It needs to be covered by the licence you hold for that market and period. A live table in the lobby is not evidence that it is. Confirm product scope with the regulator’s categories, not with the menu.
Who answers if marketing breaks a rule?
In Great Britain, the licence holder. Other markets need their own reading. Contracts may push cost to the brand partner. The regulator’s counterpart remains the licensee.
Configure the casino path against your first market and your PAM, then request a demo scoped to that lobby: Demo Requests.
