Skip to main content

Application to a live environment, end to end

The platform creates the environment, wires the wallet, connects the aggregated catalogue and applies the brand. Provisioning takes hours. Trading depends on approvals we sequence with you.

The brand colour editor with the primary and secondary swatches open beside the tokens they write into the player lobby.

How provisioning runs

From application to a provisioned environment

One sequence, run by the platform. Your part is the application and the decision to launch, not the build.

Provisioning takes hours. Getting to a live, trading casino also depends on licence approval, payment onboarding and content agreements, which we sequence with you.

  1. Apply

    One form starts the operator application. Company or individual details, target markets, and which of the two routes you want.

  2. Verify

    Identity or business verification runs through Sumsub. The attempt has its own timeline, so a stalled check is visible rather than discovered later.

  3. Provision

    The platform creates the environment, wires the wallet and the ledger, and connects the aggregated game catalogue.

  4. Brand

    Two brand colours generate the complete look. Logo, favicon and login background upload into the brand's own media space.

  5. Approve

    Nothing goes live on one signature. Platform approval and your own explicit launch are both required before players can reach it.

  6. Operate

    The back office is handed over with players, games, payments, audit and settings already in place and already connected.

What the platform assembles before anybody logs in

The environment that appears is not an empty shell waiting for an engineer. These parts arrive connected to each other.

The environment itself

A running deployment with the account core, the wallet and the ledger already wired together, rather than a checklist of services to install.

The Deposits screen showing totals for deposited, failed, paid and net, above a table breaking finished deposits down by pay currency.

The wallet and the ledger

Real, bonus and locked balances in one reconciled structure, with fiat and crypto routes ready to be switched on once the provider contracts exist.

A player record with account, tier, KYC, AML and two factor status chips above the identity, documents, review and decisions tabs.

The player account core

Registration, verification states, compliance tiers and player safety controls are part of the account from the first player, not added later.

The Highlight token panel showing a colour value, a note that it is used for badges, tags and alerts, and the five states the platform derives from it.

The brand

Two colours generate every derived state of the design system, with the contrast ratio calculated as it goes so nothing publishes unreadable.

Screenshots are captures of the MaxBet and LuckyOni demo tenants. Every figure on screen is demo data.

Dual approval, and what sits behind it

A new casino goes live only when two separate decisions agree. Governance is written into the workflow rather than into a policy document nobody opens.

Platform approval

  • Verification complete

    Individual KYC or business KYB reviewed and decided, not merely submitted.

  • Brand configuration published

    The look, the logo and the player facing copy exist rather than being planned.

  • Payment routes connected

    The rails the brand will actually take money on are wired and tested.

  • Game catalogue connected

    Studio content is synced into the lobby, with visibility set per studio.

  • Player protection controls configured

    Limits, self exclusion and account states are in place before the first player.

Your launch

  • Your explicit launch action

    The final decision is yours, taken in the back office, and recorded.

  • Domain pointed and verified

    The address players will type, under your control.

  • Staff invited with scoped roles

    Permissions decided before anyone needs them, down to the individual right.

  • Player facing terms in place

    Terms, privacy and responsible gambling pages published on the brand.

See the back office

Watch it happen

Two recordings from the running platform. The operator sign up wizard, and a new brand from an empty environment to a working player lobby.

Launch

Provision a casino. The recording follows a new brand from an empty environment to a working player lobby.

Launch: Provision a casino. The recording follows a new brand from an empty environment to a working player lobby.

What still needs a person

Provisioning is ours to promise. The rest of reaching a trading casino is not, and pretending otherwise would cost you a quarter.

Runs automatically

No ticket, no project manager

Creating the environmentProvisioning the deployment the brand will run on.
Included
Wiring the wallet and the ledgerConnecting balances, settlement and the transaction record to the account core.
Included
Connecting the game catalogueSyncing aggregated studio content into the brand and placing it in the lobby.
Included
Generating the brand look from two coloursDeriving every token state and checking contrast before publication.
Included
Deciding identity and business verificationSumsub runs the checks. A reviewer takes the decision.
Not included
Approving go-livePlatform approval and your own explicit launch, both required.
Not included
Licence approval in your target marketsA regulator's decision, taken on the regulator's timetable.
Not included
Payment provider onboardingContracts and underwriting agreed with the providers themselves.
Not included
Game content agreementsCommercial terms agreed with studios, directly or through the aggregator.
Not included

Needs a person

Ours, yours or a third party

Creating the environmentProvisioning the deployment the brand will run on.
Not included
Wiring the wallet and the ledgerConnecting balances, settlement and the transaction record to the account core.
Not included
Connecting the game catalogueSyncing aggregated studio content into the brand and placing it in the lobby.
Not included
Generating the brand look from two coloursDeriving every token state and checking contrast before publication.
Not included
Deciding identity and business verificationSumsub runs the checks. A reviewer takes the decision.
Included
Approving go-livePlatform approval and your own explicit launch, both required.
Included
Licence approval in your target marketsA regulator's decision, taken on the regulator's timetable.
Included
Payment provider onboardingContracts and underwriting agreed with the providers themselves.
Included
Game content agreementsCommercial terms agreed with studios, directly or through the aggregator.
Included

The four rows at the bottom are the second clock. They sit with regulators, banks and studios rather than with us, and we sequence them with you during discovery.

What this page covers in the feature matrix

Each capability below is a row in the platform index, where its tier sits beside the method and the date behind it. Read the full feature matrix.

Auto-provisioning for white-label

A white label casino is provisioned end to end automatically: application, verification, setup and deployment, with the platform provisioned in hours.

Dual-approval go-live

A new casino goes live only when platform approval and an explicit operator launch both land. Governance is built into the workflow, not bolted on.

No developer setup needed

Operators go from application to a live environment, and make every change after launch, without a development team on their side.

Single codebase, every deployment

Our own brands and every sold copy run identical software. An improvement is built once and reaches everyone, so quality compounds while cost stays flat.

Start an application and watch the environment appear

Tell us the route, the stage you are at and your licence position. We will start the application and walk the provisioning path with you.

We reply within one working day.