Who should commission a custom platform
A group that will own the code and the team that runs it. Typical cases: an operator whose product mechanics no licensed platform supports, a group running several brands across licences that no single vendor covers, an operator whose revenue share already costs more than an engineering team, or a company that plans to license the platform to others. If none of these applies, licensing an existing product is the faster route. The casino engine page covers that option, including what you can configure without owning the code.
The direct answer on cost: a custom build is measured in engineering-years and certification cycles, not in a setup fee. One vendor's published 2026 estimate puts the core components of a casino and sportsbook platform at 8,400 to 16,100 engineering hours, and a fully custom build at 12 to 24 months to market. That is a market estimate from another provider, not our quote. Its value is the proportion: the wallet, the sportsbook engine and the front end take about half of the hours.
When build beats buy
| Your situation | Build | Buy or license |
|---|---|---|
| Need to be live within a year | Rarely possible once certification is counted | Turnkey runs up to four months with certifications in place |
| Product mechanics no platform supports | Yes: this is the main reason to build | Only if the vendor will build it into their roadmap, on their terms |
| Revenue share above what a team costs | Worth modelling; the white label page shows how fast share outgrows fixed costs | A fixed licence fee closes much of the gap without a build |
| You plan to sell the platform to other operators | Yes, and you then need supplier licences of your own | Not possible on licensed code |
| No engineering team to own it after handover | No: gambling code that nobody maintains falls behind the next rule change | Yes |
| No licence chosen yet | Not yet: the licence sets hosting, reporting and certification | Start at gambling licensing |
Where the cost goes
The build is the visible part. Four lines decide the total, and two of them are not code at all.
| Cost line | Why it grows | What fixes it in scope |
|---|---|---|
| Wallet and ledger | Every game round, bet, bonus and payment touches it, and certification tests its failure paths | Idempotency, rollback and minor-unit rules written into the specification before the first sprint |
| Sportsbook engine | Settlement, resettlement, cash-out and feed mapping, each with edge cases | Name the feeds and markets at scoping; replay a season of results as an acceptance test |
| Certification | Each licence and each test lab is a cycle of submission, findings and fixes, and later changes may need retesting | Name the target licences and the technical standard per licence in the contract |
| Running it | Hosting, on-call, security audits, regulatory change and the next certification | Price year two before you sign year one |
The fourth line is the one buyers leave out, and it is permanent. A custom platform does not stop costing money at handover; the cost moves from our invoice to your payroll.
What goes in the scope document
- Licences and markets, with each regulator's hosting, reporting and player-protection rules attached as requirements, not as background.
- Technical standards, named per licence. GLI publishes GLI-19 v3.0 for interactive gaming systems and GLI-33 v1.1 for event wagering systems, and many jurisdictions use GLI standards as a base for their own.
- Integrations: game aggregation and direct studios, odds feeds, PSPs, KYC, CRM, each with the party that holds the contract.
- Non-functional targets: peak concurrency, load-test multiple, recovery objectives, data residency.
- Acceptance criteria for every milestone, written as tests that can pass or fail.
- Ownership: what transfers, what is licensed, and when.
Intellectual property: what transfers and what does not
Ask for this table in the contract, filled in, before the first payment.
| Item | Usual position | What to check |
|---|---|---|
| Code written for you | Assigned to you | On final payment or per milestone, and whether escrow holds it until then |
| The developer's existing components and libraries | Licensed, not assigned | A perpetual, irrevocable licence that survives the end of the relationship |
| Third-party and open-source software | Under its own licence | A list of every component and its licence terms |
| Build pipeline, infrastructure code, test suites | Often forgotten | Named as deliverables; without them the code cannot be rebuilt or re-certified |
| Certification reports and lab correspondence | Often held by whoever submitted | Copies to you, and the right to resubmit under your name |
| Studio, feed and PSP contracts | Never part of the code | In your name from the start, so they survive a change of developer |
Certifying code that nobody has certified before
A licensed platform arrives with reports for the markets it already serves. Custom code arrives with none, and every change after launch raises the question again. The UK Gambling Commission's testing strategy is a clear model of how regulators think about this, even where you do not hold a UK licence. New games and RNGs may be released only after testing by an approved test house. Updates that do not affect game fairness can go out under the licensee's own change control. A change to a remote gaming server or RNG that could affect hundreds of games needs a representative sample retested. And the change control itself is audited every year by an approved test house.
| Licence | What custom code must clear |
|---|---|
| Curaçao | Testing by a lab accredited to ISO/IEC 17025 with online gaming systems, RNG, fairness and RTP in its scope |
| Finland | Systems and RNGs assessed by an approved body before launch; from 1 July 2028, software only from a Finnish gambling software licence holder |
| Isle of Man | Player registration on island servers, and the technical description of the system the Commission expects in the application file |
| Gibraltar | B2B platform suppliers pay £85,000 a year under the Gambling Act 2025 |
| Tobique | RNG certification, infrastructure disclosure and a bi-weekly encrypted backup to the Commission's provider |
The Finnish and Gibraltar rows raise a question a licensed platform never does: once you own the code, who is the supplier? Put it to your licensing counsel before the contract is signed, not after the build. We prepare the technical side of the certification file either way.
Acceptance
Acceptance should be a list of tests, run in the target configuration, with the result recorded. A demo is not acceptance. The tests we run before a turnkey launch translate directly: a settlement replay against a season of historical results, a load test at ten times forecast peak, the wallet edge cases a certification lab will script, and the regulator's own reporting format produced from live data. Link the final payment to the certification report rather than to delivery of the code, so the developer carries the fixes the lab asks for.
Where custom builds go wrong
- Certification left to the end. Lab findings land on code that is already frozen, and the launch date moves by a submission cycle each time.
- Ownership without the means to use it. The source code transfers, but the pipeline, infrastructure code and test suites do not, so nobody else can rebuild it.
- A team that leaves with the developer. The operator owns code it cannot change, in an industry where rules change every year.
- Scope written as features, not licences. The platform works but fails a market rule nobody listed, such as Finland's 5× retention-only bonus cap.
Questions to put to any developer, including us
- Which components are written for us and assigned, and which are your existing code licensed to us?
- Which technical standard and which lab per licence, and who submits?
- Is the final payment tied to the certification report?
- What do we receive besides source code: pipeline, infrastructure code, test suites, documentation?
- How is knowledge handed to our team, and over how long?
- Who is the supplier of record in each licence once we own the code?
Frequently asked
Can we start on a licensed platform and build later?
Yes, and it is the lower-risk order. You launch, learn which parts actually limit you, and replace those first. A migration then moves players and balances onto the new code.
Can you build only part of the platform?
Yes. Many projects replace one module, such as the front end, the bonus engine or reporting, and keep the rest. See front-end development for the most common case.
Do we need our own test lab relationship?
Not at first. The lab can be contracted by us or by you; what matters is that the reports and the right to resubmit end up with you.
What does year two cost?
Your engineering team, hosting, security audits and every retest that a change triggers. Ask any developer to price it alongside the build, because it is the part that does not end.