How an integration works
One contract, one adapter, every title. What each side builds and in what order.
Read this first, whatever you are here to do.
One integration, not one per game
A Nordon title is not an integration of its own. Every game speaks the same contract, so the work you do once covers the portfolio, and a title we release next year arrives as a game identifier rather than as a project.
The engine never learns your name. It speaks one canonical contract, and an adapter translates that contract into whatever your platform already does. That boundary is the whole arrangement: onboarding a partner never reaches the game, and a change inside a game never reaches you.
Who builds what
- You provide
- A wallet your adapter can reach, a launch token we can exchange for a session, and a test account we can play against.
- The adapter
- Translates the contract into your protocol. Either side can write it. We publish a worked example against a deliberately awkward sandbox partner, because an adapter that only works against a polite one is not an adapter.
- We provide
- The games, the round logic, the settlement, the build manifests and the conformance kit that proves the adapter before it is pointed at anything real.
- Neither side builds
- A player account. We are never told who is playing: a launch returns a reference, a currency and a limit, and nothing that identifies a person.
The order it happens in
Every step has an artefact at the end of it, so nobody has to remember whether it was done.
Evaluate
Play the demos in a browser and read the contract on these pages. Nothing is signed and nothing is installed to get this far.
Build the adapter
Five calls against your wallet. The sandbox partner ships with the kit, so the adapter can be finished and proven before your own test environment is ready for us.
Run the conformance kit
Twelve cases covering sessions, idempotency, rollbacks, amounts and error mapping. It talks to the adapter and to nothing else, so it runs against your real sandbox rather than a fake of it.
Sandbox launch
We point a game at your adapter with your tokens and play it end to end. This is the first time the two systems meet.
Go live, per game and per market
Availability is decided one title and one jurisdiction at a time, and recorded rather than agreed in a thread.
What this is not yet
Nordon is a young studio and these pages describe a contract that is implemented and proven, not a catalogue that has been through a test house and put on sale. No title has been through a test house, none is approved in a market, and nothing takes real money today.
That sequence matters for your planning more than any promise would: the integration work and the certification work are independent, and the integration is the part that is ready for you now.