Article

Game aggregators vs direct provider integrations: how a casino lobby is actually assembled

A technical explainer of direct studio integrations, aggregators, hosted games, wallets, round IDs and why provider availability can change in groups.

Published October 1, 2026Updated October 1, 2026By NivaroBet EditorialEditorial policy

6 minREAD18SECTIONSSourcedEVIDENCE

Source & verificationUK Gambling Commission — software and game-host licensingSource type: primary_or_officialStatus: verifiedVerified October 1, 2026Open source

pillar:gamestopic:gamestopic:providerstopic:transparencylong-formresearch-gradehuman-editedwave:11

Game aggregators vs direct provider integrations: how a casino lobby is actually assembled

Game Aggregators vs Direct Provider Integrations: How a Casino Lobby Is Actually Assembled

Direct integration: operator connects to the studio

Aggregation: one connection, many studios

Aggregator does not mean game developer

Hosted games add another model

Remote game launch usually creates a signed handoff

Wallet models change the integration

Round IDs are the bridge in support cases

Why a whole provider can disappear at once

Why only some titles disappear

Aggregation affects performance, but not in one predictable direction

Certification and licensing still follow the regulated roles

What the operator controls

What the studio controls

What the aggregator controls

Why provider counts are easy to inflate

NivaroBet data model

A failure map for reviews

Sources

Related articles and guides