Operator guide

White-Label vs Custom Casino: Which Should You Build?

12 min readBy

Once you decide to launch an online casino, the single biggest decision is the build model: white-label, turnkey, or custom. It sets your cost, your speed, how much you control, and — crucially — how much of the business you actually own. Get it right and you launch fast without boxing yourself in. Get it wrong and you either overspend on day one or hit a ceiling six months later.

Here's the honest comparison. The table below is the quick version. The full head-to-head matrix further down has the detail. Either way, choose for where you want to be in 12–24 months, not only for the cheapest launch.

The three models at a glance

ModelYou ownSpeedCostControl
White-labelThe brand onlyWeeksLowestLowest
TurnkeyBrand + license + platformWeeks to monthsMediumHigh
CustomEverything, built to specMonthsHighestHighest

White-label: rent the whole operation

With a white-label casino you operate under someone else's license and platform. They handle the license, the games integration, the payments and compliance; you bring the brand and the marketing.

Best for: testing a market or a brand idea quickly and cheaply, or affiliates moving into operating for the first time.

The trade-offs:

  • You're a tenant, not an owner — limited control over design, payments and features.
  • You share revenue, often significantly.
  • You may not fully control your player data, which is the asset that matters most long-term.
  • Migrating off later means moving players and money — painful once you have scale.

There's also a quieter risk. The provider's relationship with its regulator becomes your business risk: if their license is suspended, your site goes down with it. The licensing, data and contract sections below cover this in detail.

White-label is a fast, low-risk entry point. It is rarely where a serious operator stays.

Turnkey: own the business, skip the plumbing

A turnkey casino gives you your own license path and a fully set-up platform — games and aggregation, cashier, KYC, back office — configured and handed to you. You own the brand, the license, and the player relationship; you just don't build every integration yourself.

Best for: operators who want to run a real, ownable business without becoming a systems integrator. For most people this is the sweet spot.

Because you're the licensee, compliance accountability sits with you. Even if the provider runs the platform, you need at least one compliance owner in-house.

The trade-offs: more upfront cost than white-label and a slightly longer setup — but you keep the upside and control.

Custom: build exactly what you imagine

A custom build designs the platform around your brand and roadmap from the ground up. This is what you choose when you have a differentiated product — in-house originals, prediction markets, a Telegram-native casino, or requirements a shared platform can't meet.

Best for: funded teams with scale and a genuine product edge.

The trade-offs: the largest investment and several months to build. Only worth it when you're building something the market doesn't already sell. It also raises the technical bar (certification, payment security, build vs buy), which we cover further down.

The hybrid path: turnkey core, custom layers

You don't have to pick a pure model. Many operators land in the middle: a turnkey platform underneath, with custom work on top.

Custom front-end on a turnkey core

The wallet, game aggregation, KYC and back office stay on the turnkey platform. You build a fully custom-branded front-end and player journey. Players see a distinct product, and you never rebuild a cashier.

Start turnkey, add custom modules later

Launch on turnkey, prove demand, then add custom modules where they earn their keep: proprietary games, a loyalty system, or a Telegram or crypto-native front-end.

Why it works: you use proven, already-integrated infrastructure where differentiation doesn't matter, and spend custom budget only where it does. What to check: how much API access you get to the core platform, and who owns the IP in the custom layers you pay for.

Head-to-head: white-label vs turnkey vs custom

Costs and timelines here are relative tiers, not market figures.

FactorWhite-labelTurnkeyCustom
License holderProviderYouYou
Player data and databaseOften the provider; depends on contractYouYou
Commercial modelRevenue share, often plus minimum feesMainly fixed platform feesBuild cost plus your own running costs
Upfront costLowestMediumHighest
Ongoing costGrows with GGRMostly fixed and predictableHighest (team, hosting, maintenance)
Time to launchFastestMediumSlowest
Game providers and aggregatorsProvider's catalogueWide choice, pre-integratedAnything you integrate
Payment and crypto methodsProvider's cashierConfigurableAnything you build or integrate
Branding and UXSkin or theme levelStrong, within the platformUnlimited
Back office and CRM accessLimitedFullFull, built to spec
Compliance and AML/KYCMostly provider, but your brand carries the riskYou, with platform toolingYou, end to end
Regulated marketsLimited to the provider's license coverageYes, with the right licenseYes, with license and certification
Exit and migration difficultyHardModerateLowest — you own it
Best fitAffiliates, market testersMost operators who want to ownFunded teams with a product edge

Red flags in a white-label contract

  • No data-export clause, or no clarity on who controls player data
  • The provider owns the domain or the brand assets
  • Payment or game providers you're not allowed to change
  • Revenue share on GGR with undefined deductions, or on NGR with open-ended ones
  • A long lock-in with heavy exit penalties
  • No SLA or uptime commitment
  • Vague wording about which markets the provider's license actually covers

Licensing reality: whose license are you running on?

White-label: borrowed license, borrowed risk

