The build-vs-buy decision is the most consequential infrastructure choice an iGaming operator makes. It shapes every subsequent decision: which markets you can enter, how fast you can launch, how much you control your customer experience, what your operating cost looks like, and whether your enterprise value compounds or accretes. Most operators get the framing wrong because they treat it as a binary. It is not. It is a three-option choice with different time horizons.
On this page
- The decision is rarely binary
- The three real options
- White label: when it works
- Turnkey: the middle path
- Proprietary: when the economics support it
- Total cost of ownership over five years
- The strategic-control question
- Decision framework
- Frequently asked questions
The decision is rarely binary
Operators frame this as “build vs buy” and then debate it as if those are the only two options. The framing is wrong on two counts. First, “build” can mean anything from “fork an open-source platform” to “engineer a full proprietary stack.” Second, “buy” can mean white label (rent a brand on someone else’s platform), turnkey (buy a managed-service platform with operator-level control), or piecewise (assemble best-of-breed components yourself).
The real choice is: where on the build-buy spectrum does the operator’s strategic position justify the investment? An operator with three years of operating history, a clear product thesis, and capital available has a different right answer from an operator launching its first market.
The framework that works is to evaluate each layer of the stack separately. Game content (almost always buy via aggregator). Wallet and payments (depends on scale). Player account management and KYC (depends on multi-market exposure). Risk and fraud (depends on volume). CRM and segmentation (often differentiating, often build). Reporting and analytics (often differentiating, often build).
Operators who decide layer-by-layer end up with a hybrid stack that fits their strategy. Operators who decide platform-vs-everything end up with answers that fit no one’s strategy.
The three real options
White label. The operator rents a brand position on a third-party platform. The platform owner handles licensing (or sublicenses to the operator), integration, payments, compliance technology, and operations. The operator focuses on marketing and brand. Time-to-launch is fast (typically 6-12 weeks for established white-label providers). Operating control is limited.
Turnkey. The operator licenses a managed platform under its own gaming licence, with substantial control over configuration, integrations, and customer experience. The platform vendor provides infrastructure, a base game library via aggregation, payment-provider connections, and compliance technology. The operator runs marketing, CRM, customer service, and strategic decisions. Time-to-launch is moderate (3-6 months). Operating control is meaningful but not absolute.
Proprietary. The operator builds and operates its own platform stack. Aggregator integrations, payment providers, KYC, RG, CRM, and reporting are all integrated under operator-owned engineering. Game content is still licensed (no operator builds slot games), but everything around it is operator-controlled. Time-to-launch from scratch is 12-24 months. Operating control is total.
The right option depends on operator scale, strategic ambition, capital availability, and tolerance for engineering risk.
White label: when it works
White label works when speed-to-market matters more than control, when the operator’s differentiation is marketing-and-brand rather than product-and-experience, and when the operator’s revenue base does not yet justify a proprietary investment.
Use cases that fit:
- A media or affiliate brand extending into operator economics with limited operational appetite
- A team launching a new brand to test market thesis before committing capital
- A group entering a new geographic market where it lacks local infrastructure
- An operator generating less than €5m annual GGR where the proprietary build does not pay back
White label has structural limitations. The operator does not control the technology roadmap; if the platform vendor deprioritises a feature the operator needs, the operator waits. Customer-data ownership is shared or delegated, with implications for marketing autonomy. Switching cost between white-label vendors is high and is often understated at signing.
The economic structure is typically a revenue-share or fixed-fee plus revenue-share, with platform vendor retaining 20-40% of NGR depending on volume and product mix. At scale, this revenue share becomes the dominant cost in the P&L. White-label operators successful at scale often migrate to turnkey or proprietary as the per-NGR cost of the platform exceeds the total cost of building or buying alternatives.
Turnkey: the middle path
Turnkey is where most mid-tier operators land. Time-to-market is acceptable. Cost is moderate. Operating control is sufficient for most strategic decisions. The operator builds its own brand, marketing, and customer relationships while leveraging the platform vendor’s engineering investment.
Use cases that fit:
- An operator with €5m-€100m annual GGR
- A group running multiple brands across multiple markets
- An operator with clear product differentiation that does not require proprietary platform development
- An operator with engineering capability for integrations but not for ground-up platform engineering
Turnkey vendors typically charge a setup fee plus monthly licensing plus per-market or per-product modules. Total cost over five years is meaningful but predictable. Roadmap influence is real but not absolute; the operator gets a voice but does not own the priorities.
The selection criteria for a turnkey vendor matter. Game-aggregator integrations, payment-provider connections, multi-market regulatory support (which jurisdictions are pre-integrated, which require custom work), API quality and documentation, certification status across required jurisdictions, and the financial stability of the vendor are all material. The “choosing an iGaming game aggregator” article addresses the aggregator layer specifically.
The right turnkey vendor for an operator depends heavily on which markets the operator targets. A vendor pre-integrated for the Netherlands, UK, and Sweden is materially better for an EU-focused operator than a vendor pre-integrated for Curaçao and Anjouan only.
Proprietary: when the economics support it
Proprietary investment makes sense when the operator’s scale supports it, when product differentiation is core to the strategic thesis, and when control over the technology roadmap has strategic value beyond cost savings.
Scale threshold: roughly €100m+ annual GGR, or strategic-investor capital that funds the build before scale is reached. Below that threshold, the proprietary build accumulates cost faster than savings.
Strategic justifications: differentiated product features that no aggregator or turnkey vendor offers, customer-experience depth that requires integrated UX work, multi-market expansion where vendor coverage is incomplete, or strategic acquirer-readiness where proprietary technology supports a higher exit multiple.
Engineering reality: proprietary platforms require sustained engineering investment. The build is not the cost; the maintenance is the cost. A proprietary platform that ships in year one and is not invested in for years two through five becomes legacy debt by year three. Operators who underestimate the maintenance commitment end up worse off than they would have been on turnkey.
Examples of operators that have made proprietary work: Flutter (FanDuel, Sky Bet stack), Entain (multiple acquired stacks integrating slowly), Bet365 (proprietary at scale), Kindred before its acquisition. The list is short for a reason: the economics work for the largest operators and rarely below.
Total cost of ownership over five years
The five-year TCO comparison is where most operator decisions are won or lost. Headline pricing on white label looks attractive in year one and looks expensive by year five at scale. Headline pricing on proprietary looks expensive in year one and looks proportionally cheaper if the operator scales but absurd if the operator does not.
A directional five-year TCO for a mid-tier operator targeting €30m annual GGR by year five (illustrative figures, not your specific deal):
White label: Setup minimal. Year-one revenue share at 25-35% of NGR. Years two through five same revenue share applied against growing NGR. Five-year cumulative platform cost at the assumed GGR trajectory: €15m-€25m. Plus the operator carries marketing, CRM, customer service, content licensing pass-through.
Turnkey: Setup €200k-€500k. Monthly licensing €30k-€80k depending on modules and markets. Per-NGR transaction or revenue-share components 5-15% on top. Five-year cumulative platform cost: €5m-€12m. Plus operator carries marketing, CRM, customer service, content licensing, and most integration work.
Proprietary: Build year-one €3m-€10m depending on scope. Engineering team of 10-30 people sustained across five years at €1.5m-€5m per year fully loaded. Plus integration costs, hosting, certification, and ongoing roadmap. Five-year cumulative platform cost: €15m-€40m. The operator owns the technology asset.
These numbers vary widely by operator. The point is the shape of the curves: white label cost rises with revenue, turnkey cost rises modestly with revenue and markets, proprietary cost rises with engineering investment regardless of revenue. The crossover point between turnkey and white label sits around €15m-€30m annual GGR. The crossover between turnkey and proprietary sits much higher.
The strategic-control question
TCO is half the question. The other half is strategic control.
Three control dimensions matter. Roadmap control: which features ship when. White label has none, turnkey has influence, proprietary has full control. Customer-data control: who owns the customer record, who controls marketing access, who can extract data on exit. White label often has shared or delegated control; turnkey gives the operator most rights with vendor access for support; proprietary gives full control. Differentiation control: ability to ship product features competitors cannot match. White label produces a product the operator’s competitors can also rent. Turnkey produces a product configurable by the operator but built on shared foundations. Proprietary produces a product the operator alone owns.
For operators whose strategic thesis is “we are a great brand executing on standard product,” white label or turnkey are appropriate. For operators whose thesis is “we have a differentiated product experience that drives retention,” proprietary is the only option that delivers it.
Most operators who say they have “differentiated product” actually have differentiated marketing on standard product. That is fine. White label or turnkey serves them adequately. The mistake is paying for proprietary on the assumption that the differentiation is technology-driven when it is actually marketing-driven.
Decision framework
Five questions to answer:
-
What is the operator’s annual GGR target by year five? Below €15m, white label is most economic. €15m-€100m, turnkey usually wins. Above €100m, proprietary becomes economically defensible.
-
Is the differentiation marketing-led or product-led? Marketing-led: white label or turnkey. Product-led with engineering capability: turnkey with deep customisation, or proprietary.
-
How many markets does the operator target by year three? One or two: turnkey with the right vendor pre-integration. Three to five: turnkey with multi-market vendor or proprietary. Five-plus: proprietary unless a turnkey vendor has comprehensive pre-integration.
-
What is the engineering team’s existing capability? No engineering team: white label or turnkey only. Five to ten engineers: turnkey with integrations. Twenty-plus engineers and product leadership: proprietary becomes feasible.
-
What is the strategic acquirer-readiness horizon? A three-to-five-year sale path with proprietary technology supports higher multiples than the same business on white label, holding everything else equal. The technology asset is part of the enterprise value.
Operators who answer these questions honestly arrive at a clear option. Operators who answer aspirationally end up paying for a build they cannot maintain or renting a platform that constrains them.
Frequently asked questions
Can an operator start on white label and migrate to turnkey or proprietary later?
Yes, but the migration is non-trivial. Customer data extraction, account migration, customer-experience continuity, and licence-conditions all require careful planning. Operators planning a future migration should negotiate the exit terms at white-label signing. Most do not, and pay later.
Is open-source iGaming platform a viable option?
Limited. Open-source iGaming platforms exist but lack the regulatory certifications and pre-integrated supplier ecosystem of commercial turnkey vendors. The cost saving on licensing is offset by the engineering investment required to bring an open-source base to certification. Use cases are narrow.
How does the choice affect multi-market expansion?
Materially. White label expansion into a new market typically requires using the white-label vendor’s licence stack in that market (if available) or migrating to a different vendor. Turnkey expansion is straightforward if the vendor is pre-integrated for the new market. Proprietary expansion gives full control but requires internal engineering investment per market.
What about hybrid stacks?
Common and often correct. Operator-owned customer-account, CRM, and reporting layers integrated with a turnkey core platform is a defensible hybrid. The operator owns what differentiates and rents what does not. The complexity is integration management.
How long should the build-vs-buy evaluation take?
For a serious operator decision, three to six months from initial scoping to vendor selection or build commitment. Operators who shortcut this to weeks usually pay later in vendor mis-fit or scope creep.
Working through a build-vs-buy decision? I work with operators on platform-strategy decisions and the architecture choices that compound across multi-market portfolios. Request a conversation via WhatsApp.
Related: Multi-market strategy · Choosing an iGaming game aggregator · iGaming KPIs that matter to your CFO