Real-Time Decisioning Demo | Sportsbook Next Best Lobby / Homepage
Pipeline<15ms
1 / 9
1
Architecture
2
Session Start
3
Ingest
4
Context
5
Feature Serving
6
Ranking
7
Business Impact
8
Outcome
9
Architecture Recap
Stage 1: The Architecture
Unified player context behind the betting homepage
Five tiers form a continuous loop: ingest, context, decide, act, learn. Wallet, identity, bet history, casino sessions, bonus state, risk signals, and live sporting events flow through RDI and Redis Feature Form. Redis RAM handles the hot session path. Redis Flex holds broader player history, vectors, and cross-product behavior. The platform decides what the player should see first before the session turns into drift.
Data Sources

Player Identity

Profile, device, geography, language

Wallet + Payments

Balance, deposit recency, withdrawal state

Sportsbook Engine

Open bets, favorite leagues, live markets

Casino + Slots

Last game, live tables, session depth

Kafka / Live Ops

Odds changes, event starts, promo triggers

Ingest Layer

Redis Data Integration (RDI)

Syncs wallet, profile, bonus, and product state from operational systems

Redis Feature Form

Serves online features for intent, retention, and cross-product steering

Unified Context Layer

Redis RAM

Hot session, active bet slip, live event urgency

Redis Flex

Warm cross-product history, behavioral embeddings, and long-tail behavior

Feature Store

Product affinity, churn, bonus responsiveness, RG signals

Redis Context Retriever

Assembles the Player 360 — session state, product affinity, and betting history — and exposes it as structured MCP tools for the decision engine

Decision Engine

Eligibility Rules

Geo, age, product, risk and responsible gaming guardrails

NBA Ranker

Engagement, retention, and conversion weighting

Redis Search

Player-to-product semantic matching

Policy Arbitration

Balances growth, trust, and safer-play priorities

Output Surfaces

Homepage Hero

Next best lobby, event, or product row

Sportsbook

In-play focus, slip recovery, top market row

Casino Lobby

Live tables, slots, recent play

Push / CRM

Session recovery and re-entry prompts

