Stop renting the platform you built the business on.
Revenue-share white-label costs grow with your volume for as long as the contract runs. A software licence you own does not.
This page is for operators weighing a white-label or turnkey contract against owning the platform outright: what the two models actually cost as volume grows, what moves across when you leave one, what has to be re-contracted, and where a white-label is still the better answer.
Same casino. Very different arrangement.
Both models put a working platform under your brand. What differs is who holds it, what it costs as you grow, and what happens on the day the relationship ends.
Written from the arrangements operators describe to us. Contracts differ, so the one in front of you is the one that matters — these are the clauses worth reading before signing.
Revenue share grows with volume. A fixed software price does not.
The comparison is not "cheap versus expensive" — it is a variable cost against a fixed one, and which wins depends entirely on your volume and how long you intend to operate.
Work out your own break-even first
Take your projected monthly gross gaming revenue, apply the revenue share you have been quoted, and multiply by thirty-six. Compare that with a one-off licence plus three years of hosting and the engineers to run it. The crossing point is usually somewhere between modest and mid-sized volume — and it is your number, not ours, so do it before evaluating any quote including ours.
The percentage is charged on your best months
Revenue share scales with success rather than with cost to serve. The month a campaign works is the month the platform bill is largest, and nothing about serving that traffic became proportionally more expensive for the vendor.
Owning has costs a quote does not show
Infrastructure, monitoring, and a team that can operate a platform of this size — several engineers, not one. We would rather you plan for that now than discover it in month two; the point of the comparison is the total, not the licence line.
The exit has a price in one model only
Leaving a white-label means migrating players, balances and history off a platform you do not control, on terms written before you had leverage. Leaving a software vendor means you keep running the software you already hold, and simply stop buying support.
What moves with you, and what has to be rebuilt.
The platform is rarely the hard part of a migration. The data and the contracts are, and they run on different clocks — which is why this is worth establishing before a launch date is promised to anyone.
Migrates, given a cooperative export
- Player accounts and profiles
- Wallet balances
- Transaction and game history
- KYC status and verification records
- Bonus balances and wagering progress
- Agent and affiliate structures
Has to be re-contracted in your name
- Game provider agreements
- Payment provider and PSP agreements
- The gaming licence for each market
- Domain, DNS and CDN arrangements
- KYC and AML vendor accounts
How cleanly the first column moves depends on what your current provider will export, and that is a question to ask them early — it affects the timeline more than the technical work does. The second column is contract work running in parallel, and it usually sets the launch date.
The move can be made in stages.
The migration that goes badly is the one that happens in one night for the whole business. The common pattern is quieter: a new brand launches on the owned platform first, the team learns the software while nothing is at stake, and the existing brand moves once the operation has proven itself. Both run in parallel for as long as that takes — they are separate systems with separate contracts, and neither knows about the other.
Cases where renting is the right answer.
This page argues for one model, so here is the argument against it — an operator who reads only the case for owning will discover the rest at their own expense.
You are testing whether the business works at all
At low volume a revenue share costs less than a platform plus a team, and it can be stopped. Buying software to find out whether a market responds is expensive research.
You have no engineering team and do not want one
Owning the source is only an advantage if somebody reads it. A platform of this size needs several engineers to operate; without them, a vendor doing it for a percentage is doing real work for that percentage.
You need to be live in weeks with no in-house capability
A white-label can put a brand in front of players faster than any deployment you run yourself, because the platform, providers and payment rails already exist on their side.
Your licence and providers already sit with the vendor
If the vendor holds the licence and the provider contracts, leaving means rebuilding both. That is a commercial project, not a technical one, and it should be planned rather than discovered.
Questions about making the switch.
What operators ask once the comparison stops being abstract.
No, and the difference shows up in the contract rather than in the software. A white-label is a service you rent: the vendor operates the platform, holds the data and takes a share. Here you receive a full copy of the code, deploy it on your own infrastructure and pay no percentage of revenue. Support and new modules are a separate service you can buy or stop buying without the platform changing hands.
That depends on your volume and on scope — individual modules, the full platform, or the platform with our engineers alongside your team — so a figure on a web page would mislead most readers. What we suggest is bringing your own numbers: projected GGR, the share you pay today, and the term you are planning for. One call is enough to establish whether the arithmetic favours owning, and if it does not, we will say so.
Player accounts, balances, transaction history, KYC status and bonus progress can all be migrated. How cleanly depends entirely on what your current provider will export and in what format — that is worth establishing with them before any date is committed to, because it drives the timeline more than the technical work does. Game and payment provider agreements do not migrate; they are re-contracted in your name.
The software can be deployed quickly — it ships containerised with its own CI/CD and migrations. What sets the date is the contract work running alongside it: providers to re-sign, payment rails to open in your name, and the licence for each market. Operators who plan for that sequence, rather than for a technical cut-over, are the ones whose launch dates hold.
Yes. Several engineers, not one — the services are small and consistent, but there are 35+ of them and no single person carries all of it, ours included. If you do not have that team and do not intend to build one, a white-label is genuinely the better arrangement, and we would rather say so now than after a purchase.
Callisto is a product rather than a bespoke build, so the same code goes to more than one operator, and nothing in how it is sold reserves it for one. Every deployment runs on its own infrastructure with its own data, and no deployment can see another. Exclusivity in a market is a commercial question rather than a technical one — raise it before signing rather than assuming either answer.
Bring your numbers, not just your questions.
Tell us your projected volume, the revenue share you pay today and the markets you operate in. We will work through the comparison with you — including the case where staying where you are is the right answer.
We reply within a day, usually the same one.
See what is delivered