Casino operators can source original games in four ways: license hosted games from a studio, license white-label originals rebranded for their casino, license a ready-made game together with its source code, or build a custom game in-house or with a development partner. Four questions decide the route: how fast the games must go live, whether you are willing to share their revenue for as long as they run, how much control you need over math, limits and roadmap, and whether you need games no other casino can offer.
This guide compares the four paths for founders, Heads of Product and CTOs. It covers what each path actually gives you in rights, how the costs behave over time, who carries certification and supplier-licensing obligations, and how to choose. If you are still deciding whether originals belong in your lobby at all, start with what casino originals are and how the four game types differ.
Build, license or buy: the short answer
- License hosted games when speed and breadth matter most. Integration is quick, but you share the games’ revenue for as long as they run, and the studio controls the math and the roadmap.
- License white-label originals when you want games that look like yours without building or hosting them. The same game runs at other casinos under other brands, and the supplier keeps the server, the code and usually a recurring fee.
- License a ready-made game with source code when originals earn, or will earn, a meaningful share of your GGR and you can run game servers. You stop sharing revenue with the supplier and take on hosting, operations and, in regulated markets, the build you certify. In most deals “buying” means a license to the code, not ownership of the game.
- Build a custom game when you need a mechanic or exclusivity that no catalog offers and can fund math, development, testing and long-term maintenance.
- No path removes compliance work. Certification follows the specific build in each market, and supplier obligations follow who makes, supplies, installs and adapts the software, not only who hosts it.
This is a decision about game content. The platform decision (building, buying or licensing the casino platform itself) is a separate question with its own trade-offs.
The four ways to source casino originals
1. License hosted games from a studio
The studio builds the game, owns its intellectual property (IP) and runs it on its own remote game server (RGS). You connect it through the studio’s API or, more often, through an aggregator that bundles many studios behind one integration. The game appears under the studio’s brand, and you configure only what the studio exposes: bet limits, currencies and, with some studios, an RTP variant from an approved list.
You pay a share of the gross gaming revenue (GGR) the game generates, often with setup or minimum monthly fees, for as long as the game is live. When the contract ends, the game disappears from your lobby.
Strictly speaking, studio-branded fast games are licensed content rather than originals, because players see the studio’s brand, not yours. They are still the baseline that every other path is measured against.
2. License white-label originals
A B2B studio supplies fast games (crash, dice, plinko, mines and similar) that are rebranded for each casino so they look native to its lobby. The games still run on the supplier’s RGS, and the supplier keeps the code. You get your logo, colors and theme, plus the configuration options the supplier offers.
The same game runs at other casinos under other brands. Commercial terms differ by supplier, but they usually combine setup or branding work with a recurring fee or a revenue share. This path gives you the look of in-house games at a low commitment, with the supplier still in control of math, updates and the game’s future.
3. License a ready-made game with source code
A developer licenses you a finished game together with its source code. The game is deployed on your infrastructure, connected to your player accounts and wallet, and branded for your casino, either by your team or by the developer as part of the deal. Payment is usually a one-time license fee, sometimes with optional paid support, and no share of GGR goes to the developer.
In exchange, you take on what the supplier used to do: hosting, monitoring, incident response, security patching and, where your license requires it, certification of the build you run. The game stays on your servers under the license terms even if you stop buying support.
This is the model behind OmiSoft’s ready-made white-label casino games and originals (OmiSoft is the publisher of this guide). The key nuance is in the word “buy”: in most source-code deals you receive a license to use and modify the code, not ownership of the game. The next section explains the difference.
4. Build a custom game
You build the game with your own team or commission a development company. You decide the mechanic, the math model, the presentation and the release plan, and the game is exclusive to you by default. In-house, the IP is yours. In a commissioned build, ownership is whatever the contract says: an assignment of IP to you or an exclusive license for an agreed scope and term. If exclusivity is the reason you are building, check which of the two the contract grants: an exclusive license can end after its window, while an assignment does not.
A custom build carries the full cost stack: game design, the math model and its simulation, the game client, the game server, wallet integration, QA, certification for each regulated market and maintenance for as long as the game is live. A reskin of an existing engine is a different, lighter production model and should not be priced or scheduled as a new original.
What you actually get: hosted license, code license, exclusive license or IP
“Buy” and “own” are used loosely in game deals. In practice there are four levels of rights, and the contract decides which one you get.
| Rights level | What you receive | Where the game runs | Can you change the code? | Can the supplier license it to others? | If the contract ends |
|---|---|---|---|---|---|
| Hosted license | Access to a game running on the supplier’s server | Supplier’s RGS | No, only the settings offered | Yes | The game is switched off |
| Non-exclusive source-code license | The code and the right to use and modify it under the license terms | Your infrastructure | Yes, within the license | Yes | Depends on the license: check whether rights are perpetual and survive the end of support |
| Exclusive license | The same rights, and the supplier may not license the game to others within the agreed scope | Your infrastructure or the supplier’s | Depends on the contract | No, within the agreed territory, period or vertical | Exclusivity ends at the end of its term; usage rights follow the license |
| IP assignment | Ownership of the game | Your infrastructure | Yes | No, unless you license it back | You keep the game |
Most source-code purchases are the second level. That is a good deal for many operators, because it removes the revenue share and gives you a finished game you can run and extend, but it is not ownership: the developer can license the same game to other casinos. If you need a game no one else can offer, you need an exclusive license or an IP assignment, which usually means a custom build.
Whichever level you choose, get it in writing, along with what the code package includes: client, server, math model and simulation results, build scripts, documentation and a list of third-party components whose licenses you must also respect.
Build vs license vs buy: the decision matrix
| Hosted studio license | White-label originals | Source-code license (ready-made) | Custom build | |
| Time to market | Fastest: integration only, often through an aggregator you already use | Fast: branding and integration | Moderate: branding, integration and deployment on your infrastructure | Slowest: design, math, development, simulation and testing |
| Upfront cost | Low: setup and integration | Low to moderate: setup and branding | One-time license fee, integration and infrastructure setup | Highest: the full development budget |
| Recurring cost | Revenue share on the game’s GGR, often with minimum fees | Recurring fee or revenue share | Hosting, operations and optional support; no revenue share | Team, hosting and maintenance |
| Who runs the game server | The studio | The supplier | You | You, or a partner under contract |
| Branding | The studio’s | Yours | Yours | Yours |
| Control of math, RTP and limits | Settings the studio offers | Settings the supplier offers | Within the approved math models; code changes are possible but create a new build | Full, within regulation |
| Roadmap | The studio’s | The supplier’s | Yours, from a finished base | Yours |
| Exclusivity | None | None by default | None by default | Yes, by design or by contract |
| IP | The studio’s | The supplier’s | The developer’s; you hold a license | Yours, or as assigned by contract |
| Certification for regulated markets | The studio certifies and maintains its builds | The supplier certifies its builds | The build you run; who submits it depends on the market and the contract | You |
| Exit and lock-in | The game leaves with the contract; replacing it means a new integration | Same as hosted | The game stays on your servers under the license | Fully yours; the risk shifts to keeping the team and the knowledge |
| Best fit | A fast launch with a broad catalog | A branded look quickly, with a low commitment | Originals that already carry real volume, and a team that can run infrastructure | A unique mechanic or true exclusivity, with budget and a strong team |
Two factors usually decide the outcome. The first is how much GGR the originals will generate: the more they earn, the more a revenue share costs and the faster a fixed-cost path pays back. The second is operational capacity: running game servers around the clock is real work, and a team that cannot do it, or pay someone to do it, is better served by a hosted model. Most lobbies end up mixing paths: hosted studio content for breadth, plus a set of owned or white-label originals for the casino’s own identity.
How the cost shape differs over three years
Game licensing prices vary widely and are rarely published, so a fair comparison starts with where the money goes and how each cost line behaves over time, not with a single headline price.
| Cost line | Type | Hosted studio license | White-label originals | Source-code license | Custom build |
|---|---|---|---|---|---|
| Integration and setup | Fixed, at launch | Yes | Yes | Yes | Part of the build |
| Branding and art | Fixed, at launch | Not applicable | Yes | Yes | Full art production |
| License or development fee | Fixed | None or small | Setup fee | One-time license fee | Full development budget |
| Share of GGR to the supplier | Variable, grows with revenue | Yes | Usually | No | No |
| Minimum monthly fees | Recurring | Common | Sometimes | No | No |
| Hosting and game-server operations | Recurring | Supplier | Supplier | You | You |
| Maintenance, updates and security fixes | Recurring | Supplier | Supplier | You, or paid support | You |
| Certification and re-testing in regulated markets | Per market and per change | Supplier, for its builds | Supplier, for its builds | The build you run | You |
The core trade is a cost that grows with revenue against a cost that does not. Under a revenue share, the fee rises with every round played. Under a one-time license, the fee is fixed, and what grows instead is your hosting and operations bill, usually more slowly than the revenue itself. The calculation to run is simple in structure:
- Estimate the monthly GGR that these specific games will generate. Use the games’ own GGR, not the casino’s total.
- Multiply it by the revenue-share rate you would otherwise pay. That is the monthly fee you avoid.
- Subtract the extra monthly cost you take on: hosting, monitoring, support and a share of expected certification work.
- Divide the one-time cost (license fee, integration and setup) by the result. That is the payback period in months.
If originals are a small or uncertain part of your mix, the revenue share works like cheap insurance: you pay little and keep no infrastructure. If they are a growing, predictable part, the longer the horizon and the higher their GGR, the more a fixed-cost path tends to come out ahead over 36 months, as long as hosting, support and certification are counted honestly. A full worked cost model with sensitivity to each input belongs to a separate business case.
Who carries certification and supplier licensing in each path
Three different obligations are easy to mix up when comparing paths:
- Operator licensing authorizes your casino to offer gambling in a market. It stays with you in every path.
- Game certification is an accredited lab’s evaluation of a specific game build against a market’s technical standard. It follows the build that players actually use.
- Supplier licensing applies in some markets to companies that make, supply, install or adapt gambling software, or that run games and game systems for operators.
The sourcing path changes the second and third obligations, not the first.
Hosted paths. The studio or white-label supplier runs the RGS, so in markets that require it, the supplier gets its builds certified and holds the supplier license or registration. Your job is to confirm that the supplier is licensed where you operate and that the certified build is the one you integrate.
Source-code path. A common assumption is that when code changes hands, the developer drops out of regulation. Regulators do not frame it that way. In Great Britain, section 41 of the Gambling Act 2005 makes it an offense, in the course of a business, to manufacture, supply, install or adapt gambling software without an operating license. The Gambling Commission’s guidance on what counts as gambling software adds that the final supplier to a licensed operator needs a gambling software license even if it does no development itself, and that anyone who installs gambling software on a licensed operator’s system needs one too. Licence condition 2.2.1 requires licensed operators to use software manufactured, supplied, installed and adapted by license holders.
In Ontario, the AGCO’s guide for internet gaming suppliers lists suppliers that “manufacture, develop, provide and/or run games and game systems” among those that may need to register as gaming-related suppliers. Its go-live compliance guide applies different sets of standards to suppliers that run critical gaming systems and to those that develop but do not run them. In other words, delivering code instead of hosting it can change which obligations apply. It does not by itself remove them.
Custom builds. When a game is commissioned, the question of who needs the supplier license can depend on who controls the product. The UK Commission says it looks at which company is responsible for design, change approval, acceptance and compliance testing, which company retains the IP, and what the contract says. Broadly, if you buy a finished product, the developer needs the license; if you buy time and expertise and keep control of the design, the license sits with you.
Certification in every path. Wherever the game runs, the build offered in a regulated market is the one that gets tested. In Ontario, for example, the AGCO’s go-live guide asks operators to confirm that every game will be certified, before it is deployed, by an independent test lab registered with the AGCO or approved by the Registrar. With source code, any change to the game logic or math produces a new build, so plan which changes trigger re-testing before you start customizing.
Requirements vary by jurisdiction, and legal counsel should confirm them for each market before you sign, especially when the developer brands, adapts or installs the game for you.
Which path fits your casino
Work through these questions in order:
- Do you need a mechanic or exclusivity that no supplier offers? If yes, choose a custom build, commissioned if you have no in-house game team. If no, continue.
- Will originals be a meaningful and growing share of your GGR in the next 12 to 24 months? If no or not sure, start with hosted or white-label games and revisit the decision once you have data. If yes, continue.
- Can you, or a partner under contract, run game servers around the clock? That means hosting, monitoring, incident response and security updates. If no, stay with a hosted model or license source code with paid support. If yes, continue.
- Do the games need to look native to your brand? If yes, a source-code license gives you that without a revenue share. White-label originals give you the same look if you prefer not to run the servers.
- Will you operate in regulated markets? Then for whichever path you pick, plan the certification of each build and confirm supplier obligations in each market before you commit.
Typical situations map to the paths like this:
| Operator situation | Usual starting point |
|---|---|
| New crypto casino that must launch in weeks | Hosted studio content for breadth, plus originals bundled with the platform or white-label originals |
| Growing hybrid casino where originals already carry real volume | Source-code licenses for the formats that earn most |
| Operator with a signature mechanic or a brand-led game concept | Custom build |
| Operator entering regulated markets | Any path with documented certification support; confirm supplier licensing first |
Questions to settle before you sign
These questions follow from the sourcing model itself. Full supplier due diligence (math documentation, fairness method, security and track record) is a separate exercise.
- Which rights level does the contract grant: hosted, non-exclusive code, exclusive or IP assignment?
- For a code license: what exactly is delivered (client, server, math model, simulation results, build scripts, documentation), and which third-party components carry their own licenses?
- Are the code rights perpetual, and do they survive the end of a support contract?
- May you modify the code, and may another company maintain it for you?
- Who provides updates and security fixes, on what terms and response times?
- For a hosted game: what happens to open rounds, player balances and round logs if the contract ends, and how much notice is given?
- Which settings can you change without touching the math, and which changes create a new build that needs re-testing?
- Who prepares and pays for certification in your markets, and in whose name is each certificate issued?
- For an exclusive deal: what is the scope (territory, period, verticals), and what happens when the exclusivity window ends?
Where OmiSoft fits: the source-code path
OmiSoft works in the third path: ready-made games, delivered with their source code, branded for your casino and integrated with your platform. It is neither a revenue-share license nor a build from scratch.
- Catalog. 22 ready-made games in four groups: instant and crash games, card and table games, slots and multiplayer games. You can see them in our white-label casino games and originals catalog.
- License model. You get a non-exclusive license to each game together with its full source code. The game runs on your infrastructure under your casino’s brand, and the same game can also be licensed to other operators.
- Payment. A one-time license fee, with optional paid support. No share of your GGR goes to OmiSoft. Pricing is set after we review the scope.
- Branding and integration. We customize each game’s look for your casino and connect it to your player accounts, wallet and backend.
- Configuration within approved math. How far the math can be configured depends on the game. In Cross the Lake, for example, operators choose from risk profiles that set trap density, the multiplier curve and a target RTP, and each profile needs its own approved math model.
- Testing. Game math, logs, configuration controls and documentation can be prepared for independent testing. Certification is issued only by an accredited laboratory after its evaluation, and supplier obligations in each market should be confirmed with legal counsel.
- Exclusivity. If you need a title no other casino can offer, that is a custom build through our casino game development services, with code and IP rights defined in the project agreement.
Operators launching a new crypto casino can also get originals with the platform: the Custom package of our white-label crypto casino includes eight original games chosen from the same catalog.










