Do you hold the rights to license your own game?
The question that stops more of these deals than price does. A studio can own its game completely and still not hold every right needed to license it for this use — because an engine licence, a music track or an old publishing agreement says something about server-side use that nobody has read in years. This guide is how to find out before a lab asks.
Work through six sources of rights you do not fully own: the engine licence, middleware and asset-store content, licensed music and audio, outsourced art and code, any publishing agreement, and employment or contractor terms. Most are workable, and the usual fixes are narrow — strip the audio, swap one middleware component, confirm one clause with a publisher. The point is to find the one that is not workable before a lab is waiting on a signature, because that is what turns a four-week deal into a four-month one.
Why this comes up at all
Nobody wrote "AI training environment" into a contract signed in 2015. The agreements under a shipped game describe making it, selling it and running it for players. A lab running the same build headless on its own hardware is a use those documents do not anticipate, which means the answer is rarely a clean yes or no — it is a reading.
That is survivable. What is not survivable is discovering it late. A studio that raises a rights question in week one looks organised; the same question in week seven, with a lab holding a draft, looks like the deal is unravelling.
1. The engine licence
Start here, because it is the most likely to matter and the easiest to check. Engine terms are written around distributing a game to end users. Running many headless instances on servers for a third party, possibly with a plugin that exposes internal state, is a different shape of use.
- What the licence says about server-side, headless or non-player use.
- Whether a modified build for a third party changes anything.
- Whether revenue from such a use counts toward royalties or revenue thresholds.
- Whether your seat or subscription tier covers what you are about to do.
A black-box environment and an engine integration can land differently here, because the second involves changing the project. Worth asking about both, even if you expect to start with one.
2. Middleware and asset-store content
Physics, audio, navigation, networking, speedtrees, crowd systems — each has its own licence, and asset-store terms in particular are often written for a single shipped product. You are looking for anything that limits use to a released game, caps installations, or requires attribution in a context an environment build will not have.
The usual fix is narrow: one component swapped or disabled in the environment build. Agents do not need a crowd system.
3. Music and audio
The most common blocker, and the one with the simplest answer. Licensed music is granted for a defined use, often a defined territory and term, and AI training is in none of those grants. Voice recordings can carry performer terms as well.
Because most environments run headless or on structured game state, audio is usually dead weight. Stripping it from the environment build removes the question entirely and costs nothing the lab wanted.
4. Outsourced art and code
Work-for-hire contracts generally transfer rights, but older or informal ones sometimes grant a licence instead, and the licence can be limited to the shipped game. The same goes for contractor-written code and for anything contributed by a partner studio.
You are not auditing the whole project. You are looking for the handful of agreements that were not standard, which the people who signed them usually remember.
5. The publishing agreement
If a publisher funded or distributed the game, read the exploitation clause before anything else. It is common for a studio to keep the IP while the publisher holds exclusive commercial rights for a period or in a territory. Whether licensing a training environment falls inside "commercial exploitation" is a genuine question, and the honest answer is often that the contract does not say.
When it is ambiguous, raising it with the publisher early is better than being right late. A publisher with no appetite for the deal is information; a publisher who wants a share is a negotiation; a publisher who finds out from the lab is a problem.
6. Employment and contributor terms
Mostly a formality, occasionally not. Jurisdictions differ on what an employee automatically assigns, and open-source components in the build carry obligations that a headless server deployment may change. Worth one pass, not a project.
What to do with what you find
Write down, per title, what you hold cleanly and what has a question mark. That document is worth more than it looks: it tells you which title to take to market first, and it is the thing that lets you answer a lab's legal team in a day instead of a month.
Then check the engine and publishing questions with your lawyer before the first call, not after the term sheet. The rest can usually be resolved while the technical work runs.
Not sure which title is cleanest? A fit check looks at the technical side under NDA, and we will tell you plainly where the rights questions usually sit.
Request a fit checkFrequently asked questions
Do I need Unity or Unreal to approve licensing my game for AI training?
Check the engine agreement rather than assume. Engine licences are written around shipping a game to players, and server-side or headless use for a third party is not always what they anticipated. Most situations are workable, but it is a question to settle before you sign, not after.
Does licensed music in my game block an AI training licence?
It can complicate it. Music is usually licensed for a defined use and territory, and AI training is not a use anyone wrote into a 2015 contract. The practical answer is often to strip or replace audio in the environment build, since agents rarely need it.
Who holds the rights if a publisher funded the game?
It depends on the publishing agreement, and the answer is frequently split: the studio keeps the IP while the publisher holds exclusive commercial exploitation rights for some period. AI training is a new use that old agreements rarely name, so it has to be read carefully and often discussed with the publisher.
What about art or code that was outsourced?
Work-for-hire agreements usually transfer rights, but not always completely, and asset-store content comes with its own licence terms. Both are worth checking for anything that limits use to a shipped game.