DEV Community

Nexx
Nexx

Posted on • Originally published at nexx.games

Inside the Cricket Exchange Panel: The System Design of South Asia's Biggest Betting Product

The system design behind South Asia's dominant betting product — for engineers curious what "exchange panel" actually means technically.

If you've seen job posts or client briefs from South Asia mentioning "exchange panels" and wondered what they are: it's a betting exchange (back/lay, position matching, commission model) wrapped in a multi-tenant credit hierarchy. The interesting engineering lives in three places.

1. The credit hierarchy is a ledger problem

Access is ID-based: an agent creates player IDs funded from the agent's credit line, agents are funded by masters, masters by the admin. Every bet settlement must propagate balance changes up a chain of 3–5 levels atomically. In practice: a double-entry ledger with per-level P&L rollups, where a session settling mid-match triggers cascading updates across thousands of accounts — and every level's dashboard must agree to the paisa, or the network's trust (the actual product) collapses.

2. Ball-by-ball repricing is an event-stream problem

Cricket session markets — runs in N overs, next-wicket, per-player totals — reprice on every delivery. The feed layer (commonly "Diamond-format" APIs: match odds, bookmaker, fancy, session, result endpoints) pushes updates that must fan out to all connected clients sub-second, with automatic market suspension on wicket events before stale-price snipes land. Suspension latency is directly measurable in money.

3. Risk is a real-time aggregation problem

The admin book needs live exposure per market/user/agent with limit enforcement and one-click suspension. Add bet-delay windows (anti-sniping), winning-account profiling, and P&L by downline. This module — not the frontend — decides operator profitability.

The delivery reality

Almost nobody builds this from scratch: ready panels (multi-tenant white label) deploy in 1–3 weeks with feeds, casino provider APIs (Evolution/Ezugi et al.) and theme families pre-integrated; custom single-tenant deployments take 4–8 weeks. The build-vs-buy economics mirror what I covered in the sportsbook cost breakdown.

Operator-side guide with the full checklist: How to Launch a Cricket Exchange Panel in 2026

Top comments (0)