Comparison
Turnkey casino vs casino API
The question is whether you already have a platform. A turnkey build supplies one; a casino API supplies content for the one you have. This is turnkey vs aggregator API in plain terms.
Turnkey
Platform, games and back office
Casino API
Games for your platform
Side by side
| Turnkey casino | Casino API | |
|---|---|---|
| Includes | Front end, PAM, back office, games, optional sport | Catalogue, launch, wallet contract, reporting |
| You bring | Licence, PSPs, marketing | A platform with a seamless wallet |
| Cost | Project fees plus a GGR share | GGR share (13% Asia, 16% elsewhere) |
| Best for | New operators without a platform | Operators with a platform |
How to decide
If you have no platform and no plans to build one, go turnkey. If you have a platform or a team building one, take the casino API. A turnkey build uses the same aggregator underneath, so the games are the same either way.
The games can match while the project does not
Because the same catalogue sits under both, the choice is not which slots exist. It is who builds the lobby, the account, the cashier wiring and the back office. A turnkey project configures those for a licence you bring, and you still bring payments and marketing. An API project assumes the lobby and the account exist and adds launch, wallet traffic and a report. Buying turnkey when the platform is already in production duplicates a stack you will then have to reconcile.
Cost follows that split. Turnkey has project work plus a share of GGR. The API is the share on games, for an operator who already pays for a platform. Compare them on the work you do not yet have, not on a demo that showed the same titles. The rate column in the table is the content share. It is not a quote for the platform project, and it is not a reason to skip payments, KYC or the licence.
Same catalogue, different owner of the player
On the API the player record stays in your platform. On turnkey it lives in the platform being configured for you, so the contract has to say how you export it. Decide that before you pick the route, or the games will look identical and the exit will not.
Match the route to what you already own
The deciding question is not which product is better. It is which of the two leaves you with less duplicated work.
| What you have | Turnkey | Casino API | The question that decides it |
|---|---|---|---|
| Licence, PSP account, no platform | Fits | Assumes a platform you do not have | Can you staff a platform build this year, or would that be the whole budget? |
| A PAM in production with a cashier and bonus engine | Duplicates a working stack | Fits | Do the callbacks you already expose match the wallet contract on offer? |
| Sportsbook live, casino missing | Rarely | Fits | Where casino stake sits in the ledger that already settles sport |
| Group launching a second market on one back office | Not usually | Fits, if the platform separates records per licence | Whether two licences can share a database without sharing a player view |
| Small team, no compliance staff, no platform | Neither yet | Neither yet | Who enforces limits and answers the regulator |
The cost sits in the duplicated stack, not the invoice
A turnkey build bought by an operator who already runs a platform produces two accounts for one player, two bonus ledgers and a reconciliation nobody requested. The invoice is visible in advance; the argument about which system owns the balance is not, and it lands on finance and support in the first month. Adding a licence, a cashier and a lobby to a stack that exists is normally a smaller project than joining two stacks together afterwards.
The API bought without a platform fails earlier and more quietly. Nothing launches, because a launch call needs a player the platform can name and a wallet that can reserve. The 24–72h figure describes the integration once those exist. A pre-launch brand should sequence the platform first and treat content as the last purchase, not the first invoice.
FAQ
Questions operators ask
If the games are the same, why would we pay for a turnkey build?
Because you do not have the account, the lobby and the back office those games need to call. You are paying for that platform work. If those pieces already run, the API is the content path and the turnkey fee would buy a second copy.
Can we start on the API and add a turnkey front end later?
Only if you are prepared to move or rebuild the player record. It is usually cleaner to pick the owner of the account first. Adding games to a platform you keep is the API. Replacing the platform is a different project.
Does turnkey include the licence and the payment providers?
No. You still bring the licence and the PSPs. Turnkey configures a platform and the games. It does not stand in for the authorisation or for the cashier's banking relationships.
We have a licence and a payment provider but no platform. Which side are we on?
Turnkey, or a platform built to your specification before content is connected. A licence gives permission and a PSP gives you a way to take money. Neither provides an account, a lobby or a wallet the games can call, so an API bought now would sit untested until the platform exists.
After a turnkey launch, who ships changes to the lobby?
The contract decides. A dedicated configuration usually includes a change process with a queue and a release window, and your team writes the requirement rather than the code. Ask how a post-launch change is priced and whether a copy fix sits in the same queue as a new payment method.
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.
- Malta Gaming Authority
Licensing and player-protection rules for Malta-licensed operators.
www.mga.org.mt
- UK Gambling Commission
Remote gambling and software technical standards.
www.gamblingcommission.gov.uk
Keep reading
Related pages
- Solution · TurnkeyTurnkey casinoA full stack for licensed operators: front end, player accounts, back office, aggregated games and an optional sportsbook.Read
- 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
- ComparisonTurnkey vs white labelA turnkey casino is your own installation. A white label is your brand on infrastructure shared with other operator brands.Read
- Solution · PlatformCasino platformPlayer accounts, a back office, a bonus engine and multi-brand support, wired to the game aggregator and the shared wallet.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.