The decision that shapes the business
An operator gets its platform one of three ways: it rents a brand on someone else's licence and platform (white label), it licenses a platform to run under its own licence (turnkey), or it builds and owns the core (proprietary). The White Label vs Turnkey guide on this site sets out the commercial trade-offs; this lesson goes into the technical and operational ones, because the decision is rarely made once. Many operators start on a turnkey platform, layer their own technology on top, and either graduate to proprietary or stay hybrid, and the path they take depends on what they understand about the architecture.
White label, technically
Under a white label the operator has no platform relationship at all: the provider runs the PAM, the wallet, the integrations, the compliance modules and usually the front-end framework, and the brand owner supplies a skin, a domain and marketing. The customer's account lives in the provider's database under the provider's licence; in Britain the Gambling Commission's 2019 to 2020 compliance report was explicit that responsibility for compliance on a white-label site always sits with the licence holder, which should make sure its customer monitoring works across all its partners so that it has a holistic view of each customer's activity. The technical consequences follow. The brand has read access to its customers through the provider's reporting and, typically, cannot export the customer base in a form that lets it re-register them elsewhere; product, cashier and bonus configuration are the provider's decisions within a menu; and integrations the brand wants (a CRM tool, an affiliate platform, an analytics stack) are limited to what the provider exposes. Speed to launch is the benefit: a brand can go live far sooner than under any other model, with certified games, working payments and a compliance function already in place.
Turnkey, technically
Under a turnkey arrangement the operator holds the licence and the customer relationship; the provider supplies the PAM, the integrations and the modules as a service, hosted by the provider or in a cloud tenancy the operator controls. The operator's engineers work against the platform's APIs: a front end built on the API, a data feed from the platform's events into the operator's warehouse, CRM and analytics connected through webhooks and exports, and configuration of bonuses, limits, markets and payments through the back office. The platform is multi-tenant in most cases, so the operator's roadmap is the provider's roadmap, and a feature the operator needs is a request that competes with every other tenant's.
What the operator owns under turnkey is decided by the contract and the architecture: the customer data (with export rights), the front end, the data warehouse, the CRM and the configurations. What it does not own is the core, and switching cores is a migration: re-registering or migrating customers and balances, re-integrating games and payments, recertifying in every market, and running two platforms in parallel through a cutover. Migrations take many months, and that cost and risk are the reason platform providers' commercial position is strong.
Proprietary, technically
A proprietary platform is built by the operator's own engineering organisation, usually starting from the wallet and the account core and integrating games, payments, sportsbook and compliance modules from specialist suppliers. The decision to build is a decision to run a technology company: an engineering team of its own, a product organisation, security and infrastructure functions, and a certification programme in every market. The advantages are control of the roadmap, no platform revenue share, the ability to differentiate the product at the core (a bespoke wallet feature, a unique bonus mechanic, a data model built for the operator's analytics) and, at scale, lower unit cost; many of the largest operators run proprietary cores and present them as a competitive advantage. Flutter, for example, tells investors in its annual report that it has a distinctive proprietary technology platform developed and refined over more than 30 years.
The risks are the ones any large software project carries, compounded by regulation: a core that takes two years, a certification that fails, a wallet defect discovered in production. Operators that have built successfully have usually done it in stages, replacing one rented component at a time behind a stable API, rather than in a single cutover.
The hybrid, which is what many operators run
The common shape of a mid-sized operator's technology is a rented core with proprietary layers: the PAM and wallet from a provider; the front end, the data platform, the CRM logic and often the sportsbook trading tools built in-house; specialist modules (identity, payments orchestration, geolocation, anti-money-laundering scoring, game aggregation) from best-of-breed vendors integrated by the operator; and the bonus engine somewhere between, configured on the platform but driven by the operator's CRM. This architecture captures most of the differentiation available (the customer experience, the data, the marketing) without the core-platform risk, and it is the path from which operators graduate to proprietary if they choose to, by replacing the core last.
The evaluation
Choosing a turnkey provider, or a set of modules for a hybrid, is a due-diligence exercise with a technical checklist alongside the commercial one.
Certifications. In which jurisdictions is the platform certified, by which laboratories, to which versions, and who pays for new certifications when the operator enters a market.
Wallet and API performance. Latency and throughput under load, with evidence from other tenants; the seamless wallet's behaviour under game and sportsbook peaks; API completeness for the operator's front-end and data needs.
Integrations. Which game studios and aggregators, sportsbook feeds, payment providers, identity vendors and CRM systems are live, in which markets, and what a new integration costs and takes.
Data. What the operator can extract, how (real-time events, daily exports, direct warehouse access), in what schema, and whether the provider's own analytics are a substitute or a supplement.
Configuration versus code. How much of the operator's needs (bonus rules, limits by market, product restrictions, cashier flows) can be configured without a change request, and what the change-request process and pricing look like.
Security and resilience. Certifications and audits, penetration testing, disaster recovery, uptime history and the incident-response process; lesson four covers the security standards and lesson five covers resilience.
Roadmap and reference customers. Where the platform is going, how many tenants share it, and what those tenants say.
Exit. Data export rights, migration support, and what the contract says about termination and transition. The evaluation that skips this item is the one the operator regrets.
The supplier landscape
The platform market has a recognisable shape without naming names. A handful of large providers supply turnkey PAMs to many operators across regulated markets, often bundled with their own sportsbook or casino content. Sportsbook specialists supply the betting engine and managed trading with or without a PAM. Aggregators supply casino content integration. Payment orchestration, identity, geolocation, anti-money-laundering and CRM are supplied by specialist vendors, many of them from outside gambling. White-label providers sit at the entry end, often themselves running on a turnkey platform. And several large operators license their proprietary platforms to others as a B2B business, which is how a proprietary investment becomes a revenue line: Betsson, for example, offers its technology and platform to other gaming operators alongside its own brands. Supplier licensing regimes mean that many of these suppliers are themselves licensed or registered, and an operator's choice of supplier is constrained to the ones approved in its markets. In Britain all gambling software a remote casino, bingo or betting licensee uses must be manufactured, supplied, installed and adapted by holders of a gambling software licence, although general business software is not licensed. Sweden requires an authorisation for anyone who manufactures, installs or modifies gambling software used for online gambling; Denmark requires a supplier licence of anyone providing games to its betting and online casino licensees; Romania licenses software suppliers, affiliates and payment service providers, and operators may work only with licensed partners; and American states such as New Jersey go furthest, registering vendors from outside gambling as well: its internet gaming vendor list, last updated in March 2020, runs from payment processors to large technology companies.
What to take from this lesson
White label means no platform relationship and no exit; turnkey means the operator owns the licence, the customers, the front end and the data but not the core; proprietary means owning the core and running a technology company; and the hybrid, a rented core with proprietary layers and best-of-breed modules, is what many operators run and the path to graduation. A platform evaluation covers certifications, wallet performance, integrations, data access, configuration scope, security, roadmap and, above all, exit. Gambling software suppliers are themselves licensed in many regulated markets, and some regimes cover other vendors too, which constrains the choice.