Skip to content

An in-play betting engine built like a trading desk

How a casino & sportsbook operator came to run its live book on an engine that treats every market like a trading position — serving hundreds of thousands of end users with sub-second settlement.

Custom softwareDedicated team100k+ end users
<300ms
bet-to-settlement latency
100k+
end users served
peak-proof
no downtime through top events
M1
RG controls designed in

The situation

A casino & sportsbook operator wanted to grow its in-play offering — live odds that move with the game, cash-out mid-event, markets that open and close in seconds. Its incumbent platform was built for pre-match betting: odds updated on a polling cycle, settlement ran in batches, and traders managed risk from spreadsheets refreshed by hand. Every top fixture was a stress test the platform barely passed.

The problem underneath the problem

In-play betting is not a faster version of pre-match betting — it is a different discipline. Odds are a live price; open bets are open positions; a stale feed is unpriced exposure. The operator's real problem was that its systems had no concept of a position. The diagnosis reframed the build: not a faster sportsbook, but a trading floor with a sportsbook attached.

What we built

An event-driven engine where every market is a book and every bet a fill. Odds move on market events, not timers; settlement is computed the moment an outcome resolves; and the trading desk watches live exposure per market, per event and per customer segment, with automated limits that pause a market before risk runs — and trader overrides for judgment calls the rules can't make.

System shape: real-time odds and settlement pipeline · per-market exposure dashboards · automated risk limits with trader override · responsible-gaming controls and full audit trail from milestone one

The hard part

Peak load is not average load. A top event compresses a day's traffic into stoppage time, and the one moment the system must not fail is the moment everyone is using it. The engine was load-tested against multiples of the operator's biggest recorded event before each milestone was accepted — and the settlement path was kept deliberately boring: no clever caching between a resolved outcome and a customer's balance.

Results that held

The live book now runs through peak fixtures without incident, bet-to-settlement stays under 300 milliseconds at load, and the trading desk manages risk from dashboards instead of spreadsheets. Responsible-gaming controls and a complete audit trail were part of milestone one, not a compliance retrofit. The engagement continues as a dedicated team extending the engine to new market types.

Running real-time money on batch-era systems?

The diagnosis session is free — and it starts by measuring your peak, not your average.