Under white-label, the provider's standing with its regulator is your risk, and so is any enforcement action against it. Regulators do act. The Malta Gaming Authority publishes its enforcement actions under the Gaming Act (Cap. 583), including suspensions of authorisations. The structure can also change: if a jurisdiction reforms how it licenses operators, a setup built on someone else's license may need restructuring. With turnkey and custom, you hold your own license or are directly accountable under one.

Regulated markets: UK, Malta, Ontario

  • UK: the Gambling Commission sets out which licence types a business may need, what they cost, and the licence conditions and codes of practice that apply. Serving Great Britain means working inside that framework.
  • Ontario: operators must take steps with both iGaming Ontario and the AGCO. Under Ontario's framework, igaming operators can only operate sites once they have entered into an operating agreement with iGaming Ontario and been registered by the AGCO. Some suppliers must also register with the AGCO and have their technology certified by a registered independent testing laboratory.
  • Malta: the MGA licenses operators directly and keeps a public register.

In short, tightly regulated markets expect the operator to be properly licensed and accountable. Confirm your route with the regulator and with licensing counsel. This article is not legal advice. For the bigger picture, see casino licensing explained.

How to verify a provider's license

Don't take a provider's word for it. The MGA register can be searched by licensee name, authorisation status, URL or Gaming Service. Check that the entity named in your contract matches the one on the register.

Who owns the players? Data, GDPR and your core asset

The player database (accounts, deposit history, KYC records, marketing consents) is where the business's long-term value sits. Under GDPR, if you process the personal data of people in the EU or offer them services, the regulation applies to you even if you're outside the EU. Fines max out at €20 million or 4% of global revenue, whichever is higher.

Controller or processor: get it in writing

GDPR defines a data processor as a third party that processes personal data on behalf of a data controller. Your contract should say explicitly whether you or the provider is the controller of player data. GDPR also gives data subjects a range of privacy rights, and you need both the contractual and the technical ability to honour them. For custom builds, data protection "by design and by default" (Article 25) means building it into the product from the start.

Questions to ask about player data

  • Who is the controller, and who is the processor?
  • What export format and frequency do you get?
  • Can marketing consents move with the data?
  • What happens to the data when the contract ends?

Total cost over time: why cheap can become expensive

White-label with a revenue share is the cheapest model upfront. It can become the most expensive once GGR grows, because the provider's cut grows with you and fixed platform fees don't.

Revenue share vs fixed fees: a simple break-even

Illustrative example only, not market data. Say a white-label provider takes 25% of monthly GGR. A turnkey platform costs a fixed €15,000 a month, plus €10,000 a month of your own license and compliance overhead, so €25,000 in total. Break-even is where 25% of GGR equals €25,000, which happens at €100,000 GGR a month. Below that, the revenue share is cheaper. Above it, every extra euro makes white-label more expensive: at €300,000 GGR the share is €75,000 against €25,000 fixed. Swap in the numbers from your own quotes.

Hidden and ongoing costs in each model

Whatever the model, budget for setup fees, minimum monthly fees, game-provider fees and GGR-based royalties, payment processing, compliance and certification, and hosting. Team size grows by model: white-label needs the smallest in-house team, turnkey needs compliance and operations staff, and custom adds engineering. For line items, see the cost breakdown.

Contract terms to check before you sign

  • Term and lock-in: length, renewal terms and exit penalties
  • Exit and data export: what you get, in what format, and how fast
  • Ownership: domain, brand assets, content and affiliate relationships
  • Restrictions: which payment providers, crypto methods and game providers you're allowed to use
  • SLA: uptime commitments, and remedies if they're missed
  • Revenue share: GGR or NGR, which deductions are allowed (bonuses, payment fees, game fees, taxes), and whether you have audit rights
  • License coverage: exactly which markets you may serve

Leaving later: what migration actually involves

What has to move

Player accounts, real-money balances, KYC records, open bonus liabilities, payment tokens and stored methods, affiliate tracking, and responsible-gambling settings such as self-exclusions and limits. How long it takes depends on your export rights, how well the provider cooperates, and licensing approvals on the new platform, so plan in months rather than weeks. The usual failure points are tokenised card data that can't be moved, lost marketing consents and broken affiliate attribution.

How to structure a white-label deal so you can leave

Negotiate controller and data-export clauses, ownership of the brand and domain, defined handover help, and no exclusivity on payment providers. Do this before you sign, while you still have leverage.

Custom builds: the technical bar

Certification and testing

GLI tests gaming devices and systems against the standards set by gaming jurisdictions, and many regulators use GLI's standards as the starting point for their own rules. In Ontario, games and critical gaming systems must be certified by an AGCO-registered testing lab before they can be offered for play.

Cashier and PCI DSS scope

If your cashier handles card payments, PCI DSS applies. The current version is v4.0.1, a limited revision of v4.0. Design the cashier so you handle as little raw card data as possible, and confirm your scope with a qualified assessor. Responsible-gambling tooling (limits, self-exclusion, reality checks) also has to be built in from the start, not added later.

Build vs buy, component by component

Look at each component separately: core platform, game aggregator, CRM, cashier, KYC. Most custom builds still buy aggregation and KYC and build only what sets them apart.

A simple way to choose