↺
Learn:  Clicks, launches, deposits, bet placements and dismissals retrain the models and update policy in Redis.
Decision Target
<15 ms
Primary Surface
Homepage + lobby routing
North Star
Session start → action
Stage 2: Session Start
The player lands and the platform has seconds, not minutes
Mateo lands on the homepage at 8:42 PM with an active wallet, an unfinished live bet slip, a strong casino affinity on weekends, and a Copa Libertadores match starting in six minutes. The platform needs to decide whether his next best experience is sportsbook, live casino, slots, or wallet action.
Homepage Session Event
MR
Mateo Ruiz
Spanish-language player | Active wallet | Sports + live casino crossover | 11 sessions this month
HIGH INTENT
Eventhomepage_session_start
Time8:42 PM local (prime live sports window)
Wallet balanceMXN 1,850
Open bet slip1 unfinished in-play slip
Last product usedLive casino roulette, 2 nights ago
Favorite patternFootball midweek, live casino weekends
Last outcomeBrowsed 4 minutes, no action in prior visit
Why This Moment Matters
The homepage is not just a navigation surface. It is a decision surface. The first row determines whether the player bets, deposits, crosses into another product, or leaves.
A generic homepage shows the same popular modules to everyone. A real-time decisioning homepage uses live context to decide which experience should lead.
The opportunity: Mateo has live-sports urgency, unfinished bet intent, and cross-product history. The right surface can turn a homepage visit into immediate action.
Without Redis: the site falls back to stale merchandising and popularity rows. Mateo scrolls, compares, and drifts.
Stage 3: Ingest
Operational systems and streams flow into Redis
RDI synchronizes wallet state, bonus state, bet history, product history, and account context from operational repositories. Redis Feature Form serves online features built from telemetry, product behavior, and live event data. Redis becomes the live context layer for the session start decision.
Source Systems → Redis
ID
Account + Identity
Profile, device, language, geography, verification state
→
WLT
Wallet + Payments
Balance, recent deposits, withdrawal state, preferred payment rails
→
SBK
Sportsbook Engine
Open slips, favorite leagues, live markets, odds movement
→
CAS
Casino + Live Tables
Recent games, dwell depth, session frequency, dealer/table affinity
→
BON
Promotions Engine
Bonus eligibility, active offers, wagering requirements, suppressions
→
KFK
Kafka or Redis Streams + Live Ops
Match start times, odds changes, clickstream, dismissal signals
→
Pipeline Status
Profile syncSub-second
Wallet + bonus stateContinuous CDC
Sports + casino telemetryStreaming
Redis Feature Form parity100%
Cold-start fallback<3%
Decision dependencyServed from Redis
Additive architecture: identity, wallet, sportsbook, casino, and bonus systems stay in place. Redis is the low-latency operating layer that makes them act together.
Stage 4: Context
Redis assembles the live player context
Historical behavior and live-session behavior meet in the same path. That is what makes the homepage a real-time decision surface instead of a static merchandising page.
Redis RAMRedis FlexRedis Context Retriever
Historical Context
Primary affinityFootball in-play + live roulette
Average deposit cadence2 per week before large matches
Cross-product patternSports first, casino after settlement
Favorite competitionCopa Libertadores
Bonus responsivenessLow to generic banners, high to contextual offers
Churn signalModerate — 2 recent browse/no-action sessions
Live Session Context
Match urgencyFavorite team starts in 6 minutes
Slip stateOne unfinished in-play bet
Wallet readinessBalance sufficient, no deposit needed
Casino triggerHigh likelihood after bet settlement
Current intentSports-led, high action probability
Risk / RG stateNo active suppressions
Context signal: Redis Context Retriever assembles the Player 360 — session state, product affinity, and betting history — so the decision engine has exactly what it needs. The next best homepage is not the most popular module. It is the module most likely to convert this session into action right now.
Stage 5: Feature Serving
Online features hydrate in milliseconds
Redis Feature Form serves the features that matter for homepage and lobby routing: sportsbook urgency, casino crossover likelihood, deposit need, bonus responsiveness, and churn risk. Redis RAM serves the hot path. Redis Flex contributes broader behavioral context.
sportsbook_urgency_score
Likelihood the player acts immediately on live sports if surfaced first
0.930.3 ms
casino_crossover_propensity
Likelihood the player moves from sportsbook to casino in the same session
0.710.4 ms
unfinished_slip_salience
Strength of unfinished action recovery on the homepage
0.880.3 ms
deposit_need_score
Probability the player needs wallet action before betting
0.120.2 ms
bonus_response_contextual
Probability the player responds to contextual vs generic promo placement
0.740.4 ms
browse_exit_risk
Probability the player exits without taking action
0.410.5 ms
Feature Serving Performance
Features Hydrated
196
P99 Lookup
2.0 ms
Train / Serve Parity
100%
Hot-path storage
RAM + Flex
Stage 6: Ranking
The platform ranks the next best homepage
The decisioning stack chooses what should lead the session now — sportsbook hero, unfinished slip recovery, live casino row, or promotional module. Redis supplies the unified context needed to make that choice in the live moment.
4 homepage routes evaluated
policy-aware and risk-aware
best next experience surfaced first
#1 Winner
SPORTSBOOK HERO
Live football + unfinished slip recovery
Highest immediate action probability for this session
Combines match-start urgency with unfinished action recovery and no wallet friction.
Decision score0.94
#2 Cross-product
LIVE CASINO
Roulette follow-on row
Strong secondary path if sportsbook action completes
Good fit, but not the strongest first-screen action for this exact moment.
Decision score0.79
#3 Suppressed
BONUS TILE
Generic deposit bonus module
Suppressed because wallet need is low
The player already has funds. A generic bonus tile creates distraction, not conversion.
Decision score0.31
Stage 7: Business Impact
The homepage becomes a decision surface, not a merchandising page
The value is not just cosmetic optimization. Better homepage routing increases action rate, improves cross-product conversion, and reduces browse-without-action sessions.
Session Economics
Homepage → action rate+18 to +28%
Browse-without-action reduction-15 to -25%
Cross-product conversionHigher sportsbook-to-casino transitions
Generic promo suppressionImproves relevance and trust
Wallet friction avoidanceLess distraction when funds are already available
Key insight: the business win is not “more banners.” It is turning the homepage into a real-time decision point that gets the player to the right action faster.
Per-Session Outcome
4m browse
Generic homepage
drift and compare
→
bet in <20s
Redis-powered homepage
action-first route
Stage 8: Outcome
Same homepage. Different decision layer.
Without Redis, the site shows generic popular modules. With Redis, the first surface is assembled around the player’s live moment.
Generic Homepage
MR
Welcome back, Mateo
Top promotions
Popular offers
Same order for broad segments
Browse
#1
Generic deposit bonus
No wallet or intent awareness
Skip
#2
Popular slots row
No live sports urgency
Scroll
4m
browse time
0
actions
high
drift risk
Redis-Powered Homepage
MR
Welcome back, Mateo
Next best lobby
Live football now
Slip recovery + match starts in 6 min
Why this leads
SLIP
Resume unfinished bet
Existing live intent
Bet
LIVE
Favorite match starts soon
Urgency + affinity aligned
Watch
Context assembled in Redis
Homepage route confidence: 94%
Wallet state, slip state, match urgency, and cross-product behavior point to sportsbook first.
<20s
to action
94%
confidence
higher
session value
Stage 9: Architecture Recap
Redis turns the homepage into a real-time decisioning surface
Wallet, sportsbook, casino, bonus, and identity systems stay in place. RDI and Redis Feature Form make them operational. Redis RAM and Redis Flex serve the unified context. The decision stack picks the best next homepage route in milliseconds, before the player drifts.
Data Sources

