An iGaming platform provider checklist helps operators compare suppliers using measurable technical capabilities, commercial terms, and documented evidence rather than sales promises.
Before signing a contract, assess the provider across 12 areas: architecture, APIs, ownership, scalability, integrations, security, compliance, service-level agreements, reporting, total cost, implementation, and exit terms.
This guide from SwissDice explains what to ask potential suppliers, which documents to request, and how to identify risks before committing to a platform.
1. Evaluate the Platform Architecture
Start by understanding how the platform is built and how its components interact. A provider should explain the architecture clearly, including the systems responsible for player accounts, wallets, game aggregation, bonuses, payments, reporting, and administration.
Determine whether the platform uses modular components or a tightly coupled system. Modular architecture may simplify upgrades and integrations, while a tightly coupled system can make some changes more dependent on the original provider.
Ask these questions:
- Which core modules are included in the standard platform?
- Can individual components be upgraded or replaced independently?
- How are development, testing, and production environments separated?
- How are software updates deployed and rolled back?
- Which third-party systems are essential to platform operation?
What to verify: Request an architecture diagram, deployment documentation, and a demonstration of how the provider implements a typical system change.
Do not select a supplier based on terms such as “cloud-native” or “microservices” alone. Evaluate how its architecture supports your actual operating requirements.
2. Test API Quality and Integration Flexibility
APIs determine how easily your platform connects with external services and internal business systems. Poor API documentation or limited access can increase implementation costs and restrict future development.
Request API documentation before signing. Review authentication, permissions, rate limits, versioning, error handling, webhook reliability, and sandbox availability.
For wallet and transaction APIs, examine how the system handles duplicate requests, delayed responses, failed transactions, and reconciliation. These scenarios are important for maintaining consistent transaction records.
Ask whether APIs cover player management, payments, bonuses, game sessions, reporting, and other required functions. Confirm whether access is included in the commercial agreement or requires additional fees.
What to verify: Obtain API specifications, test credentials, sample requests and responses, and details of how failed requests are recovered.
A supplier should demonstrate its integration capabilities rather than relying on a general claim that its platform supports APIs.
3. Clarify Software Ownership and Data Rights
Ownership is one of the most important commercial checks because it affects flexibility and the ability to change suppliers.
Clarify who owns the underlying platform, custom-developed modules, configuration files, brand assets, and intellectual property created specifically for your business. Software licensing does not necessarily mean that the operator owns the source code.
Data rights also require careful review. Establish how you can access and export player records, transaction histories, reports, and other business-critical information, subject to applicable privacy and regulatory requirements.
Ask the provider:
- Who owns custom development and configuration work?
- Can your team access and export operational data?
- Which accounts and credentials remain under your control?
- Are there restrictions on using custom modules with another supplier?
- What happens to your data and configurations when the contract ends?
What to verify: Review intellectual-property clauses, data-processing agreements, export specifications, and account ownership arrangements with your legal team.
4. Verify Scalability and Performance
A platform that performs well during initial testing may struggle during promotional campaigns, major sporting events, or rapid business growth.
Ask providers to explain how they measure capacity. Concurrent player sessions, transaction throughput, game launches, and reporting workloads are different performance indicators.
Discuss database capacity, caching, infrastructure scaling, geographic distribution, and dependencies on external services. You should also understand how the system behaves when a payment gateway or game provider experiences an outage.
Request performance test results and clarify the assumptions behind any capacity claims.
What to verify: Ask for load-testing evidence, expected response times, error-rate thresholds, monitoring examples, and disaster-recovery procedures.
Your evaluation should establish whether the platform can meet realistic launch requirements and accommodate projected growth without unexpected infrastructure or licensing costs.
5. Review Third-Party Integrations
An iGaming platform may depend on multiple external providers for games, payments, identity verification, fraud monitoring, analytics, customer relationship management, and affiliate operations.
Create an integration checklist based on your target markets and operating model. For each required integration, identify whether it is already available, requires certification, depends on another supplier, or needs custom development.
Also clarify who manages integration maintenance and incident resolution. An integration appearing in a supplier's portfolio does not necessarily mean it is available for your specific configuration or jurisdiction.
Ask these questions:
- Which integrations are live and ready to use?
- Are additional integration or certification fees applicable?
- Can you select your preferred third-party providers?
- Who handles incidents involving external vendors?
- How long does adding a new integration typically take?
What to verify: Request an integration matrix, implementation estimates, and a list of third-party charges.
6. Assess Security Controls
Security should be evaluated through documented controls and independent evidence, not general assurances.
Review encryption, access management, multi-factor authentication, privileged-user permissions, vulnerability management, secure development practices, and security monitoring.
Ask how production access is approved, how access rights are reviewed, and how security incidents are detected and escalated. Understand how the provider evaluates subcontractors and other technology partners that may process sensitive information.
Request information about independent penetration tests and relevant security certifications. Verify their scope, validity, and applicability to the services being offered.
What to verify: Review security policies, assessment summaries, incident-response procedures, access-control practices, and data-retention arrangements.
Your security assessment should also establish how the provider supports your own security obligations and incident-reporting requirements.
7. Check Compliance and Responsible-Gambling Support
A platform provider can supply compliance-related functionality, but using its technology does not automatically make an operator compliant. Requirements depend on the licence, jurisdiction, product, and responsibilities assigned to each party.
Assess support for identity verification, KYC and AML workflows, self-exclusion, player limits, account restrictions, audit trails, and regulatory reporting where required.
Determine which capabilities are native, which rely on external services, and which require configuration or custom development. Ask how regulatory changes are incorporated into the platform and communicated to clients.
What to verify: Request a jurisdiction-specific capability matrix, audit-log examples, and a written allocation of compliance responsibilities.
Have qualified legal and compliance professionals confirm that the proposed arrangement meets your obligations before committing.
8. Examine the Service-Level Agreement (SLA)
An SLA defines the service commitments a provider makes and the remedies available when those commitments are not met.
Do not assess an SLA solely by its headline uptime percentage. Check which services are covered, how uptime is calculated, what exclusions apply, and whether maintenance periods are included.
Review incident severity classifications, response times, update frequency, escalation procedures, and service-credit conditions. Response time and resolution time are different commitments, so understand both.
You should also assess backup procedures, disaster recovery, and business continuity. Ask about the recovery time objective (RTO), which defines the target time to restore a service, and the recovery point objective (RPO), which defines the targeted limit on data loss measured in time.
What to verify: Request the complete SLA, escalation matrix, incident-management process, and disaster-recovery test results.
9. Validate Reporting and Analytics
Reliable reporting helps operators monitor transactions, financial performance, player activity, bonuses, and operational issues.
Review the reports included in the platform and establish how frequently data is updated. Determine whether reporting data can be exported, accessed through APIs, or connected to your existing analytics systems.
Pay particular attention to metric definitions. Gross gaming revenue (GGR), net gaming revenue (NGR), active players, deposits, withdrawals, and bonus costs can be calculated differently across systems.
Ask how the platform records reversals, adjustments, currency conversions, time zones, and historical corrections. Inconsistent definitions can create reconciliation problems between operational, financial, and compliance reports.
What to verify: Request sample reports, a data dictionary, export options, and examples of transaction reconciliation.
10. Calculate the Total Cost of Ownership
The initial setup price rarely represents the full cost of operating an iGaming platform.
Your financial comparison should include implementation, licensing, revenue share, minimum monthly commitments, payment processing, game aggregation, hosting, support, custom development, integrations, upgrades, and additional market requirements.
Ask which fees are fixed and which depend on usage, revenue, transaction volume, or product expansion. Clarify the charges for adding brands, currencies, games, or jurisdictions.
Build a three-year cost model using conservative, expected, and growth scenarios. Include the cost of routine changes and third-party services, not just the initial launch.
What to verify: Request a complete fee schedule, implementation scope, change-request rates, minimum commitments, and renewal conditions.
The objective is to compare the likely cost of operating each solution over time, rather than choosing the supplier with the lowest quoted setup fee.
11. Review Implementation and Product Roadmaps
A successful implementation requires clear responsibilities, realistic milestones, and a structured testing process.
Ask the provider for a project plan covering configuration, integrations, testing, acceptance, deployment, and post-launch support. Identify which tasks belong to your team, the platform supplier, and external vendors.
Review how the provider handles software releases, API changes, feature requests, and product roadmap commitments. Distinguish confirmed delivery commitments from proposed features that have no agreed timeline.
If a feature is essential to launch, document its specifications, deadline, acceptance criteria, and consequences if it is not delivered.
What to verify: Request a sample implementation plan, responsibility matrix, release policy, and acceptance-testing checklist.
Strong project governance reduces ambiguity and makes delays, dependencies, and additional costs easier to manage.
12. Negotiate Exit and Migration Terms
Exit provisions should be reviewed before signing, even when both parties expect a long-term relationship.
If your business requirements change, you need to understand how you can migrate to another provider without losing access to essential records or becoming dependent on undocumented processes.
Review termination rights, notice periods, renewal clauses, data-export timelines, migration support, and post-termination access. Confirm how custom-developed components, configurations, integration credentials, and third-party licences will be handled.
Ask whether the provider will support data migration and what fees apply. Establish how data will be securely deleted once retention obligations have been met.
What to verify: Request a sample exit plan, data-export specifications, transition-service rates, and written confirmation of your rights to operational data.
A practical exit plan reduces supplier lock-in and gives your business more flexibility when evaluating future technology options.
How Should You Score an iGaming Platform Provider?
Use the same evaluation criteria for every shortlisted supplier. Score each of the 12 checks from 1 to 5:
- 1 — Poor: Claims are unsupported or major gaps exist.
- 2 — Limited: Significant limitations remain unresolved.
- 3 — Acceptable: Requirements are met with manageable gaps.
- 4 — Strong: Evidence supports the required capabilities.
- 5 — Excellent: Capabilities are demonstrated, documented, and aligned with your requirements.
Weight each category according to your business priorities. For example, operators entering regulated markets may place greater weight on compliance, security, and auditability. Businesses planning rapid expansion may prioritize scalability, API flexibility, and integration speed.
Do not let a high average score conceal a critical failure. Treat unresolved security, transaction integrity, compliance responsibilities, data access, and exit rights as potential deal-breakers.
Score evidence rather than feature labels. For each requirement, record the owner, supplied evidence, acceptance test, dependency and unresolved exception. A provider demo is useful, but a reproducible sandbox result and a clear contract boundary answer different questions.
Review PAM responsibilities and reporting readiness before setting acceptance criteria. An independent technical architecture review can help turn the selection into a testable scope.
Which Platform Model Should You Consider?
The right delivery model depends on your business objectives, technical resources, customization requirements, and desired level of control.
A Turnkey iGaming Platform may be relevant if you want an integrated technology stack with multiple operational components. A White Label iGaming Platform may suit businesses seeking a branded launch with a more predefined setup.
These models can differ significantly by provider. Compare actual module coverage, integrations, customization limits, data rights, support, and commercial terms rather than relying on the model name alone.
SwissDice also offers iGaming Consulting to help businesses assess technical requirements, integration dependencies, and platform planning. Define your requirements before comparing suppliers so your final selection reflects your operating needs.
Final Thoughts
Evaluating an iGaming platform provider requires more than reviewing product features and launch promises. Operators should verify technical capabilities, assess commercial commitments, and establish clear ownership and exit arrangements before making a decision.
Use this checklist to structure supplier demonstrations, due diligence, and contract negotiations. A provider that offers transparent documentation, realistic commitments, and verifiable technical evidence is better positioned for a productive long-term partnership with your business.
Sources & further reading
Sources checked on 30 October 2026. Regulatory examples apply to the named jurisdiction; research forecasts and supplier descriptions retain their own scope.