Ask three questions:

  1. How fast do I need to be live? Weeks → white-label or turnkey. Months are fine → custom is on the table.
  2. Do I want to own the business, or just test? Test → white-label. Own → turnkey or custom.
  3. Is my product different enough to justify building it? No → turnkey. Yes → custom.

For most operators the answer lands on turnkey: you own the license, the brand and the players, you're live in weeks, and you didn't spend six months and a fortune reinventing a cashier.

The mistake isn't picking the "wrong" model — it's picking white-label to save money, scaling into its ceiling, and paying twice to migrate. Choose for where you want to be in a year.

Score your situation

Rate each of these from 1 to 5: time pressure, ownership intent, product edge, how regulated your target market is, and available capital. High time pressure with low ownership intent points to white-label. High ownership intent with strict target markets points to turnkey. A high product edge with plenty of capital points to custom or hybrid.

Four operator scenarios

  • An affiliate testing one market → white-label. It's low risk and proves demand before you commit capital. Negotiate export rights.
  • A funded operator targeting a regulated EU market → turnkey. You need your own license and direct accountability.
  • A crypto- or Telegram-native product team → custom or hybrid. The edge is the front-end, and shared platforms won't fit it.
  • An established brand expanding into new regions → turnkey core with custom layers. You keep one consistent brand and handle compliance market by market.

Common mistakes

  • Choosing on upfront price alone
  • Signing without data-export rights or a clear controller clause
  • Picking a license jurisdiction that blocks your target markets
  • Under-budgeting player acquisition and launching to an empty lobby
  • Building custom with no real product differentiation
Compliance note: Online gambling is regulated differently in every jurisdiction. This article is general information, not legal advice. Confirm licensing, data-protection and payment-security requirements with the relevant regulator and qualified counsel before launching, and only offer gambling where your license permits it.

Where a full-service partner fits

Whichever model you pick, the hard part is the same: wiring product, games, payments, compliance and tracking into one operation that actually runs. iGaming Gods builds turnkey or fully custom casinos — designed, branded and launched as yours, live in weeks — and runs the traffic and AI operations too, so you don't launch to an empty lobby.

New to the decision? Start with the complete guide to starting an online casino, and price each model with the cost breakdown.

→ Tell us your market and we'll recommend the right build model: talk to the studio

Gambling products are for adults 18+ (or the higher minimum age in your market) and may only be offered where legal. Check licensing and advertising rules in every market you target.

FAQ

Is a white-label casino worth it?

Yes, for testing a market fast and cheap. You launch in weeks under a provider’s license, but you trade control and a slice of revenue and you may not own your player data. It is a starting point, not usually an endgame.

What is the difference between turnkey and custom?

Turnkey gives you your own license and a pre-integrated platform, configured for you. Custom builds the platform around your brand and roadmap from scratch — more control and cost, longer to build.

Can I move from white-label to my own platform later?

Often yes, but migrating players, data and payments is real work. If you expect to scale, starting turnkey (which you own) can save a painful migration later.

How long does each casino build model take to launch?

Relatively speaking, white-label is fastest and usually takes weeks. Turnkey takes weeks to months, depending mostly on how long your licensing takes. Custom takes months. In practice the bottleneck is usually licensing and game or system certification rather than the platform, so start those workstreams first, whichever model you choose.

Can a white-label casino operate in regulated markets like the UK or Ontario?

Usually not in the traditional sense. Tightly regulated markets expect the operator to hold, or be directly accountable under, a proper license. The UK Gambling Commission licenses businesses that serve Great Britain. In Ontario, operators must register with the AGCO and enter into an operating agreement with iGaming Ontario. Confirm your route with the regulator and with licensing counsel.

Who holds the license in a turnkey casino deal?

Usually the operator. The provider supplies and configures the platform, and you hold the license along with the compliance accountability that comes with it. Don't assume this. Put it in the contract explicitly, together with who acts as data controller and which markets the license allows you to serve.

What revenue share do white-label casino providers take?

It varies a lot from contract to contract, and there's no standard figure. Check whether the share is calculated on GGR or NGR, which deductions are allowed (bonuses, payment fees, game fees, taxes), whether you have audit rights, and whether minimum monthly fees apply on top. Then compare the total against a fixed-fee turnkey quote at your expected GGR.

Can a custom casino use third-party game aggregators?

Yes, and most do. A custom build usually means building the layers that set you apart and buying the commodity components: game aggregation, KYC and sometimes the cashier. Aggregated games still need the right certification in each market you target, so check what your aggregator already holds for those markets.

Sources

  1. Malta Gaming Authority · mga.org.mt
  2. UK Gambling Commission – Licensees and businesses · gamblingcommission.gov.uk
  3. iGaming Ontario: Steps to join the Ontario market · igamingontario.ca
  4. AGCO: Internet gaming FAQs · agco.ca
  5. What is GDPR? – GDPR.eu · gdpr.eu
  6. GLI Standards – Gaming Laboratories International · gaminglabs.com
  7. PCI Security Standards Council · pcisecuritystandards.org

How we write and check articles, and how to report a correction: editorial policy.

Planning a launch? We build white-label, turnkey and custom casinos as your brand.

Talk to the studio