Custom casino platform development: the parts, the decisions and the order of work

What does a casino platform consist of?

Build, rent or split?

Three routes exist: rent a whole platform, build your own, or split, renting some layers and owning the rest. Published figures help set the scale.

SOFTSWISS's cost calculator says "it is reasonable to plan for an initial investment starting from EUR 1 million to cover setup and the first year of operations", listing company setup and legal registration, licence acquisition, software purchase or integration, website and front-end development and initial marketing as one-time costs, and licence fees and software maintenance, staff, marketing, payments, bonus payouts, game provider fees, taxes and compliance as recurring ones^[2].

A platform agreement filed with the U.S. SEC, between Pragmatic Solutions (IOM) Limited and HR Entertainment Ltd and dated 31 January 2023, sets a EUR 40,000 platform setup fee and a EUR 20,000 migration fee, a EUR 15,000 monthly minimum, royalties of 2.00% of GGR up to EUR 1,000,000 and 1.50% above it, and a 3-year term^[4].

The same agreement licenses the platform for use "in object code form only", states that "the Supplier retains all Intellectual Property Rights in and to the Platform and applicable Documentation", and sets termination compensation as the monthly minimum multiplied by the number of months outstanding of the term^[4].

These are the terms you replace when you build, and the ones you keep when you split. One such split: an own wallet, bonus engine and back office, with a rented game aggregator and rented KYC. It keeps the data and the product logic yours without rebuilding content integrations from scratch. What the rented platforms publish, vendor by vendor, is on SOFTSWISS alternatives, Pragmatic Solutions PAM alternative and SOFTSWISS vs EveryMatrix.

Which decisions decide certification and operations?

A ledger, not a balance column. Store every movement as an immutable entry and derive balances from entries. Retries from game providers, payment callbacks and manual adjustments then become lookups and new entries, not overwrites, and a regulator's question about one transaction is answered from records.

Bonus money as its own balance. Keep bonus money, wagering progress and loyalty points apart from withdrawable cash, so a bonus can be granted, wagered, converted or forfeited without touching the cash ledger. The bonus engine also has to encode what a market forbids.

Brazil's regulator states that, to prevent bettor indebtedness, offering credit to bet and sign-up bonuses to attract bettors is forbidden, as is the use of credit cards, with the measures in force from 1 January 2025^[5].

Identity and money as a closed loop. Registration owns identity, and the cashier owns which instruments a player may use. Some markets fix both in their rules.

The SPA states that every bettor has to be identified with documents and a "sistema de reconhecimento facial com prova de vida", and has to register a bank or payment account in their own name that is "a origem e o destino de todos os recursos que enviar ou receber da empresa de apostas"; operators are forbidden to accept deposits from any other account, and deposits or prizes in cash or by boleto are prohibited^[5].

Records designed for the regulator from the first table. Retention, backup and export rules reach into the data model, so they are decided before it exists.

The SPA states that operators must keep an updated backup, for at least five years, of all data relating to bettors and operations, under Annex I of Ordinance SPA/MF 722/2024; that the data must be updated at least every 24 hours; and that its integrity and correspondence must be tested at least every seven days^[5].

Game content is certified, and the catalogue has to know it. Certification is a gate on which games may be offered, per market, so the catalogue carries certification data and the lobby filters on it. The regulator's own wording for Brazil: every online game must be certified, and from 1 January 2025 operators may offer only online games sent via Sigap and certified by the five certifying entities authorised by the SPA^[5]. The integration side is on casino game aggregation and integration; the full reading of Brazil's rules is on Brazil sportsbook platform requirements.

Configuration per market and brand. Limits, game availability, bonus rules, tax and reports differ by jurisdiction. Treat them as data with versioned changes, so a market launch is configuration and certification, not a fork of the code.

In what order is the work done?

1. 1.Scope with compliance in the room: target markets, licences held or applied for, payment methods, game providers, bonus types.
2. 2.Ledger, wallet and accounts: the core every other part writes to, with idempotent calls and an audit trail.
3. 3.Game integration layer: one internal contract, the first providers or an aggregator, reconciliation against provider reports; the wallet side is in the game-provider aggregation layer.
4. 4.Payments and KYC: provider integrations, withdrawal flow with checks, reconciliation.
5. 5.Bonus engine and responsible-gambling controls: offers, wagering, limits, exclusions.
6. 6.Back office and reporting: support tools, manual adjustments with approvals, regulator reports.
7. 7.Certification and load testing: lab testing against the relevant standard, such as GLI-19 v3.0 for interactive gaming systems^[1]; load tests sized for the busiest expected promotion or live-dealer peak, the failure modes of which are in scalability lessons from iGaming platforms.
8. 8.Migration, if you are leaving a platform: data import, parallel running and cutover by market.

How do you leave a white label or turnkey platform?

SOFTSWISS's knowledge base says of the move from a white label to an own platform: "Migration requires new investment, compliance re-certification, and regulatory approval timelines"^[3].

The sequence that holds up in practice, with licence and payment accounts moved first, is in moving from a white label to your own platform. If you are on SOFTSWISS specifically, the exit checklist is on the SOFTSWISS alternatives page.

What should you ask a casino platform development company?

1. 1.Show the ledger model: how is a rollback for a bet the wallet never saw handled?
2. 2.How are bonus balances, wagering and cash kept apart, and how is a bonus converted?
3. 3.Which parts do you propose to rent, and how would one be replaced later?
4. 4.Which certification standards and markets was the design prepared for?
5. 5.How is a player's full history exported for a regulator or a dispute?
6. 6.Who owns the code, the schemas and the deployment scripts at the end, and which components stay the vendor's?

Who should not build a custom casino platform?

• An operator testing one market with no plan to change the product: a white label or turnkey platform starts faster.
• A business that needs its own game catalogue produced: game content is a separate studio business.
• A buyer who needs someone to hold the gambling licence: licences are held by operators.

Related on this site: iGaming platform case study.

Product and company names are trademarks of their respective owners and are used only to identify their products and published documents. No vendor named here reviewed or endorsed this page. The regulatory passages are an engineering reading of the SPA's own FAQ, read on 2026-09-23, not legal advice, and nothing here says which operators hold authorisations.