Kody Nexov
Published 
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
iGaming Platform Architecture Evidence Crosswalk 2026
A 2026 architecture evidence crosswalk for iGaming platforms, APIs, PAM, wallet, payments, CRM, reporting, reliability, security, and release assurance.
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
- iGaming platform
- Compare platform architecture, integration depth, module ownership, and operational constraints before selecting a core stack.
- platform map
- Assign platform boundaries, systems of record, interface owners, acceptance evidence, and degraded-mode questions.
- affiliate platforms
- Affiliate platforms are a critical growth component for iGaming operators, acting as the technical bridge between traffic acquisition partners and backend financial systems.
- iGaming platform
- Understand the core platform, its operating boundaries, and the architecture decisions that shape an operator stack.
- iGaming Software Modules guide
- Evaluate platform modules separately while preserving end-to-end workflow, data, and operational ownership.
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.
- PCI Security Standards Council — PCI DSS Industry standards body. Payment account data security requirements for merchants, processors, service providers, and systems that can affect the cardholder data environment.
- OWASP Application Security Verification Standard Open application-security standard. Testable web-application security requirements and procurement-ready verification criteria.
- NIST Cybersecurity Framework 2.0 Government standards body. Cybersecurity governance, risk management, protection, detection, response, and recovery outcomes.
- AWS Well-Architected — Reliability Pillar Cloud architecture guidance. Availability targets, resilience testing, incident learning, recovery objectives, capacity, and dependency management.