Player Identity

Profile, device, geography, language

Wallet + Payments

Balance, deposit recency, withdrawal state

Sportsbook Engine

Open bets, favorite leagues, live markets

Casino + Slots

Last game, live tables, session depth

Kafka / Live Ops

Odds changes, event starts, promo triggers

Ingest Layer

Redis Data Integration (RDI)

Syncs wallet, profile, bonus, and product state from operational systems

Redis Feature Form

Serves online features for intent, retention, and cross-product steering

Unified Context Layer

Redis RAM

Hot session, active bet slip, live event urgency

Redis Flex

Warm cross-product history, behavioral embeddings, and long-tail behavior

Feature Store

Product affinity, churn, bonus responsiveness, RG signals

Redis Context Retriever

Assembles the Player 360 — session state, product affinity, and betting history — and exposes it as structured MCP tools for the decision engine

Decision Engine

Eligibility Rules

Geo, age, product, risk and responsible gaming guardrails

NBA Ranker

Engagement, retention, and conversion weighting

Redis Search

Player-to-product semantic matching

Policy Arbitration

Balances growth, trust, and safer-play priorities

Output Surfaces

Homepage Hero

Next best lobby, event, or product row

Sportsbook

In-play focus, slip recovery, top market row

Casino Lobby

Live tables, slots, recent play

Push / CRM

Session recovery and re-entry prompts

