UK gaming software license: define your B2B permissions
For a game studio, platform provider or content host, the first step is the same. Establish what your software does, which entity supplies it and how it reaches licensed operators. Those facts determine the UKGC licensing assessment, whatever label the commercial contract uses. MGL Solutions can help assess the proposed supply model and coordinate the application work. Begin with a product description, an entity chart and a diagram of where the software and the gaming transactions run.
Which software activities need assessment?
The UKGC remote gambling software permission covers manufacturing, supplying, installing or adapting gambling software through remote communication. The official software activity page sets out its scope.
Look at what each component does. Software that accepts or records gambling transactions, determines results or allocates winnings raises different questions from a general-purpose infrastructure tool. The UKGC's software definition guidance separates gambling-specific functions from ordinary business applications, such as general CRM or analytics.
For a platform with several modules, assess each module and its interfaces. Calling the whole product “infrastructure” can hide a component that controls game results or settlement.
Map functions to legal entities
Use this working map before you choose the applicant entity. It is a preparation tool, and several rows can fall under one license.
Question | Record in the map | Evidence to check |
|---|---|---|
Who creates and changes the gambling logic? | Entity, product owner and release authority | Development agreements and change permissions |
Who supplies the deployed software? | Contracting supplier and recipient | Supply agreements and software delivery route |
Where does the game or betting service run? | Host, system location and operating entity | Architecture and hosting agreements |
Who contracts with players? | Entity named in customer terms | Terms, account ownership and operating model |
Who can stop a faulty release? | Responsible person and escalation route | Release controls and incident process |
A group may own the intellectual property in one company, develop the product in another and contract through a third. Name the entity behind each role. Neither the group brand nor a certificate bearing a product name tells a reviewer who holds the license responsibility.
Software, host and customer-facing operator
A software supplier permission alone does not authorize a consumer casino business. The remote casino game host permission is relevant to qualifying suppliers that host games through other operators. Its conditions include holding a gambling software operating license and having no direct contracts with the players who access that content.
If the proposed entity will have its own player contracts, assess customer-facing permissions through the UKGC operating-license route. For betting or bingo content, select the activity that matches that content.
Resolve this boundary before you price the application. If it moves later, you may need to change the entity, the fee assumptions and the split of customer responsibilities all at once.
What should the UK supplier dossier demonstrate?
Build the file around a named product and supply chain. A practical dossier should let a reviewer trace:
the licensed applicant to its development, supply and hosting contracts;
the proposed product to a system diagram and defined gambling functions;
each release to an identifiable version, approval and testing record;
the responsible managers to the decisions they control;
the commercial forecast to the proposed activity and revenue model.
Keep a separate list of unresolved questions. For example, “the upstream developer is still negotiating release control” is a live dependency. Keep it visible on that list, even when the policies folder is finished. Use the application readiness checklist for the company, funding and personal-submission work common to all applicants.
Technical readiness and continuing supply
Software you supply for use under UKGC operating permissions must support the applicable Remote gambling and software technical standards. Determine the testing requirements for each product and each change, including independent testing where it is required.
Useful evidence ties the test report to the software you supplied. Record the game or component, build, tested configuration, report reference, deployment and later changes. When an operator asks for a different integration, check whether the existing evidence still covers that configuration.
The UK technical compliance guide explains the control and release records. Keep them going after the grant: every later software change needs its own record.
Fees and the scope of MGL's work
Budget for the permission set you need, the technical work and the continuing obligations. Price software, hosting and consumer-operation fees as separate lines, instead of one generic “B2B license price.” The UK cost guide gives the dated fee anchors and a budget worksheet.
Agree with us which parts our engagement covers: the initial scope assessment, application documents, coordination of personal submissions, supplier follow-up and responses during the assessment. Give third-party testing and your internal engineering work named owners and separate budgets.
Questions suppliers should settle
A foreign license can be relevant background. On its own, it does not replace the UK permission that the proposed supply activity requires. For the earlier choice between jurisdictions, use the global B2B licensing overview.
Taking players changes the operating model. Assess the customer-facing permissions, contracts and controls before you accept the first player.
Send the product and function map and the proposed applicant and group roles. Add target operators and markets, current supply and hosting arrangements, and the intended release date. Flag anything still uncertain about player contracts or control of the gambling logic.
Send the product and function map, the proposed applicant and group roles, target operators and markets, and the intended release date.