iGaming software providers,
compared.

Compare on what actually matters

Logos and feature lists don’t tell you who will get you live and keep you up. Compare providers on the five dimensions below — then see our buyer’s guide and how-to-choose checklist.

Four kinds of provider — and what each one actually sells you

“iGaming software provider” covers four different businesses that make money in completely different ways. Before you compare features, work out which category a vendor sits in — the category decides the economics, the lock-in, and who owns the player at the end. A slick demo tells you none of that.

Turnkey and white-label platform suppliers

These firms rent you a ready-built casino or sportsbook. You get a wallet, a games lobby, payment connectors, a back office, and often a licence to trade under — sometimes in weeks. The commercial model is almost always revenue share: a percentage of your gross gaming revenue, every month, for as long as you run on their stack. It is the fastest way to a live product and the cheapest to start. The trade-off is that you are a tenant. The platform, the player database, and frequently the licence belong to the supplier, and the rev-share does not taper when you reach scale. This is the model our turnkey platform guide breaks into its three tiers.

Aggregators

An aggregator is not a platform at all — it is one integration that gives you thousands of games from hundreds of studios through a single API and one wallet contract. You still need a platform to plug it into. Aggregators solve content, not operations: they handle game certification, studio onboarding, and a unified game-transaction feed, and they take a cut of the revenue on the games routed through them. Most operators use one regardless of who builds their platform, because integrating studios one by one is a standing engineering cost. Judge an aggregator on catalogue breadth, wallet integration model, and how cleanly it reports round-level data — not on anything resembling platform features.

Generalist software agencies

A generalist agency will build whatever you brief — a marketplace, a fintech app, a gambling site. They are capable engineers, but gambling is not their specialism, and it is a domain where the hard parts are invisible in a demo: bonus abuse, responsible-gambling triggers, jurisdiction-specific reporting, RNG certification, settlement edge cases. A generalist can write the code. What they usually cannot do is tell you what the regulator will ask for before you have paid them to find out. You own the result, which is the upside — but you are also funding their learning curve on your timeline.

Specialist custom developers

A specialist studio builds you an owned platform — your code, your database, your IP — with gambling domain knowledge already in the room. There is no revenue share and no per-brand licence tax; the build is a project cost, not a permanent tenancy. This is the slowest and most expensive route to a first launch, and honestly the wrong one for a small single-market operator just testing demand. It becomes the right one when you have volume, a product you want to differentiate, multiple brands or markets, or an intention to sell the company — because owned IP is the asset a buyer pays for. This is where a dedicated iGaming development team earns its cost.

The five axes that separate providers

Once you know the category, five axes do the real discriminating. Score every shortlisted provider on each, and the right answer for your situation usually falls out.

1. Ownership model

Do you own the platform or licence it? Owned means a fixed build cost and no revenue share. Licensed means a fast start and a permanent cut of your revenue. Neither is wrong — but the crossover point, where owned works out cheaper, is a volume question. Model it before you sign, not after.

2. Specialism

Is gambling the provider’s core business or a vertical they will take on? Specialism shows up in the things nobody demos: how bonus logic resists abuse, whether the reporting already maps to a regulator’s return format, how the wallet handles a reversed transaction mid-session. Generalists reach these problems in production; specialists designed for them.

3. Compliance depth

Is compliance engineered into the data model or bolted on before certification? KYC, AML and responsible-gambling controls that are retrofitted tend to be brittle — they pass the audit and then leak at the edges. Engineered compliance means identity checks, affordability triggers, self-exclusion and audit logging sit in the transaction path, not in a layer over it. Ask how a self-exclusion propagates across brands; the answer is revealing.

4. Where your data and player relationship live

On a rented platform, the player database is often the supplier’s and your access to it is contractual. On an owned build it is yours outright. This matters most on the day you want to leave, launch a second brand, or do anything with your own player data that the platform owner would rather you did not.

5. Exit and lock-in

What does leaving cost? With a rented platform, migrating players, balances and history off the supplier’s stack is the hardest project you will ever run — which is exactly why the rev-share holds. With owned code there is nothing to leave; you already have it. Price the exit at the start, because it is cheapest to negotiate before you are dependent.

Three questions that expose the real difference

Sales decks converge; answers to blunt operational questions do not. Three questions separate the categories faster than any feature grid.

Whose licence do you operate under?

If the answer is “ours”, you are a sub-licensee on someone else’s permit — convenient at launch, but your right to trade depends on their standing with the regulator, not yours. If the answer is “your own”, you carry the compliance burden and the freedom that comes with it. There is no universally right choice; there is only knowing which one you are buying. Our guide to iGaming licensing covers what holding your own entails.

Who owns the wallet and the player data?

The wallet is the heart of the platform — it holds balances, drives bonuses, and records every transaction a regulator can later ask about. Whoever owns the wallet owns the operation. On a rented stack it is the supplier’s; on an owned build it is yours. Ask this early, because it decides everything downstream about data, reporting and exit.

Can you leave, and what does it cost?

Ask for the offboarding clause before you sign the onboarding one. A provider confident in its product will tell you plainly how a migration works and what it costs. Evasion here is the single clearest signal of lock-in.

These three questions decide the shape of the deal. The full due-diligence list — team seniority, certification track record, security posture, SLAs — lives in our how-to-choose checklist, and the rent-versus-own economics are worked through in development vs white-label. This page compares the types of provider; those two pages are the decision and the checklist that follow from it.

Where a custom build fits — and where it honestly does not

We build owned, custom platforms, so treat this as an interested opinion — but a candid one. Custom is not the default answer, and pretending it is would waste your money.

A custom build is wrong when you are a small operator in a single market testing whether demand exists at all. At that stage, speed and low upfront cost beat ownership, and a turnkey or white-label platform gets you live to learn. Spending a build budget to prove an unproven market is the expensive way to fail.

A custom build earns its cost when one or more of these is true: you have volume, so a permanent revenue share now dwarfs a one-off build; you want a product that does something the rented stacks cannot; you run multiple brands or markets and the per-brand licence tax compounds; or you intend to sell the company, and the owned platform is the asset a buyer is actually paying for. In those cases the questions above all point the same way — toward owning the IP, the wallet, the data and the exit. If that is where you are, our portfolio shows the kind of platforms we build, and a scoping call will tell you honestly whether custom is right for you yet.