↺
Learn:  Clicks, launches, deposits, bet placements and dismissals retrain the models and update policy in Redis.
Decision Target
<15 ms
Primary Surface
Homepage + lobby routing
North Star
Session start → action
Stage 2: Session Start
The player lands and the platform has seconds, not minutes
Mateo lands on the homepage at 8:42 PM with an active wallet, an unfinished live bet slip, a strong casino affinity on weekends, and a Copa Libertadores match starting in six minutes. The platform needs to decide whether his next best experience is sportsbook, live casino, slots, or wallet action.
Homepage Session Event
MR
Mateo Ruiz
Spanish-language player | Active wallet | Sports + live casino crossover | 11 sessions this month
HIGH INTENT
Eventhomepage_session_start
Time8:42 PM local (prime live sports window)
Wallet balanceMXN 1,850
Open bet slip1 unfinished in-play slip
Last product usedLive casino roulette, 2 nights ago
Favorite patternFootball midweek, live casino weekends
Last outcomeBrowsed 4 minutes, no action in prior visit
Why This Moment Matters
The homepage is not just a navigation surface. It is a decision surface. The first row determines whether the player bets, deposits, crosses into another product, or leaves.
A generic homepage shows the same popular modules to everyone. A real-time decisioning homepage uses live context to decide which experience should lead.
The opportunity: Mateo has live-sports urgency, unfinished bet intent, and cross-product history. The right surface can turn a homepage visit into immediate action.
Without Redis: the site falls back to stale merchandising and popularity rows. Mateo scrolls, compares, and drifts.
Stage 3: Ingest
Operational systems and streams flow into Redis
RDI synchronizes wallet state, bonus state, bet history, product history, and account context from operational repositories. Redis Feature Form serves online features built from telemetry, product behavior, and live event data. Redis becomes the live context layer for the session start decision.
Source Systems → Redis
ID
Account + Identity
Profile, device, language, geography, verification state
→
WLT
Wallet + Payments
Balance, recent deposits, withdrawal state, preferred payment rails
→
SBK
Sportsbook Engine
Open slips, favorite leagues, live markets, odds movement
→
CAS
Casino + Live Tables
Recent games, dwell depth, session frequency, dealer/table affinity
→
BON
Promotions Engine
Bonus eligibility, active offers, wagering requirements, suppressions
→
KFK
Kafka or Redis Streams + Live Ops
Match start times, odds changes, clickstream, dismissal signals
→
Pipeline Status
Profile syncSub-second
Wallet + bonus stateContinuous CDC
Sports + casino telemetryStreaming
Redis Feature Form parity100%
Cold-start fallback<3%
Decision dependencyServed from Redis
Additive architecture: identity, wallet, sportsbook, casino, and bonus systems stay in place. Redis is the low-latency operating layer that makes them act together.
Stage 4: Context
Redis assembles the live player context
Historical behavior and live-session behavior meet in the same path. That is what makes the homepage a real-time decision surface instead of a static merchandising page.
Redis RAMRedis FlexRedis Context Retriever
Historical Context
Primary affinityFootball in-play + live roulette
Average deposit cadence2 per week before large matches
Cross-product patternSports first, casino after settlement
Favorite competitionCopa Libertadores
Bonus responsivenessLow to generic banners, high to contextual offers
Churn signalModerate — 2 recent browse/no-action sessions
Live Session Context
Match urgencyFavorite team starts in 6 minutes
Slip stateOne unfinished in-play bet
Wallet readinessBalance sufficient, no deposit needed
Casino triggerHigh likelihood after bet settlement
Current intentSports-led, high action probability
Risk / RG stateNo active suppressions
Context signal: Redis Context Retriever assembles the Player 360 — session state, product affinity, and betting history — so the decision engine has exactly what it needs. The next best homepage is not the most popular module. It is the module most likely to convert this session into action right now.
Stage 5: Feature Serving
Online features hydrate in milliseconds
Redis Feature Form serves the features that matter for homepage and lobby routing: sportsbook urgency, casino crossover likelihood, deposit need, bonus responsiveness, and churn risk. Redis RAM serves the hot path. Redis Flex contributes broader behavioral context.
sportsbook_urgency_score
Likelihood the player acts immediately on live sports if surfaced first
0.930.3 ms
casino_crossover_propensity
Likelihood the player moves from sportsbook to casino in the same session
0.710.4 ms
unfinished_slip_salience
Strength of unfinished action recovery on the homepage
0.880.3 ms
deposit_need_score
Probability the player needs wallet action before betting
0.120.2 ms
bonus_response_contextual
Probability the player responds to contextual vs generic promo placement
0.740.4 ms
browse_exit_risk
Probability the player exits without taking action
0.410.5 ms
Feature Serving Performance
Features Hydrated
196
P99 Lookup
2.0 ms
Train / Serve Parity
100%
Hot-path storage
RAM + Flex
Stage 6: Ranking
The platform ranks the next best homepage
The decisioning stack chooses what should lead the session now — sportsbook hero, unfinished slip recovery, live casino row, or promotional module. Redis supplies the unified context needed to make that choice in the live moment.
4 homepage routes evaluated
policy-aware and risk-aware
best next experience surfaced first
#1 Winner
SPORTSBOOK HERO
Live football + unfinished slip recovery
Highest immediate action probability for this session
Combines match-start urgency with unfinished action recovery and no wallet friction.
Decision score0.94
#2 Cross-product
LIVE CASINO
Roulette follow-on row
Strong secondary path if sportsbook action completes
Good fit, but not the strongest first-screen action for this exact moment.
Decision score0.79
#3 Suppressed
BONUS TILE
Generic deposit bonus module
Suppressed because wallet need is low
The player already has funds. A generic bonus tile creates distraction, not conversion.
Decision score0.31
Stage 7: Business Impact
The homepage becomes a decision surface, not a merchandising page
The value is not just cosmetic optimization. Better homepage routing increases action rate, improves cross-product conversion, and reduces browse-without-action sessions.
Session Economics
Homepage → action rate+18 to +28%
Browse-without-action reduction-15 to -25%
Cross-product conversionHigher sportsbook-to-casino transitions
Generic promo suppressionImproves relevance and trust
Wallet friction avoidanceLess distraction when funds are already available
Key insight: the business win is not “more banners.” It is turning the homepage into a real-time decision point that gets the player to the right action faster.
Per-Session Outcome
4m browse
Generic homepage
drift and compare
→
bet in <20s
Redis-powered homepage
action-first route
Stage 8: Outcome
Same homepage. Different decision layer.
Without Redis, the site shows generic popular modules. With Redis, the first surface is assembled around the player’s live moment.
Generic Homepage
MR
Welcome back, Mateo
Top promotions
Popular offers
Same order for broad segments
Browse
#1
Generic deposit bonus
No wallet or intent awareness
Skip
#2
Popular slots row
No live sports urgency
Scroll
4m
browse time
0
actions
high
drift risk
Redis-Powered Homepage
MR
Welcome back, Mateo
Next best lobby
Live football now
Slip recovery + match starts in 6 min
Why this leads
SLIP
Resume unfinished bet
Existing live intent
Bet
LIVE
Favorite match starts soon
Urgency + affinity aligned
Watch
Context assembled in Redis
Homepage route confidence: 94%
Wallet state, slip state, match urgency, and cross-product behavior point to sportsbook first.
<20s
to action
94%
confidence
higher
session value
Stage 9: Architecture Recap
Redis turns the homepage into a real-time decisioning surface
Wallet, sportsbook, casino, bonus, and identity systems stay in place. RDI and Redis Feature Form make them operational. Redis RAM and Redis Flex serve the unified context. The decision stack picks the best next homepage route in milliseconds, before the player drifts.
Decision Latency
<15 ms
Outcome
Homepage → action
Redis Role
Operational context layer
This is the mindset shift from cache to decisioning infrastructure. Redis is not just accelerating page load. Redis is assembling live context fast enough for the platform to decide what experience should lead the session.
Press ← → or click to navigate