Turnkey iGaming platform,
live in weeks.

Speed, without the shortcuts

A turnkey launch gets you to market in weeks on a platform that is already proven and certified-ready. You bring the brand and the licence; we bring everything else.

Outgrow it later? It is the same modular core, so you can customise without re-platforming.

“Turnkey” is three different deals wearing one word

The list above is what a turnkey launch includes. It says nothing about what you own — and that is the question the word is used to avoid. Ask five suppliers for a turnkey platform and you will get five contracts that differ on the only thing that matters at exit. The blurring is deliberate. Here is the taxonomy underneath it.

White-label — you rent a brand on someone else’s licence

The provider holds the gambling licence. Your players register under it, accept the provider’s terms, and legally become the provider’s customers. You supply a brand, a domain and the marketing spend. The provider supplies everything else and takes a share of revenue. In regulatory terms you are closer to an affiliate with a skin than to an operator. If the relationship ends, the players stay where they registered.

Turnkey — your licence, their platform

You hold the operating licence. You carry the regulator relationship, the AML obligations and the liability. The provider licenses the platform to you and runs it. This is a genuine step up: you are an operator, the player relationship is yours, and you answer to the regulator directly. But the software is still licensed, not owned. You cannot fork it, you cannot take the codebase to another vendor, and the fee usually still scales with your revenue.

Custom build — you own the codebase

The platform is written for you, the IP assigns to you, and it runs on infrastructure in your accounts. There is no revenue share because there is no licensor. The trade is real: you pay for the build up front and you carry the product decisions yourself.

Buyers sign “turnkey” deals every year believing they bought the third tier, then discover at diligence they bought the first. The contract language that decides it is rarely on the sales deck. Our companion piece on custom development versus white-label works that comparison end to end; this page is about the trap in the middle tier.

Four questions that settle which tier you are buying

Ignore the brochure. These four answers, in writing, place any deal on the table above. A supplier who will not answer them plainly has answered them.

1. Whose licence are players registered under?

Read the player terms and conditions your sign-up form will actually show. The licensee named in that document owns the customer relationship in the regulator’s eyes. If it is not your entity, you are white-label, whatever the sales agreement is titled.

2. Who is the data controller, and where does the wallet ledger live?

Two questions that get answered as one. The player database can be nominally yours while the wallet — the authoritative ledger of balances, bets and settlements — sits inside the provider’s system. That matters because balances are liabilities. If you cannot reconstruct every player’s balance from data you hold, you cannot move and you cannot audit yourself. Ask for the export schema, not a promise of “full data access”. KYC and AML records have the same problem: verification artefacts and audit trails are what a regulator asks for, and they are often the hardest things to get out.

3. What can you actually take with you?

Not the platform — that is what a licence means. The realistic question is the rest: player records, transaction history, KYC artefacts, outstanding bonus liabilities, and the integration contracts with game studios and payment providers. Check whose name is on those contracts. If the provider signed them, the terms leave with the provider.

4. At exit, does a buyer acquire an asset or a contract?

This is the question that reprices the whole decision. Diligence asks what the company owns. A licence and a player base have value. A platform contract with a change-of-control clause is something the buyer must renegotiate with a third party who knows the deal cannot close without them. Owned code sits on the balance sheet and cannot be repriced by someone else’s commercial team.

The cost curve, honestly

White-label and turnkey are cheaper on day one. That is not marketing — it is true, and a developer who tells you otherwise is selling. But the deferred cost is not avoided. It is converted into a share of every future month.

Revenue share has one unpleasant property: it scales with your success. You pay the most in exactly the months you are winning, and what you pay is not tied to work the provider is doing that month. A custom build inverts the shape — front-loaded, uncomfortable, then flat, sized to load rather than to margin. Somewhere the two lines cross.

Where they cross is not a number we can print: it depends on your take rate, your marketing efficiency and your provider’s tiers. Anyone who quotes a universal figure is guessing. The conditions that pull the crossover earlier are knowable:

• Volume. Revenue share is a tax on gross gaming revenue. The bigger the GGR, the worse the trade gets — automatically, every month.
• Multi-brand. Licensing deals usually charge per brand. Owned code deploys a second brand for the cost of the deploy.
• Multi-market. Each new jurisdiction adds compliance work you must persuade a provider to prioritise against their other clients. On your own infrastructure, you set the queue.
• Differentiated product. If your edge is a mechanic, a bonus structure or a risk model nobody else runs, a shared platform cannot express it. And if it could, your competitors get it in the next release.
• Intent to sell. If there is an exit thesis, the asset is the entire point.

If none of those apply — single brand, single market, commodity product, and you are testing whether the market wants it at all — white-label is the correct answer. We will tell you so on the call.

What we mean when we say turnkey

We do not sell the middle tier. We sell its speed without its ownership cost, and the mechanism is scope rather than shortcuts.

A first launch does not need every vertical, every market and every payment rail. It needs one casino or one sportsbook that converts, a cashier that clears, and compliance that passes certification. Built on a modular core — wallet, player account management, bonusing, reporting and provider integrations as separate services rather than one entangled monolith — that is a build you can put live in weeks and then extend, because the seams are exactly where the next thing attaches.

What you get on day one is narrower than a shelf platform. What you have in year two is a codebase that absorbed a second brand, a second market and a mechanic your competitor cannot copy — with no re-platform, no renegotiation and no migration.

Getting off a white-label later — and why you will not enjoy it

Every buyer who chooses speed tells themselves they will migrate once the numbers justify it. Some do. It is worth knowing what that project is before you rely on it as a plan.

The players do not come with you

If your players registered under the provider’s licence, they are the provider’s customers. A new licence means a new legal relationship, so in practice every active player must re-register with your entity and re-verify. You will not carry all of them, and the drop-off lands at exactly the moment you are changing everything else.

Balances are liabilities, not rows

Player balances cannot be copied into a new database. They are money you owe, and moving them has to satisfy your regulator, your payment providers and your auditors. Expect to run both systems in parallel while balances drain or settle, and expect to reconcile two ledgers to the cent. This workstream sets the timeline, not the code.

The licence transition is the long pole

Your own licence has to be live before migration, not after — so licensing runs months ahead of any technical work. The regulator will also want the platform itself assessed. RNG and game certification is a separate queue you cannot compress by working harder.

SEO and domain continuity

The asset most often destroyed in a migration is organic search. Rankings attach to URLs, and a re-platform typically changes every one of them. Keep the domain in your own registrar account from day one — never the provider’s — map old URLs to new ones, redirect them before launch, and expect a dip anyway. If acquisition depends on search, this is a pre-condition, not a launch-week detail.

None of this makes white-label wrong. It makes “we’ll migrate later” a project rather than a footnote, and it is worth pricing when you sign, not when you outgrow. If you are still weighing partners, our notes on how to choose an iGaming development company cover what to ask before the contract is drafted.