Who this guide is for
Founders choosing how to launch, white label operators deciding whether to move, and turnkey operators whose roadmap has started to wait on someone else's release queue. The short answer: pick the model by what you need to own in three years, not by what you can afford this quarter. White label is a brand on someone else's licence and platform. Turnkey is your licence on someone else's platform. Ownership is your licence on a platform you control, either a licensed engine with source-code rights or a custom build whose IP is assigned to you.
Setup fees, revenue shares and three-year costs for white label and turnkey are on the online casino software page. This guide covers what sits outside the price: ownership, exit and the order of moves.
The third model: owning the platform
Owning the platform comes in two contract forms, and they are not the same thing.
- A licensed engine with source-code rights. You take an existing product, such as our casino engine, and the contract gives you the source plus the right to modify, host and maintain it yourself. The vendor keeps title to the code. What matters is the scope of your licence: perpetual or fixed-term, exclusive or not, limited to your brands or transferable to a buyer of your business.
- A custom build with IP assignment. A platform written for you under a development contract, such as our custom platform development, with the copyright assigned to your company. Under UK law the developer is the first owner of the code by default, so without a written assignment you may hold only an implied licence to use it.
Both forms share one trap. Getting the source code delivered and getting rights in it are two separate events, and every developer reuses its own libraries, its "background IP". If the contract assigns the new work but says nothing about the background, you own a platform you cannot legally run without the vendor. Ask for a perpetual, warranted licence to every background component, and for a list of the open-source components and their licences.
What ownership buys: you change the product on your own schedule, any development team can work on it, and the platform takes no share of your GGR. What it costs: hosting, security, release engineering, and certification of each release wherever your licence requires a lab to test the platform. Curaçao, for example, accepts reports only from test houses accredited to ISO/IEC 17025 by an ILAC-signatory body. That is a standing team, not a project.
Who holds what in each model
Read each row as a clause to find in the contract. Where the model leaves it open, the default usually favours whoever drafted the contract.
| Asset | White label | Turnkey | Platform ownership |
|---|---|---|---|
| Gaming licence | The provider or a master licensee. In Great Britain the regulator says compliance responsibility for a white label site rests with the licence holder and cannot be transferred | Yours | Yours |
| Player data | Held by the licence holder; your access and your export on exit exist only if the contract grants them | Yours, on the vendor's platform; check export format and frequency | Yours, on infrastructure you control |
| Merchant accounts and processing history | The licence holder's MCC 7995 accounts; the history is not yours unless the exit clause hands it over | Yours | Yours |
| Domain and brand | Should be yours. Check who is the registrant of record and who holds the registrar account, not only whose logo is on the site | Yours | Yours |
| Game studio contracts | The provider's, so the provider's prices and studio lists apply | Often through the vendor's aggregator; direct contracts optional | Yours to sign, directly or through an aggregator |
| Platform code | The provider's; no access | The vendor's; escrow if you negotiate it | Yours by assignment, or licensed to you with the source |
| Platform certification | Covered under the licence holder's approvals | The vendor holds the product certificates; testing of your own setup for a given licence may fall to you | Yours, for every release the licence makes you submit |
The licence row has a variant worth knowing. An Isle of Man sub-licence lets you register players under your own licence while games run on a fully licensed partner's servers, but the sub-licensee may use only one Isle of Man-licensed platform at a time. You hold a licence and are still tied to one platform, so a move means changing licence structure as well as software.
What the exit clause must say, by model
Negotiate the exit before the entry price. Each model blocks it on something different.
| Leaving white label | Leaving a turnkey vendor | Leaving a platform you own | |
|---|---|---|---|
| Blocked on | Your own licence being granted | A new platform being certified and integrated | Nothing contractual; only your own team's capacity |
| Data to get in writing | Full player export with balances, KYC status, responsible-gaming limits and self-exclusions, in a stated format | The same, plus transaction and bonus history the regulator may ask you to keep | Not applicable |
| Money | Release schedule for the rolling reserve and final settlement | Final invoice, any minimum-fee tail | None |
| Transition help | A period during which the provider keeps the brand live while you move | Parallel running and data-migration support at stated rates | Handover documentation from whoever maintained it |
| Typical failure | Processing history stays with the provider's acquirer | Export arrives as an unusable dump, and nobody owns the mapping | Background IP licence ends with the vendor relationship |
For a vendor-held platform, source-code escrow is the clause that covers the case where the vendor itself disappears. Release triggers are usually the vendor's insolvency or a material failure to maintain the software. An escrow is only as good as its last deposit, so require a fresh deposit after each release and a verification test that compiles it.
The usual migration path
Operators rarely start on an owned platform. The moves come in this order, each with a trigger you can see coming.
- White label to turnkey when the revenue share outweighs the cost of a licence, or when the licence holder's restricted list blocks a market you want. Start the licence application before you need it, because the licence sets the date. The white label page lists what moves and in which order.
- Turnkey to an owned platform when your product roadmap waits on the vendor's release queue, when you run several brands or markets that need different builds, or when a buyer or investor will value the platform as an asset. The move is a platform migration: same licence, new system, player balances and history carried across.
- Straight from white label to ownership is rare. You need a licence for either step, and building or adopting a platform at the same time as your first licence application puts two long, separate risks on one launch date.
Owning the platform can bring a supplier obligation with it. Finland accepts applications for a gambling software licence from 1 July 2027, and from 1 July 2028 licensed operators may run only software from licensed providers. If you own the engine and target a market like that, ask counsel early whether the supplier licence becomes yours.
Who should not own the platform
- Operators without a licence yet. Ownership solves a control problem you do not have until you hold one.
- A single brand in a single market whose roadmap fits a vendor's product. You would be paying for an engineering team to keep what a licence fee already covers.
- Anyone who cannot staff release, security and certification work every month, not just at launch.
Questions to put to any vendor, including us
- In whose name are the domains, the merchant accounts and the studio contracts registered on day one?
- What exactly do I receive on exit, in what format, and within how many days of notice?
- Is the source code assigned, licensed or escrowed, and what happens to background IP when our contract ends?
- Which release triggers does the escrow agreement name, and when was the last deposit verified?
- Which approvals belong to your product, and which ones must I obtain for my own configuration?
Frequently asked
Is turnkey the same as owning the platform?
No. Turnkey gives you your own licence, merchant accounts and players on a platform the vendor owns and runs. Ownership means the code is assigned to you, or licensed to you with the source and the right to change it yourself.
Can I buy the source code of a turnkey platform later?
Where a vendor offers it, a source-code licence is a separate contract with its own price and scope. Ask whether it covers background components and future versions, and whether you can transfer it if you sell the business.
Do I need source-code escrow if I own the code?
No. Escrow protects a licensee against a vendor that fails. If the code is assigned to you and you hold a current copy that builds, there is nobody to escrow against.
Which model keeps the most value if I sell the business?
The one where the assets sit in your company: licence, merchant accounts with their history, player data, domains and, with ownership, the platform. A white label brand sells mostly its marketing and its traffic, because the rest belongs to the licence holder.