Lucky Bets – Casino Games Aggregator

Overview of the project

Lucky Bets came to us with a familiar problem in regulated iGaming: 15 game providers, 15 different APIs, 15 different lobby states and a reconciliation backlog that grew faster than the team could clear it. The operator had built revenue but the platform was straining under the integration tax. We were brought in to consolidate everything onto one aggregation layer with sub-100ms odds-style latency for casino lobbies, real-time analytics and a backoffice that did not require a senior engineer to interpret.

The challenge

Casino aggregation looks simple on a slide and never is. Each provider exposes different game metadata schemas, different bonus and free-round mechanics, different RTP reporting cadences and different RGS reconciliation windows. Lucky Bets needed a single API surface for the lobby, a single source of truth for spin events and a single audit trail for the regulator. They had three weeks of free runway before the next regulator review.

Engineering approach

We built a Rust-based aggregation gateway sitting between provider RGS endpoints and the operator wallet. Provider responses normalised into a canonical event model. Spin, bet, win and bonus events written into an event-sourced ledger keyed by the player session token. The lobby got a single GraphQL surface returning provider-agnostic game catalogue plus RTP plus jurisdictional eligibility filters. Reconciliation moved from a nightly batch into continuous streaming across providers.

Tech stack

• Backend: Rust services (tokio plus axum) running on Kubernetes (AWS EKS), PostgreSQL with logical replication for the event ledger, Redis for session state and lobby cache, Apache Kafka for inter-service event streaming.
• Frontend: Next.js lobby with React Query, server-side rendering for SEO-relevant pages, Web Workers for live RTP recalculation across active sessions.
• Infrastructure: Cloudflare edge cache, OpenTelemetry traces, Grafana dashboards, Prometheus alerting. PCI DSS Level 1 segmentation between cashier and aggregation services.

Key features delivered

Casino games aggregation

One API for 100+ providers. Game catalogue, bonus mechanics, RTP, jurisdiction filters, free-spin allocation and provider-side promotional triggers all routed through a unified endpoint. Operators add a new provider in days, not weeks.

Real-time analytics

Per-spin event streaming into a real-time analytics layer with sub-second freshness. Dashboards for live exposure per provider, bonus utilisation across promotional campaigns and player segmentation by RTP cohort. The trading and risk teams stopped waiting for nightly batch jobs.

Scalable APIs

The aggregation layer absorbs traffic spikes during major promotional events without performance degradation. Designed for 4x baseline load as headroom. Per-endpoint rate limiting plus circuit breakers per provider so a single provider degradation never takes down the whole lobby.

Business results

• 3,000+ games integrated through the unified aggregation layer across 100+ providers, with new providers added in days.
• 75% reconciliation time cut. Nightly batch reconciliation moved to continuous streaming. Finance close went from 8 hours to 2.
• 4x traffic spikes handled during major promotional events without latency degradation or queue backups.
• Sub-100ms latency for lobby catalogue and game launch endpoints across all providers.
• Zero downtime cutover. Migration from the legacy aggregator ran in parallel with no impact on live players.

Why it worked

One team owning the full stack. No vendor handoff for the aggregation layer, no offshore contractor pod for backend services, no marketplace of integrations to debug at 2 AM. Engineering, compliance, infrastructure and frontend shipped under one roadmap with one squad. The operator kept the codebase. The licence stayed with them. The boring infrastructure became the product.