Research for evidence-led software decisions
Each study defines a buyer question, freezes the field set, prefers current primary sources, preserves uncertainty, publishes limitations, and provides downloadable data. The work is designed to start an RFP or test plan, not to replace one.
Current studies
Online Casino Software Stack Evidence Map 2026
A 2026 online casino software stack evidence map covering PAM, wallet, payments, games, KYC/AML, bonus, reporting, security, reliability, and exit.
Open the studyPublication standard
- State the operator decision and the unit of analysis.
- Use current supplier, regulator, standards-body, government, or testing sources.
- Separate explicit support, partial support, missing public evidence, and unevaluated fields.
- Publish the checked date, methodology, limitations, source ledger, and CSV.
- Do not infer price, performance, eligibility, compliance, or implementation success from marketing visibility.
Frequently asked questions
Are these pages vendor rankings?
No. They are dated evidence matrices and control crosswalks. They do not score private product quality, price, performance, or customer outcomes.
Why publish the CSV?
The downloadable dataset exposes the field definitions, classifications, source anchors, checked date, and limitations so a buyer can review or adapt the work.
Concept map
Related concepts and decision guides
- Online Casino Software: A First-Time Buyer’s Guide
- Learn the systems, decisions, and launch paths behind an online casino.
- Online Casino Software Learning Path
- Learn the operator modules in sequence, from player identity and games to payments, compliance, mobile UX, and administration.
- Online Casino Software Components
- Map the core and optional modules in an operator stack.
- Online Casino KYC and AML
- Understand verification, monitoring, limits, and operator accountability.
- common mistakes
- Avoid early decisions that create cost, compliance, and migration problems.
Evidence layer
Primary references and verification limits
Sources were checked on . They support the standards and verification questions used in this guide. They do not prove a supplier-specific price, market eligibility, implementation result, or private product claim; buyers should request current, versioned evidence for those points.
- UK Gambling Commission — Remote gambling and software technical standards Regulator. Remote gambling software controls, security requirements, player-facing technical controls, and jurisdiction-specific verification questions.
- UK Gambling Commission — Testing strategy for remote gambling software Regulator. Testing, release control, audit evidence, change management, independent review, and production assurance questions.