Early social casino platforms had a straightforward architecture: player opens a browser tab, loads a slot, spins through a session, closes the tab. Solo, self-contained, and completely disconnected from anyone else on the platform at the same time. For a category with “social” in the name, the actual social layer was thin.
That’s changed substantially over the last few years, driven by the same technology stack that rebuilt live commerce, multiplayer cloud gaming, and real-time collaborative software. WebRTC for low-latency video, WebSocket connections for persistent state sync, CDN edge infrastructure for global stream delivery, and server-side event systems for coordinating shared experiences at scale. Platforms like Spree Casino, operated by Play Spree Ltd as a browser-based and PWA promotional sweepstakes platform, now look architecturally very different from what the category offered in 2022 – even when the game titles on screen look superficially similar.
Here’s what that infrastructure actually looks like, and what it’s changed about the player experience.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
WebRTC and the live dealer layer
The live dealer room is the most visible live feature in the social casino category, and WebRTC is what makes it work at scale. It’s the same open standard that powers Google Meet and Jitsi – handling real-time video transport from a studio camera to a player’s browser, with latency targets under 500 milliseconds to keep dealer interaction feeling synchronous.
The production setup behind a live dealer table is more complex than a standard WebRTC video call. The studio runs multiple camera angles on a single table, with a vision mixer cutting between them based on game state. That mixed feed gets encoded at multiple bitrate tiers simultaneously – typically 1080p at 4 Mbps, 720p at 2 Mbps, and 480p at 800 Kbps – and distributed through a CDN edge network that selects the right tier based on each player’s measured connection quality in real time. A player on strong broadband gets the 1080p feed; a player on a congested mobile connection steps down to 480p without any visible interruption.
The game state layer runs separately from the video transport. Dealer actions – card draws, wheel spins, result announcements – are captured by a game control interface that writes results to a central game server in real time. That server pushes outcome data to all connected player clients simultaneously via WebSocket, so every player sees the same result at the same time regardless of their individual video stream latency. Separating video from game state is a deliberate architectural choice: a player on a degraded video connection still gets accurate, timely results even if their visual feed is running behind.
WebSocket and shared lobby state
The persistent WebSocket connection is what enables everything beyond the solo session. Unlike a standard HTTP request that closes after a response, a WebSocket stays open after the initial handshake and lets the server push data to the client at any time. That push capability is what makes real-time shared state possible.
In a social casino lobby, a single WebSocket connection carries several simultaneous data streams. The prize counter for a shared mechanic like SpreePotz – Spree’s uncapped progressive jackpot added to regular spins, that can be won at any time – updates in real time as players across the platform engage with eligible sessions. When a SpreePotz prize fires, the event is broadcast to all connected clients simultaneously, producing the shared notification that makes the mechanic feel like a community moment rather than a private outcome.
Connection management at scale is the engineering challenge here. A platform with tens of thousands of concurrent users – each maintaining a persistent connection – needs a connection broker architecture that can distribute load across multiple server nodes, handle reconnections gracefully, and maintain session state across those reconnects. Modern WebSocket brokers handle this through sticky session routing and distributed session state storage, making a player’s active session recoverable from any node in the cluster.
CDN edge architecture for live streams
Live dealer content distribution is a CDN problem most web applications don’t encounter. A single table serving five hundred concurrent viewers is delivering five hundred simultaneous video streams, each encoded at multiple bitrate tiers, to players distributed across the continental US and beyond. The origin studio can’t serve that directly.
The standard two-tier distribution model works like this: the studio sends a single high-quality origin stream to a small number of regional ingest points. Those ingest points transcode into multiple delivery tiers and distribute to edge nodes in each region. A player in Los Angeles receives their stream from an LA-area edge node; a player in New York receives from New York. Round-trip latency from player to edge node typically sits under 20 milliseconds, keeping end-to-end dealer-to-player latency within the 500-millisecond target despite transcoding and distribution overhead.
For a browser-based platform like Spree Casino – which runs without a native app, relying entirely on the browser’s built-in video decoding and WebRTC stack – the CDN delivery has to be compatible with codec support across mainstream browsers. The current standard uses H.264, which has near-universal hardware decode support across desktop and mobile, with VP9 as an alternative for Chrome-based Android where H.264 hardware decode is less consistent. Adaptive bitrate selection runs through the browser’s media source extensions API, querying network conditions and instructing the CDN to switch tiers without interrupting playback.
Real-time leaderboards
Slot tournaments with live leaderboards are one of the more technically demanding live features in the stack. They require consistent, low-latency state synchronisation across a large number of concurrent players all generating score events simultaneously – thousands of write events per minute, merged into a consistent ranked view, pushed to every connected client within a latency budget that keeps the leaderboard feeling live.
The standard architecture uses an event streaming system like Apache Kafka to ingest score events from game servers, a leaderboard service that consumes the event stream and maintains ranked state in an in-memory store like Redis, and a push delivery layer that broadcasts updates to connected clients over WebSocket. Rather than pushing on every single score event, the leaderboard service buffers events for a short window – typically 500 milliseconds to two seconds – and pushes a consolidated update at the end of each window. That reduces push frequency by orders of magnitude while keeping the displayed leaderboard within a few seconds of the true current state.
The SpreePotz broadcast problem
The SpreePotz mechanic illustrates a specific engineering challenge that shared prize features introduce: how to handle a low-frequency, high-visibility event that needs to be communicated to a large number of connected users simultaneously without creating a thundering herd on the server infrastructure.
A SpreePotz prize fire is rare relative to the total number of spins happening across the platform at any moment. But when it fires, every connected user needs to be notified within a very short window. The broadcast architecture separates event detection from event delivery – the game server detects the prize trigger and writes a prize event record to the event streaming system, a dedicated broadcast service consumes that event and fans it out to all connected WebSocket clients through the connection broker’s pub/sub infrastructure. Clients subscribe to a prize event channel on connection; the broker handles delivery without the game server needing to know individual connection states.
The thundering herd risk is real: if every player who receives the notification immediately sends a request to check their own prize eligibility, the eligibility check endpoint gets hammered. Handling that requires rate limiting on the endpoint, client-side backoff logic that staggers requests across a short window, and server-side caching of eligibility results to prevent redundant computation.
The browser as the universal client
Spree Casino’s decision to run entirely in the browser – no native iOS or Android app – has real implications for the live feature stack. The browser is a more constrained runtime than a native app: no platform-level push notifications outside the Web Push API, video decoding performance tied to hardware decode support for the specific codec in use, and WebSocket behaviour that varies across Chrome, Safari, and Firefox.
Against those constraints, the browser offers meaningful advantages for live feature deployment. New features can be deployed and available to all users within minutes, with no App Store review cycle. The same codebase runs on desktop, tablet, and mobile without platform-specific builds. And the browser’s WebRTC implementation benefits from continuous performance improvements that browser vendors ship on their regular release cadences.
The PWA layer fills the capability gaps. Web Push notifications let the platform send prize event alerts and daily login prompts to users who have installed the PWA, even when the browser tab isn’t open. The service worker caches the application shell and static assets, reducing load time on subsequent visits to near-instant. And full-screen launch mode removes the browser chrome – address bar, tab strip, navigation controls – to give the live dealer room and slot titles a full-viewport experience close to what a native app delivers.
Spree Casino: platform features at a glance
| Feature | Detail |
|---|---|
| Welcome offer | 25,000 GC + 2.5 FREE SC on signup |
| Game library | 2,900+ titles across 33 leading studios |
| Daily login | 2,000 GC + 0.3 SC |
| Referrals | Up to 100 SC for inviting friends |
| Redemptions | 10 SC gift cards, 100 SC prize redemption |
| Top potential prize | SpreePotz, an uncapped progressive jackpot added to regular spins, that can be won at any time |
| Operator | Operated by Play Spree Ltd, browser-based & PWA only |
Where the stack is heading
AV1 codec adoption across browsers and hardware is expanding, which will reduce the bandwidth cost of high-quality live video delivery and make 1080p streams accessible to players on connections that currently receive 720p. WebTransport – the IETF standard using QUIC as a transport layer instead of TCP – offers lower head-of-line blocking than WebSocket on congested connections, which could improve reliability of leaderboard and prize event delivery for players on variable mobile networks.
On the application side, shared viewing features that let players watch another player’s session in real time, with a synchronised prize event feed and a shared chat layer, draw directly from the Twitch co-streaming model and are a natural extension of the shared lobby architecture platforms are already running. Real-time spatial audio in live dealer environments – using the Web Audio API to position dealer voice and table sounds in a virtual space – is another capability several studios are evaluating.
Each of these builds on the same WebRTC, WebSocket, and CDN foundation that live social casino features already run on. The investment in that infrastructure today is the prerequisite for the feature set that will differentiate platforms in 2027 and beyond. Whether that plays out as expected depends partly on how quickly browser vendors and CDN providers move on AV1 and QUIC adoption – but the direction is reasonably clear from where the broader streaming infrastructure industry is already heading.
