If you're building a real-money gaming platform in the United States, the first decision isn't a tech-stack decision. It's a regulatory one: are you Class II, Class III, or both? The answer shapes every line of code that comes after.
Most non-specialist teams blur the two. Operators don't have that luxury. Here's the plain-language version, with the engineering implications attached.
Class II — the bingo-based world
Under the Indian Gaming Regulatory Act (IGRA), Class II games are bingo and bingo-derived games. The defining technical characteristic: outcomes are determined by a server-drawn bingo, with players competing against each other for prizes drawn from a shared pool. The slot-machine-looking presentation on top is exactly that — a presentation. The math underneath is bingo.
What this means for the build:
- A bingo draw engine that operates a shared player pool and emits results deterministically and auditably.
- Re-skinnable presentation layers — the same bingo math, visualised as slots, instant-wins or traditional bingo cards.
- Compatibility with tribal regulatory frameworks, not state gaming commissions.
- Audit trails that map presentation events back to bingo outcomes.
Class III — the RNG world
Class III is the casino-style world: slots, table games, instant-win, sportsbook. Outcomes are determined by a certified Random Number Generator. Where Class II is shared-pool, Class III is per-player and stateless.
What this means for the build:
- A certified RNG, integrated and audited end-to-end.
- RGS (Remote Game Server) integration with third-party math/content studios.
- Per-jurisdiction player-protection: limits, cooling-off, self-exclusion, RG controls.
- State-level (or tribal compact) regulatory compliance, with the audit and reporting infrastructure that follows.
What's the same
Both classes need the same surrounding platform: wallet, KYC, AML, geo-fencing, payments, payouts, responsible-gaming controls, operator dashboards, BI, observability. We've shipped these layers for tribal Class II operators and for fantasy/Class III hybrid platforms like PlaySQOR and Acquire.bet, and 60–70% of the engineering surface is shared.
What's different
The differences sit in three places: the math layer (bingo vs RNG), the certification path (tribal lab vs state-recognised lab like GLI), and the player pool model (shared vs per-player). Get those three right and the rest of the platform is recognisable engineering.
How to choose
Operators don't pick "Class II vs Class III" in a vacuum. They pick based on the markets they want to serve, the compacts they hold, and the content they want to license. Many operators run both — Class II content in tribal markets, Class III content in licensed states — on a unified platform. That's the world we build for.