Turnkeyxgaming

Comparison

Casino API vs white label casino

This casino API comparison is about how much of the business you want to own. An API gives you content for a platform you already run. A white label gives you a running casino on someone else's platform.

Casino API

Content for your own platform

vs

White label

A branded casino on a shared platform

Side by side

Casino API (aggregator only)White label
You needYour own platform with a walletA brand, marketing and usually a licence
ControlFull control of product and dataLimited to theme, content and promotions
Time to launch24–72h of engineering once your wallet is readyFast, as the platform already runs
Cost modelGGR share on gamesPlatform fees plus a GGR share
Lock-inLower: the ledger stays yours, but switching aggregator is still a second integrationHigher: the platform holds the accounts, the stack and often the round history

White label vs aggregator-only: how to decide

Choose aggregator-only if you have, or are building, a platform and want control over product and data. Choose a white label if speed and low upfront cost matter more than control, and if the licensing model works in your markets. Shared-licence white labels are not accepted everywhere: several stricter European regimes expect the operating company to hold its own licence, so check the model market by market rather than treating it as a European default.

There is also a middle path: a turnkey casino, with a dedicated platform configured for you. The turnkey vs white label comparison covers it.

What you still operate after either choice

An API contract does not hand you a cashier, a KYC flow or a bonus engine. You already have them, or you are building them, and the games call the wallet you expose. A white label moves that stack onto a platform someone else runs. You still bring the brand, the marketing and, in markets that will not accept a shared licence, the licence itself. The speed you gain is the speed of a platform that is already up, not the disappearance of player-account work.

Lock-in follows the data. On an API, player records and the ledger stay in your platform, so changing aggregator is a second integration rather than a move of the database. On a white label, export terms decide whether you can leave with accounts, open bets and the history players will ask for. Read those terms before you treat a fast launch as reversible. A shared-licence model that cannot be used in the markets you actually want is not a cheaper version of the same product. It is a product those markets will not take.

Do not buy a platform to avoid a wallet

If the only gap is games, an API on the wallet you have is the smaller project. A white label solves a missing platform. Using it to dodge a callback you have not designed yet moves the player record onto someone else's stack, which is a larger decision than the callback was.

Which operator should take which route

Five profiles cover most of the calls we see. The last column is the work that has to happen before either signature, whichever route is chosen.

Your situationCasino APIWhite labelClear before signing
New brand with a platform in stagingFits: launch on the wallet you are already buildingSpends money on a platform you are about to finishA test account that can complete a spin, a refund and a failed debit
Group with a back office, adding a second licenceOften cheaper for a second brand, once the platform is already paid forOnly if the second brand must look like a separate companyPlayer records separable per licence, not by skin colour
Sportsbook that wants casino tilesFits: the wallet already reserves and settlesAdds a second account system beside the one you runWhere casino stake sits in the ledger you settle sport on
Small team with no compliance officerTechnically easy, operationally notNot a substitute for the licence holder's dutiesA named person who owns limits, AML and the regulator's questions
Marketing-led brand with no engineersNoFits, where the shared-licence model is accepted in your marketsThe export clause, read before the theme options
Market test budgeted for under a yearOverbuild unless the platform already existsReasonable, if priced with the exitWhat the export costs, how long it takes and who runs it

An illustrative first-year cost comparison

Assumptions, all replaceable: EUR 2,000,000 annual casino GGR, a 16% content rate, 150 engineering hours at EUR 55, and a white-label platform fee planning figure of EUR 12,000 a month plus 10% of GGR. No supplier quote is implied.

Cost lineCasino API routeWhite-label routeWhat the number depends on
Content or platform share16% of GGR = EUR 320,00010% of GGR = EUR 200,000Your negotiated rate and the GGR definition
Fixed platform feeEUR 0 in this exampleEUR 144,000 a yearYour quote, contract length and included brands
Wallet engineering150 hours = EUR 8,250, plus ongoing ownershipIncluded in the platform in this exampleWhether your team already has a wallet
Front end and account systemYour existing platform (not costed here)Included in the platformWhat you already operate
Exit or migrationA second aggregator integrationExport and rebuild, scope unknown until the contract is readThe export clause and the data you can take
Illustrative first-year totalEUR 328,250 plus your platformEUR 344,000 plus brand and marketingReplace every line with your own quotes

What the wrong route costs in the second year

A content contract signed before the wallet is ready does not begin a 24–72h integration. It begins a project to build debit, credit and rollback, and the catalogue sits idle until a test account can spin and be refunded. As an illustrative planning assumption, not a measured average, budget a week of content configuration and a quarter of wallet engineering for a team building its first wallet; the gap that opens between those two dates is what a board later hears described as supplier delay.

Put the two routes on one page with your own quotes before either signature. The worked example below uses round planning figures so the arithmetic is visible; replace them with the numbers in your quotes.

The white-label error runs the other way. A shared platform is fast because the account, cashier and bonus engine already exist, and that is also why leaving is slow. Put four things in writing before you pay: the export format for accounts, balances, bonus state and unfinished rounds; the notice period; whether the export is included or invoiced; and whether old game rounds stay queryable once the contract ends. A supplier who cannot describe the file has not offered an exit, only a launch.

FAQ

Questions operators ask

Can a white label keep our existing player database?

Only if that platform has an import you have tested, including balances, limits and open bonuses. Many white labels expect players to register again. An API leaves the database where it already is.

Who runs responsible-gambling limits on a white label?

The platform has to enforce them, and your licence still makes them your obligation. Ask which limits exist, which products they cover, and what you can evidence. Do not assume the theme settings include them.

If we outgrow a white label, what has to be rebuilt?

Anything the platform owned: account, cashier, bonus rules and the game launch, unless the export and the contract let you keep them. Teams that might outgrow the shared stack should cost that rebuild before they start, not after the brand has traffic.

Which route asks more of our engineering team after launch?

The API leaves you the wallet, the launch call and the reconciliation, plus every release on your own platform. The scope is yours and it does not stop. A white label moves releases to the platform and leaves you configuration, brand assets and the reports you pull out of it. Neither is zero work, and the difference is who is on call at two in the morning.

If we start on a casino API, can we move to a white label later without losing players?

Only if the shared platform can import accounts you export. Ask for the import field list before either contract, and test it with a player holding an open bonus and an unfinished round. Moving from shared platform to your own stack is the harder direction, because the round history sits with whoever operated the platform.

References

Sources and further reading

Primary regulator, standards or studio documentation behind the technical and regulatory points on this page. External links open in a new tab. Links checked 2026-11-15.

Keep reading

Related pages

  • Product · Casino APICasino APIThe casino API is one contract — a catalogue, a launch call and wallet callbacks — built once and reused for every studio we connect.Read
  • Solution · White labelWhite labelYour brand on shared casino infrastructure, with aggregated games, an optional sportsbook and a shorter, licence-dependent path to launch.Read
  • ComparisonTurnkey vs APIA turnkey project supplies the platform. A casino API supplies the games for a platform you already operate and control.Read
  • ComparisonTurnkey vs white labelA turnkey casino is your own installation. A white label is your brand on infrastructure shared with other operator brands.Read

Get a written quote and sandbox access

Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.

Telegram @turnkeyxhub WhatsApp Email Contact form