Game Studio Distribution Strategy: Aggregator vs. Direct Integration and the Compliance Trade-offs That Determine the Right Model
Choosing between aggregator and direct integration isn't just a commercial decision — it determines who holds the compliance burden. Learn which model fits your studio's size and regulated footprint.
Every game studio distributing content into regulated markets faces the same structural decision: route games through a licensed aggregator, or build direct integrations with operators. The choice looks commercial on the surface, but it has binding compliance consequences that determine how many licences you must hold, how certification costs are allocated, and who carries enforcement exposure when a game fails a technical audit.
The aggregator model does not transfer your compliance obligations, it layers a second licensee between you and the regulator without eliminating your own authorisation requirements. Understanding precisely where that boundary falls across the UKGC, MGA, AGCO, AGLC, and Spelinspektionen frameworks is the starting point for any distribution strategy that holds up under regulatory scrutiny.
What Regulators Actually Require of a Game Studio
The threshold question is whether your studio must hold its own authorisation in each market, independent of the aggregator or operator you supply. Across every major regulated market except Spain, the answer is yes.
Under the Gambling Act 2005, any business that manufactures, supplies, installs, or maintains gambling software must hold a gambling software licence issued by the UK Gambling Commission. This is an entity-level licence, not a product approval. A studio whose titles reach British-facing remote operators through an aggregator’s remote game server (RGS) must hold that licence in its own name. UKGC Licence Conditions and Codes of Practice condition 2.3.1 then requires all gambling software licensees to comply with the Commission’s Remote Technical Standards (RTS, last updated 31 October 2025), including submitting games through an approved testing programme. The aggregator’s technical stack does not satisfy that requirement on the studio’s behalf.
The MGA framework under the Gaming Act (Chapter 583 of the Laws of Malta) and Directive 3 of 2018 (V2, October 2021) uses a sharper definitional structure. A “game provider” is defined as a B2B licensee that provides a critical gaming supply in terms of paragraph (a) of point 3 of the First Schedule to the Gaming Authorisations Regulations. That definition captures any studio supplying game content, regardless of whether that content is routed through an aggregator. Directive 3, Article 27(1) states explicitly that licensees obtaining a critical gaming supply from an outsourcing service provider must ensure that such provider is duly in possession of a B2B licence or a recognition notice. An aggregator distributing your titles is not relieving you of B2B licence obligations, it is creating a chain in which both the aggregator and the originating studio must be authorised.
Source: MGA, Directive 3 of 2018, Gaming Authorisations and Compliance Directive, Article 27(1) and definition of “game provider”, V2 October 2021.
In Ontario, the AGCO’s Registrar’s Standards for Internet Gaming (updated 29 May 2025) reach the same conclusion through Standard 1.22, which prohibits operators and gaming-related suppliers from contracting with any supplier that would require registration under the Gaming Control Act 1992 without holding that registration. A studio providing game content into Ontario must be registered as a gaming-related supplier under the GCA, whether or not an aggregator sits between it and the operator.
Alberta’s AGLC Standards and Requirements for Internet Gaming (SRIG, issued 14 January 2026) establish an equivalent structure. Goods or Services Suppliers must hold a registration to perform functions including making or supplying equipment or services to operate or support the operation of an iGaming site. A game studio whose content feeds into an Alberta-facing operator, through an aggregator or directly, falls within that definition and requires its own registration.
Where the Aggregator Model Genuinely Reduces Compliance Burden
Knowing that licences cannot be borrowed, studios can still extract real compliance value from aggregators, provided they understand which obligations the aggregator absorbs and which remain with the studio.
The most significant relief is API integration overhead. A studio distributing through an aggregator’s RGS maintains a single certified technical connection rather than building and maintaining separate integrations for every operator. Each direct operator integration requires its own technical onboarding, change-management notification obligations, and, in jurisdictions such as Sweden, separate system certification review if the integration constitutes a material change to a certified gambling system. Under SIFS 2022:3 (Spelinspektionen’s technical regulations, May 2025 guidelines), suppliers’ technical equipment and games form part of the applicant’s gambling system and must be included in the system certification. Centralising delivery through one aggregator integration substantially compresses the certification surface that must be re-tested when the studio updates a game or changes a technical parameter.
In the MGA framework, aggregators that are themselves B2B licensees can operate as “resellers” of game content under Article 19(2) of Directive 3 of 2018, which states that the provisions on game additions and new game providers also apply to a B2B licensee that obtains games from one or more game providers to resell or otherwise provide to other licensees. This means an MGA-licensed aggregator can add your studio’s titles to its product catalogue and distribute them to its B2C operator clients, handling the five-day notification obligation to the Authority when new games from an existing authorised provider are added. The studio does not need to notify the MGA for each individual operator onboarding, that obligation shifts to the aggregator’s compliance team.
A B2C licensee that obtains the services of one or more game providers in order for them to provide it with games for a gaming vertical which it is already approved to offer shall notify the Authority forthwith and in no case later than five (5) days following the addition of such games.
For studios with a broad operator footprint across dozens of MGA-licensed B2C operators, consolidating delivery through one or two aggregators reduces notification management from a potentially continuous obligation to a manageable structural feature of the aggregator relationship. In practice, compliance teams that map this correctly can eliminate a category of routine regulatory correspondence entirely.
The MGA Material Supply Certificate: An Underused Strategic Tool
Directive 3 of 2018, Article 27(2) provides that B2B licensees wishing to provide material supplies may apply to the MGA for approval of those material supplies as part of the B2B licence. The application is voluntary, and the MGA Compliance Audit Manual confirms that auditors will check whether all companies providing material gaming supplies hold either a material supply certificate or an Authority-approved case-by-case approval.
For game studios, this creates a valuable certification pathway that is distinct from the main B2B licence. A studio can seek a material supply certificate for its RNG infrastructure or core game engine. Once certified, that certificate is recognised by B2C licensees using it, enabling aggregators to distribute the studio’s titles to their operator clients without each operator needing to conduct its own case-by-case technical assessment. The Player Protection Directive (Directive 2 of 2018) reinforces this: B2C licensees whose games are hosted and managed by an approved B2B licensee may have the obligation to monitor average return-to-player percentages fulfilled by the B2B licensee on their behalf. An aggregator holding games from a studio with a valid material supply certificate can absorb that operational monitoring obligation, reducing the per-operator compliance tail for the studio’s content.
Studios that skip the material supply certificate route and supply directly, title by title, into multiple aggregators without a certified core infrastructure face fragmented case-by-case review cycles with each aggregator’s compliance function, a material source of delay in commercial launch timelines.
Direct Integration: When It Makes Compliance Sense
Direct integration with operators is appropriate when a studio has a small, stable operator roster, a mature in-house compliance function, and a single-market or dual-market footprint. The compliance overhead of direct integration is quantifiable: per-jurisdiction entity licence or registration, per-game technical certification through an approved testing facility (ATF), change-management notification for each material game update across each operator integration, and ongoing reporting obligations to the relevant regulators.
Under the AGCO Registrar’s Standards (Standard 1.19), operators are responsible for the actions of third parties they contract with, and must require those third parties to conduct themselves as if they were bound by the same laws, regulations, and standards. In a direct integration, the studio is that third party, and operators will contractually pass through AGCO compliance obligations directly. Studios supplying one or two Ontario operators directly will typically find that compliance terms in the master supply agreement are manageable. Studios supplying fifteen operators directly across Ontario, Alberta, and the UKGC simultaneously face a multiplying overhead: each new jurisdiction adds a registration or licence, each new operator adds a contractual compliance schedule, and any game update triggers change notifications across all active integrations.
The AGLC SRIG (2026-03-17) draws an important technical distinction that affects direct integrations specifically. Where a registered operator uses a third-party registered Goods or Services Supplier running critical gaming systems, the operator’s annual Technology Compliance Confirmation does not include that supplier’s technology, the supplier must provide its own confirmation. This means studios running their own game delivery infrastructure for direct integrations carry an independent Technology Compliance Confirmation obligation with AGLC, adding to the annual reporting cycle.
Key obligation: Under the AGLC SRIG (Section 4), registered operators and registered Goods or Services Suppliers running critical gaming systems must each provide AGLC with an annual Technology Compliance Confirmation. A studio operating a direct-integration RGS for Alberta carries this obligation independently of its operator clients.
Certification Reuse: The Most Misunderstood Efficiency
Studios entering multiple regulated markets look for certification reuse, the ability to carry a technical approval granted in one jurisdiction into a second jurisdiction with minimal retesting. The economics of this calculation depend heavily on whether distribution is via aggregator or direct, because the certification is attached to the game and its delivery infrastructure, not to the commercial relationship between studio and operator.
GLI certification reports, for example, are specific to the items submitted and the test methods applied. The GLI terms confirm that the certification established by a report applies exclusively to tests conducted on the specific items submitted. A studio that certifies its game engine through GLI for the UKGC market has a certification artefact. Whether that artefact is accepted in Ontario or Alberta depends on whether the AGCO or AGLC recognises the testing laboratory and whether the test was conducted against the relevant standard for that jurisdiction.
Aggregators with established multi-jurisdictional approvals frequently hold ATF-certified game delivery infrastructure that covers multiple markets. A studio distributing through such an aggregator may find that the aggregator’s system-level certification provides the compliance envelope within which the studio’s game content sits, reducing the studio’s certification obligation to game-level RNG and mathematics testing rather than full system certification. This is a material cost and timeline difference, particularly for studios entering four or more regulated markets concurrently.
The Swedish market illustrates this dynamic clearly. Under SIFS 2022:3 and the May 2025 Spelinspektionen guidelines, suppliers’ technical equipment and games form part of the licensed operator’s gambling system and must be included in that system’s certification by an independent, accredited testing house. A game studio supplying directly must ensure its games and delivery infrastructure are incorporated into each Swedish operator’s system certification scope. Supplying via a Spelinspektionen-aware aggregator whose RGS is already certified substantially reduces the studio’s individual certification exposure, the studio’s obligation narrows to ensuring its game content meets SIFS technical requirements, rather than certifying an entire delivery stack per operator relationship.
How Studio Size and Market Footprint Drive the Right Model
The compliance cost of each distribution model scales differently with size, and the optimal model shifts at predictable thresholds.
An early-stage studio launching its first three to five titles into one or two regulated markets should default to aggregator distribution. The entity-level licence obligation (MGA B2B, UKGC gambling software, AGCO gaming-related supplier) cannot be avoided regardless of distribution model, but every other compliance element, change-management notifications, per-operator contractual compliance schedules, Technology Compliance Confirmations, system-level certification, is substantially absorbed by the aggregator’s existing compliance infrastructure. The commercial cost of the aggregator’s revenue share is almost always lower than the cost of building equivalent in-house capability from scratch.
A mid-size studio with twenty or more operator relationships across three or more regulated markets faces a more complex calculation. At this scale, direct integrations with the largest operators by revenue may generate commercially attractive terms that justify the per-integration compliance overhead. Simultaneously maintaining aggregator distribution for smaller operator relationships and secondary markets is a standard hybrid model. The compliance team’s job at this stage is to maintain a consolidated change-management and notification register that covers all channels, because a game update that triggers a 5-day notification to the MGA under Directive 3 of 2018, or a change-management process under the AGLC SRIG, must be tracked across every active distribution path simultaneously, not just the direct integrations.
A large studio with fifty or more operator relationships and full-market licences in the UKGC, MGA, AGCO, and AGLC markets will typically operate primarily through direct integrations with Tier 1 operators while maintaining aggregator relationships for market-entry in new jurisdictions. The compliance team at this size needs explicit governance around the distinction between obligations that attach to the studio’s own licences and obligations that have been contractually allocated to aggregator partners, and needs written confirmation from aggregator partners that those obligations are being met, because the studio’s B2B licence remains at risk if an aggregator distributes its content in breach of jurisdictional requirements.
A licensee shall take responsibility for third parties to whom it outsources any aspect of its business related to its licensed activities.
Source: MGA, Directive 3 of 2018, Gaming Authorisations and Compliance Directive, Article 26, V2 October 2021.
Contractual Allocation of Compliance Obligations in Aggregator Agreements
Both distribution models require studios to manage compliance obligations contractually, but the nature of those obligations differs. In a direct integration, the studio is in privity with the operator and compliance terms flow directly. In an aggregator relationship, the studio must ensure its distribution agreement explicitly allocates responsibility for notification obligations, change-management processes, RTP monitoring, and technical standards compliance between the studio and the aggregator.
Under MGA Directive 3 of 2018, an aggregator that adds the studio’s games to its product vertical must notify the MGA within five days. That notification obligation sits with the aggregator, but if the aggregator fails to comply, the MGA may determine under Article 26 that responsibility lies with the studio, the aggregator, or both. Studios distributing through aggregators should require contractual confirmation that the aggregator’s compliance team manages these notifications, with evidence of submission upon request.
For RTP monitoring, MGA Directive 2 of 2018 (Player Protection Directive) allows B2C licensees using an approved B2B licensee to have that B2B licensee fulfil the monitoring obligation on their behalf. An aggregator acting as the B2B delivery layer for a studio’s games can absorb RTP monitoring contractually. Studios should confirm this allocation in writing and verify it is operative before relying on it in any regulatory submission.
AGCO Standard 1.20 requires operators and gaming-related suppliers to maintain a list of suppliers providing goods or services in relation to lottery schemes, available to the Registrar on request. An aggregator is a supplier in this context. Studios distributing through aggregators into Ontario should be listed on the operator’s supplier register, and should in turn maintain their own register of the operators ultimately served through each aggregator, to the extent they can obtain that information, to support any AGCO compliance enquiry.
For Ontario operators and studios looking for broader context on the regulatory framework governing these relationships, the Ontario iGaming compliance guide sets out the full scope of AGCO obligations that flow through the supply chain. Studios targeting the MGA ecosystem should review the MGA licensing guide for the B2B licence structure within which both direct and aggregator distribution strategies must operate.
The Practical Decision Framework
Translating regulatory requirements into a distribution decision requires answering four questions in sequence. First, which jurisdictions do you intend to supply? Every target market determines the entity-level authorisation you must hold regardless of distribution model. Second, how many operator relationships do you expect to maintain per market? Below ten relationships per market, aggregator distribution almost always yields a lower total compliance cost. Above twenty-five, hybrid models become appropriate. Third, do you have or intend to build an in-house compliance function capable of managing per-integration change notifications, annual Technology Compliance Confirmations, and game-level certification cycles? If not, aggregator distribution is the rational choice until that capability exists. Fourth, what is your game update cadence? Studios releasing frequent updates face proportionally higher change-management compliance overhead under direct integration, that overhead is substantially reduced through aggregator distribution where the aggregator’s system certification provides the delivery envelope.
Studios operating primarily in Europe’s regulated markets should seek specialist legal advice on the specific B2B licence structures required in each target jurisdiction before committing to either distribution model. The authorisation requirements described in this article reflect the frameworks as published, jurisdiction-specific application and any recent regulatory guidance may affect the analysis for particular supply arrangements.
Key Resources
MGA Gaming Authorisations and Compliance Directive (Directive 3 of 2018, V2 October 2021), Malta Gaming Authority. Governs B2B licence obligations, critical gaming supply chains, outsourcing responsibility, and the material supply certificate pathway.
UKGC Remote Gambling and Software Technical Standards (RTS, updated 31 October 2025), UK Gambling Commission. Sets the technical standards applicable to all gambling software licence holders and their game content.
AGCO Registrar’s Standards for Internet Gaming (updated 29 May 2025), Alcohol and Gaming Commission of Ontario. Establishes Standards 1.18, 1.22 governing third-party supply chain obligations for operators and gaming-related suppliers in Ontario.
AGLC Standards and Requirements for Internet Gaming (SRIG 2026-03-17), Alberta Gaming, Liquor and Cannabis Commission. Defines Goods or Services Supplier registration requirements and Technology Compliance Confirmation obligations for Alberta’s iGaming market.
Spelinspektionen Guidelines for SIFS 2022:3 (May 2025), Swedish Gambling Authority. Defines sub-supplier certification obligations and the scope of system certification for B2B game content providers in the Swedish online gambling market.
Matt Denney
Editorial · gamingcompliance.io
Reads the primary source so you don't have to. Fifteen years inside iGaming compliance: operator, supplier, and crown-corporation lottery.
The Tuesday brief, every week.
One email. Every regulator change we surface, every standard we re-index, every enforcement decision we read. No marketing, no fluff.
Unsubscribe with one click. We'll never share your address.