The decision
These labels describe delivery models, not universal ownership rules or fixed timelines. The practical choice depends on how much responsibility your team can own and which parts of the system must remain changeable.
What to check
- White label: establish who holds permissions, controls the player relationship and supplies support. Check data access, branding limits, export rights and termination terms instead of assuming the label answers them.
- Turnkey: document what arrives configured and what still requires integration, approval or operating staff. Included software does not mean every external service is included.
- Custom build: budget ongoing maintenance, security review, integrations and incident response alongside development. Control brings responsibilities; avoid treating the first release as the total cost.
- Hybrid approach: identify the component you need to replace and the interfaces around it. Test whether modular adoption is genuinely smaller than migrating the whole operation.
A practical evaluation
For each model, write who owns the licence, code, accounts, data exports and operational decisions. Ask the supplier to confirm those responsibilities in the proposal. Choose the arrangement your team can run after launch, not merely buy before it.
Responsibility matrix to attach to each proposal
For every model, fill in supplier, operator and third-party owner for each row. The label on the offer does not determine ownership; the signed scope should.
- Permissions and player relationship Who is the operating entity, who obtains relevant permissions, and who answers player complaints? Get qualified market advice; no delivery model confers permission by itself.
- Platform and changes Which configuration, source-code changes, integrations, maintenance and rollback tasks are included? Who accepts each change after launch?
- Games, sportsbook and payments Separate platform connections from provider onboarding, trading or settlement, game royalties and payment fees. Record each external contract and approval owner.
- Data and exit Who can export player and transaction records, in what format and timeframe, and who funds the transition? Verify with a sample export before signing.
- Apps and support Who prepares app builds, owns store accounts and handles review or rejection? Distinguish included support hours from player operations and incident response.
Compare the filled rows and unresolved dependencies before deciding whether white label, turnkey, custom or hybrid work fits your team's capacity.
Explore the product
nuke.ai · Pricing · iGaming terms explained
Related platform capability: Cloud-native and on-premises iGaming deployment.