White label is a model in which an operator launches a brand on someone else's infrastructure and, as a rule, under someone else's licence. The partner answers for the platform, the licensing perimeter, payments and a substantial part of compliance; the brand owner answers for marketing, traffic and the relationship with the audience.
What the supplier takes on
- Licence and regulatory reporting — the licence holder is the legal entity facing the regulator.
- Platform and content — ready integrations with providers, the wallet, the bonus engine.
- Payment perimeter — contracts with payment providers and processing of withdrawals.
- Part of operations — frequently KYC, anti-fraud and first-line support.
What it costs
The economics are built around a share of revenue rather than a one-off purchase, and minimum committed payments are usually attached to it. The second class of cost is non-monetary: product configuration stays inside the platform's boundaries, and changes to bonus mechanics or to the set of payment methods go through the partner. The player base, meanwhile, remains tied to the partner's licence and infrastructure, which turns a move to an own licence into a project in its own right rather than a switch to flip.
When the model fits
White label is justified when the team's core competence is traffic and audience work rather than running a platform, and when time to market matters. It suits poorly those building the product as a long-term asset on their own technology.
Two points deserve scrutiny before signing: the exit terms, and who owns the player data once the agreement ends.