Technical handover
The game build, API version, session and wallet model, supported devices and the team responsible for integration.
Existing technical integrations can shorten the path from your game build to launch. Find the route that fits your operation.
Discuss your integration34 routes · Commercial agreements pending
Casino, sportsbook and lottery businesses serving players.
The technology behind gaming operations and connected experiences.
Content distribution and aggregation routes connecting games with operators.
Companies are grouped by their primary role here; some also offer other services. Integration names may reflect established technical routes.
The game build, API version, session and wallet model, supported devices and the team responsible for integration.
The intended markets, testing evidence, external approvals and launch responsibilities for the specific game.
Distribution terms, availability, revenue arrangements where relevant and the parties signing the agreement.
Directory inclusion identifies an available technical route. The exact delivery model and remaining dependencies are confirmed in the technical conversation.
Tell us your platform, intended markets and the games you want to launch. We’ll review the existing integration and agree the next steps with you.