Live Dealer Software Guide: How Live Casino Actually Works

A live dealer table is two systems running in lockstep. One is a broadcast chain that moves pictures of a real table into a browser. The other is a wagering system that records bets, captures the physical outcome as data and settles against it.

Confusing the two is the most common evaluation mistake. The stream is what players talk about. The data path is what the regulator and the disputes team care about.

How does live dealer streaming technology work?

The capture layer

A production table carries at least two angles: a wide shot that establishes the dealer and the table, and a tight shot on the point of decision, the wheel head or the card leaving the shoe. Roulette usually adds a third angle on the ball track.

Those feeds reach a vision mixer that cuts between angles on cues from the table. Overlays, bet timers and multipliers are composited either there or in the player client, and where they sit decides how much you can localise later.

Reading the wheel and the shoe

Optical recognition turns the physical outcome into a number. A roulette wheel typically pairs a sensor on the rotor with a camera trained on the pockets, and the two readings are cross checked before a number is published. Card games read barcodes or optical marks on the card edge as each card leaves the shoe.

That hardware is standardised. Gaming Laboratories International publishes GLI-29 for card shufflers and dealer shoes, alongside GLI-25 for dealer controlled electronic table games. Ask any supplier which of those its equipment is tested against.

The game control unit

The game control unit sits at the table and holds the authority on state. It opens and closes the betting window, drives the dealer display, receives the recognised result and publishes it to the game logic server.

The separation matters for disputes. A player on a buffered feed may watch the ball drop two seconds after betting closed on the server. The server timestamp governs, and your terms need to say so.

What latency budget does a live table need?

Protocol choice is a real tradeoff, not a checkbox. WebRTC gives the lowest delay and is why a dealer greeting lands while the ball is still moving. Cloudflare documents its WebRTC delivery at less than 1 second of latency.

It is also the most expensive path to scale, because every viewer holds a session rather than pulling a cached segment. Low latency HLS and CMAF based low latency DASH sit in the middle: they ride ordinary CDN caching, so a large concurrent audience is cheap, and they degrade more gracefully on weak mobile networks.

Plain HLS or DASH is not viable at a table. Amazon notes that a traditional over the top stream may run as high as 30 seconds, which is longer than an entire roulette round.

Most studios therefore ship both: a real-time path where the device supports it, and a low latency HLS fallback so nobody is locked out. Size the betting window around the slower path and settle on server timestamps, so both audiences are treated identically.

Own studio or aggregated live content?

Aggregated content ships in weeks. One contract through a casino game aggregator brings dozens of studios, one wallet integration and one certification path, and the cost sits as a percentage of live gaming revenue that scales with the revenue itself.

What you give up is control. Branding is limited to what the supplier exposes, the roadmap is theirs, and shared tables seat your players beside every other operator on the same feed.

The middle option most brands actually pick

A dedicated table inside somebody else's studio is the usual compromise: your felt, your logo, your dealers in your uniform, on the supplier's infrastructure and licence. It costs a fixed monthly fee on top of revenue share, and it removes the staffing problem without losing the branding.

A full room adds property, power, cooling, redundant connectivity, surveillance, casino grade equipment and a payroll covering three shifts a day. Evolution, which streamed its first tables in 2006, now describes a global organisation of over 22,000 people. Live dealer is a staffing business wearing a technology badge.

Where regulation decides for you

Some markets settle the argument. Where a regulator requires live production inside the licensed jurisdiction, offshore aggregated tables are simply unavailable and an in-market room becomes the price of entry. Read the technical standards before you model the economics.

Equipment and infrastructure requirements

Encode to broadcast norms rather than gaming folklore. Amazon's published guidance puts 1080p at up to 8,500 Kbps, 720p at up to 4,500 Kbps and 480p at up to 1,500 Kbps, with 30 or 60 frames per second at the HD resolutions.

Two settings matter more than raw bitrate: a two second keyframe interval, or one second for lower end to end delay, and constant bitrate. AWS warns that variable bitrate spikes cause dropped frames and buffering.

Wire every encoder. The same guidance is explicit that Wi-Fi and mobile links suffer interference and queueing delay, and recommends allocating 50 percent more bandwidth than the minimum the stream requires. A table that drops is a voided round with real money attached.

Lighting, felt and audio

Lighting is what makes recognition reliable. Even, diffuse, flicker free light at a consistent colour temperature keeps card marks legible and stops the encoder spending bits on sensor noise. Dim rooms force camera gain up, and grain compresses badly.

Felt is chosen for contrast against chips and cards before brand colour. Audio needs a dealer microphone and a room microphone held in sync with the video, because audio drifting out of sync reads as fake faster than any other defect.

Redundancy

Assume failure. Dual encoders, two internet providers on physically separate routes, power protected by a UPS and a generator, and a documented fallback that moves players to another table without stranding an open bet.

Dealer training and game management

Read those five as a staffing plan. A live floor needs a supervisor per cluster of tables, a shift manager, a surveillance operator and a maintenance rota for wheels, shoes, shufflers and card decks.

What a live dealer actually does

Dealing to camera is a different craft from dealing to a pit. The dealer runs each round to a rhythm set by the game control unit, narrates it for players who cannot see their neighbours, reads and answers chat, and holds procedure even when a player turns abusive.

Training therefore covers procedure, game rules, presentation and responsible gambling escalation, and the evidence has to survive an audit. The Commission expects records of training and refresher training to be maintained.

Managing rounds, misdeals and interruptions

Real tables produce real mistakes. Procedures must define what counts as a misdeal, who calls it, how the round is voided and how open bets are returned to players.

RTS 10 on interrupted gambling requires systems capable of voiding gambles and restoring events to their pre failure state, and requires operators to publish how players are treated when a service interruption happens.

Integrating live content with the casino platform

The work concentrates in four places. Session and launch, where a signed token carries player, currency and jurisdiction into the table. Wallet, where debits and settlements must be transactional and idempotent, because a retried settlement can never be allowed to pay twice. Those mechanics are common to every remote game, and the general game API contract is covered in its own guide.

Reporting comes third: the supplier round identifier has to join cleanly to your own ledger, or reconciliation turns manual. Fourth is the lobby, where tables need live data, open seats, current limits, recent results and dealer name, refreshed rather than cached.

Limits, currencies and jurisdictions

Shared tables carry the supplier's own bet limits. Your platform layers its limits, responsible gambling caps and currency conversion on top, and any mismatch surfaces as rejected bets. Agree the limit model during integration, not in production.

Contracts matter as much as code. Whether you go direct to live game providers or through one aggregation layer changes how many wallet integrations, certifications and reconciliations your team carries.

Certification and the wider compliance path

Live tables are usually certified as part of the interactive gaming system, GLI-19 in jurisdictions that follow the GLI standards, and the studio itself is inspected wherever the regulator requires it. If the rest of the stack is still being assembled, our guide to launching a compliant casino platform covers that control matrix.

Operators comparing suppliers rather than building can start from vendor selection in the online casino software guide, then check how a delivered live casino software stack, from OHS Gaming or another vendor, maps onto the five stages above.