Live casino platform providers are three different operating models
A first-party studio, a third-party aggregation feed, and a dedicated table can all appear as “live casino” in a proposal. They do not carry the same legal entity, game authority, stream responsibility, wallet path, incident ownership, approval work, or exit risk.
Last materially updated August 12, 2026. This is a responsibility and acceptance map, not a “best live casino” ranking.
Operating-model choice
Name the route before comparing providers
Studio operations, dealer procedures, physical or virtual production, game logic, streaming chain, back office, game events, and product evidence for the contracted scope.
Player account, wallet, limits, responsible-gambling action, market eligibility, catalogue selection, promotion, player support, and operator reporting.
Studio or stream remains available while game state, wallet state, limits, or reporting diverge across systems.
Game-round authority, stream failover, dealer and table state, result recovery, wallet reconciliation, late events, and complete audit export.
Connector lifecycle, content routing, provider mapping, session launch, event normalization, retries, reconciliation, catalogue controls, and escalation across studios.
Approve each studio and title for the market, control availability, reconcile settlement and reports, manage exclusions, and retain a direct incident path.
A single integration hides different studio semantics and makes duplicate, missing, late, or reordered events look uniform when they are not.
Per-studio protocol mapping, session and round identifiers, retry behaviour, catalogue entitlement, certification map, incident routing, and exit portability.
Deliver the agreed physical or virtual production, staffing, branding, game configuration, capacity, release control, monitoring, recovery, and evidence pack.
Approve brand and scripts, forecast demand, staff governance, control promotions, verify market rules, and accept production changes and capacity plans.
The dedicated presentation is isolated but shares hidden capacity, release, or recovery dependencies that are not covered by the contracted service level.
Capacity and concurrency, camera and stream degradation, failover destination, branded UI fallback, staffing continuity, release governance, and closure or exit plan.
Current detailed studio contexts
Two studio products meet the current detail threshold
Inclusion means the studio and delivery model can be described without using a global catalogue number as a substitute. It does not mean every product, table, studio, certification, or market is available to every operator.
Physical-studio and virtual green-screen production with studio and game-interface design, streaming, back-office control, and production support.
Local studios, dedicated tables, manual and automated roulette, blackjack, baccarat, bespoke presentation, and branded interfaces are separate project choices.
PlayMatrix is a first-party live-casino product. It must not be merged with CasinoEngine or SlotMatrix third-party aggregation when ownership, studio operations, incident responsibility, and commercial scope are assessed.
Studio location, game and table availability, certification, supplier permission, product approval, operator entitlement, and contracted operating responsibility remain market- and deployment-specific.
Malta (MGA) · Denmark · UK (UKGC) · New Jersey · Pennsylvania · Michigan · West Virginia. These contexts do not establish live-product availability.
First-party live-dealer studio operations with standard, branded, and market-specific production across selected physical studio locations.
Blackjack, roulette, baccarat, game-show and branded variants can include dedicated tables and bespoke operator presentation.
The live product can sit beside Playtech PAM and casino modules, but a studio deployment does not establish that the operator uses those modules or that one service level governs the complete stack.
Recorded studio presence and named operator launches do not create automatic state access, product approval, catalogue entitlement, or availability for another operator.
UK (UKGC) · Malta (MGA) · Denmark · New Jersey · Pennsylvania · Michigan · West Virginia · Alberta. These contexts do not establish live-product availability.
Witnessed acceptance
Seven controls decide whether the model is operable
| Control domain | Required position | Witness before acceptance | Reject or escalate when |
|---|---|---|---|
| Entity and approval map | Studio operator, software supplier, game owner, aggregator, platform, licence holder, and operator-of-record are mapped per market and game. | Trace a selected table from contract and approval records through game launch, wallet, reporting, and player terms. | A group brand or studio location is used as a substitute for the exact legal entity, product approval, operator entitlement, or contracted role. |
| Round and wallet authority | Round identifiers, accepted bet, result, win, rollback, cancellation, disconnect, retry, and final wallet state have one documented authority and idempotency rule. | Interrupt play before and after each state transition; replay duplicated and late events; reconcile studio, aggregator, PAM, wallet, and reports. | The parties cannot determine which system owns the final state or how a divergence is detected and repaired without manual guesswork. |
| Stream and production continuity | Camera, encoder, network, stream, studio, table, dealer, game server, and back-office failure paths have monitoring, fallback, player treatment, and evidence. | Degrade and fail each dependency, including a shared upstream service; verify player messaging, bet state, failover, recovery, and incident timestamps. | A video fallback masks an unresolved game or wallet state, or shared capacity and recovery dependencies sit outside the proposed service level. |
| Limits and responsible gambling | Session, wager, deposit, loss, exclusion, risk, marketing, and interaction controls remain enforceable across studio, aggregator, platform, and operator systems. | Change limits and exclusion state during an active session and queued campaign; verify propagation, blocked actions, open-round treatment, and audit history. | The live product can continue accepting play or promotions using stale player-control state without a bounded fail-closed rule. |
| Dedicated production scope | Dedicated tables, dealers, hours, languages, brand assets, environments, capacity, releases, support, failover, and exit treatment are explicit schedule lines. | Verify normal and peak capacity, staff handover, branded fallback, emergency change, maintenance, relocation, and decommissioning. | Dedicated is only a visual label while critical capacity, release, support, or continuity remains shared and commercially undefined. |
| Catalogue and entitlement | Every studio, game, variant, table, currency, language, device, jurisdiction, certification, and operator entitlement is versioned and exportable. | Compare the approved catalogue with the production configuration, launch API, lobby, back office, and regulator or lab record. | A global game list or aggregation count replaces the exact market-approved and contract-entitled catalogue. |
| Reporting and reconciliation | Round, bet, result, win, fee, jackpot, promotion, incident, player-control, and correction events reconcile to stable identifiers and retained raw records. | Rebuild a trading day and selected player journeys from raw exports; resolve late, corrected, duplicated, and missing records. | A summary report cannot be traced to round-level events or the buyer cannot obtain a complete usable export for audit and exit. |
Live casino platform questions
Is a live-casino aggregator the same as a live-dealer studio?
No. An aggregator primarily normalizes access to third-party content, while a studio product controls some combination of production, dealers, streams, games, and back-office operation. A supplier can offer both, but the responsibilities and failure paths remain separate.
Does a dedicated table mean the whole service is dedicated?
No. The table, dealers, visual presentation, studio, stream, game server, capacity, monitoring, release process, and recovery path can have different sharing boundaries. The contract must name each one.
Does supplier permission prove that every live game is available?
No. Supplier status, studio operation, game certification, product approval, operator entitlement, contract catalogue, and production deployment are separate gates.