Game providers
You make games; the operators on the network bring players. One integration with Aggregator.gg makes your catalog available for distribution to eligible operators, subject to enablement, jurisdiction and commercial access, without a single per-operator project on your side. This page is the orientation; the provider docs, starting at Provider onboarding, carry the full track.
The business model
Section titled “The business model”Operators integrate once against one canonical contract, and each provider’s launch protocol, callback shape, and signature scheme is translated into that contract by a connector our team builds together with yours. You do not rewrite your game server against our API; the connector meets your protocol where it is.
Money settles through that same contract: your games send signed bet and win calls, the platform verifies every signature before anything moves, and every amount is an integer in the currency’s minor units. HMAC-SHA256 signs normalized operator callbacks; your provider-side authentication and replay rules are fixed in the connector agreement. Commercial terms are agreed directly between us; these docs carry the technical contract.
What you can use today
Section titled “What you can use today”- Assisted integration: a connector built for your protocol by our team, validated against staging before production.
- A catalog operators filter by: the metadata in Catalog requirements, including RTP with a named source, certified markets, blocked countries, currencies, and bet limits.
- The runtime contract: launch and session calls in, signed bet and win out, specified in Runtime expectations.
- A joint certification run: the happy path plus the failure scenarios, driven together on a sandbox operator before traffic opens, described in Certification and go-live.
- Free rounds: games that support them are flagged in the catalog, so operators can find and issue on them.
How you integrate
Section titled “How you integrate”The track is assisted end to end: documentation exchange, catalog handover, connector build against your test bench, the certification run, and a gradual traffic open watched by both teams. Each stage gates the next, and who does what at each stage is laid out in Provider onboarding. What you prepare is short: the game catalog with its metadata, your protocol documentation, a reachable test environment, and a technical contact.
Where to start
Section titled “Where to start”Read Provider onboarding first; it is the map of the whole track and ends with the contact step. If you prefer to start the conversation right away, write to support@aggregator.gg with your catalog and a technical contact, and we will pick the track up from stage one together.