Skip to content
Company Data Advisors

Blog

Can a game studio license its code to AI data buyers?

· Company Data Advisors

Mercor and Handshake now ask game studios for code, development records and gameplay. What each wants, and the engine and platform terms to check first.

Often yes, for the code and records a studio owns outright. As of November 16, 2026, two of the 17 programs in our buyer index ask game studios for records by name on their own pages: Mercor, through a dedicated Game Studio listing, and Handshake, through a Gaming section of its data partnerships page. Both want game source code and development records; Mercor also wants gameplay recorded with player inputs. The harder question is what in a game repository is yours to license. Engine source, console SDKs, middleware, bought assets and licensed characters usually belong to someone else, and their terms decide what has to come out before a buyer sees anything.

This is a reading of buyers' public pages and public license terms, not legal advice. Have counsel review your publisher, platform and middleware agreements before you share anything with a buyer, including a sample.

What do AI data buyers want from game studios?

AI data buyers want the record of a game being made: code with its commit history, the tickets and chat around it, design documents, and gameplay recorded with the inputs that produced it. Mercor's Game Studio listing says "Game and engine code, gameplay recordings with keyboard and mouse input, and footage of the studio's own games are all in demand." Handshake's Gaming answers say "The focus is game source code and development data, potentially including supporting graphics, audio, and design assets."

Mercor Handshake
Records named Company chat, email and documents; game and engine code; gameplay recordings and input logs; analytics and playtest data Game source code and development data; possibly graphics, audio and design assets
Adds value Code with commit history; gameplay synced with keyboard, mouse or controller input; full-length video of your own games; player analytics, playtest telemetry and support tickets; design documents and 3D assets Source code "complete enough to run the game"
Which games At least one shipped title that earns revenue Games "at all stages," including released titles, games in development and canceled projects
Size 10 to 500 employees; a team of 10+ "not mainly short-term contractors" Not stated for games; its general FAQ says companies with 20+ employees and 3+ years of history are "typically more likely to be a fit"
Kinds of company Indie and mid-size studios, mobile and browser game makers, esports organizations, QA and playtesting firms Game studios
Tools named Unity, Unreal Engine, Godot, Perforce, GitHub, Jira, Slack, Discord Not stated
Not a fit Footage of other studios' games; asset-store or template code; crypto and play-to-earn token projects Not stated

Sources: Mercor's Game Studio listing and the Gaming answers on Handshake's data partnerships page, both read on 2026-11-16. Each buyer's page in our index links to its program.

Mercor's listing gives a range for what a studio earns: Mercor says $100k to $1M, adding that "larger studios with full company data have earned more."

In a LinkedIn ad to studios running in November 2026, Handshake says a studio's "game code and development records" could be worth $100K to $4M (ad).

Two differences matter. Handshake will look at games that never shipped: its Gaming answers say "canceled and in-development projects may be a fit." Mercor requires a shipped title that earns revenue. And Mercor's ads put weight on code a studio wrote itself, with one headline reading "An engine your team built from scratch is rare data" (ad). None of the other 15 programs in our index names game records on its own pages, though most take the Slack, email and ticket records any company holds.

Why do AI labs want game code and gameplay?

Labs want game records for two different reasons, and they lead to different buyers.

  • Code for coding agents. A game repository is a large, long-lived codebase in C++ or C#, with performance work, tools and build systems, written by a team over years. In our view, that is the kind of record coding agents are trained and tested on. Our post on software companies covers why buyers prefer human-written code with its history, and flight simulators for office work explains how such records become practice environments.
  • Gameplay for world models. A world model is an AI system that learns how an environment responds to actions, so it can predict or generate what happens next. Gameplay recorded with the button presses behind it is training data for these models. Microsoft trained its Muse model on gameplay and controller actions from Ninja Theory's Bleeding Edge (February 2025). General Intuition was spun out of the clip-sharing app Medal in October 2025 to train agents on game video. WIRED reported in September 2026 that Worldmodeldata says it has licensed "almost 1 million hours" of data from game studios, and Origin Lab raised a seed round in May 2026 for a platform connecting game publishers with AI labs.

Our view: a studio holds both kinds of record, and the two can be licensed separately. The code and its history fit the programs in our index. Gameplay with input logs fits Mercor's listing and a separate group of footage buyers, most of which are outside our index. Know which you are offering before you compare prices.

What in a game repository isn't yours to license?

A game repository usually mixes the studio's own code with code and content it licenses from others, and each license sets its own limits. Mercor's listing asks the studio "Do you own the game and engine code outright?" and rules out asset-store and template code. Sort the repository by where each part came from.

Unreal Engine changed its terms on October 29, 2026

Epic removed two restrictions from the Unreal Engine EULA on October 29, 2026: the ban on using Unreal Engine, "including its source code," as a training input to generative AI, and the ban on training AI with MetaHuman characters and animation curves. Epic's announcement says the change "doesn't grant Epic any rights to your content or code." New users are prompted to accept the new EULA automatically, and existing users must accept it to get the change. Studios on a custom license with Epic should check their own agreement, and Fortnite islands built in UEFN fall under Fortnite's developer terms instead.

Two limits remain. The Unreal Engine EULA allows Engine Code, including your modifications, to be distributed in source form "to a third party who is separately licensed by us to use the same version of the Engine Code." In our reading, that is the only route the EULA gives for engine source outside a shipped product, so a studio whose repository includes a modified copy of the engine would need the buyer to hold its own Unreal license before that part goes anywhere. And Epic says the change does nothing for Fab assets: sellers can still mark their content "NoAI," and the Fab terms bar using NoAI content "in datasets utilized by Generative AI Programs."

Guides written before October 29 may still say Unreal forbids AI training. That was true until that date, and it remains true for existing users who haven't accepted the new EULA.

Unity's terms are stricter, in our reading

Unity's Editor Source Code Terms (updated June 30, 2026) say a customer "shall not, at any time, directly or indirectly, share, distribute, disclose, or otherwise make available the Unity Source Code" to any third party without Unity's written consent. They also bar using it for any purpose related to training "any competing game engine, SDK, API, AI model," and bar pasting it into any AI agent or coding assistant. Unity's terms of service bar using any Unity offering or data derived from it to train AI models, "including but not limited to training AI models on data, assets, or outputs derived from Offerings or generated via the use of Offerings, regardless of method or purpose, without prior authorization." Assets bought on the Unity Asset Store can't be used to train AI without consent from the asset's provider or Unity.

Our view: how far the terms-of-service clause reaches into a studio's own code and gameplay made with Unity is not clear from its text. A Unity studio should ask counsel, and possibly Unity, before licensing anything built with the engine. Godot is published under the MIT license, which is far more permissive, but check the license of every plugin.

Console SDKs, middleware and licensed content

  • Console platform SDKs. Nintendo's developer portal says developers "accept the Non-Disclosure Agreement and Terms of Service to gain access to platform SDKs" (Nintendo). Microsoft's console development kit is "only available under confidential license within an NDA Xbox program" (GitHub). Sony's publisher agreement isn't public, but an older version filed with the SEC bars disclosing Sony's materials to third parties without Sony's written consent (SEC filing). Platform headers, libraries and console-specific folders come out before anything leaves the studio.
  • Middleware. In our experience, audio, physics and other middleware licenses limit redistribution to the shipped game. The FMOD EULA, for example, says "FMOD SDK files are not to be distributed" apart from its run-time libraries. Check each middleware license in the repository.
  • Licensed characters, music and brands. Our view: a license to use someone else's intellectual property in a game rarely lets you pass it to a third party, so treat licensed content as excluded unless the licensor agrees in writing.
  • Publisher-funded games. Who owns the code depends on the development agreement. A publisher may own the code outright, hold a license to it, or have approval rights. Read the agreement for each title before you list it.
  • Contractor and outsourced work. Whether code, art and audio from contractors belong to the studio depends on their contracts; ask counsel. Our software company guide covers what U.S. copyright law says about contractor code.

What about players, testers and performers?

Player data needs its own decision, because Mercor counts player analytics, playtest telemetry and support tickets as adding value, and all of them hold personal information. Mercor says it "signs an NDA and runs the export, removing or protecting personal information." Three groups need a closer look:

  • Children. If a game is directed to children under 13, the FTC's amended COPPA Rule requires a separate parent's consent before their personal information is disclosed to third parties, unless the disclosure is integral to the game. In its April 2025 notice, the FTC said disclosures "to train or otherwise develop artificial intelligence technologies, are not integral to the website or online service." In our view, a children's game should leave player data out entirely.
  • Players elsewhere. Telemetry, chat logs and support tickets from EU or California players may fall under the GDPR or California's privacy law, depending on the studio; ask counsel. Our guide to records that include employee and customer data covers what de-identification does and doesn't solve.
  • Performers. Voice and motion-capture recordings are performances. SAG-AFTRA's 2025 Interactive Media Agreement added "consent and disclosure requirements for A.I. digital replica use." Our view: leave performance recordings out of a license unless counsel has reviewed the performers' contracts.

Can a closed or canceled game be licensed?

Handshake says yes for canceled projects: "Yes, canceled and in-development projects may be a fit. Our team will work with you to understand what code and materials are available in order to better assess the opportunity." Mercor's listing requires a shipped title that earns revenue. In our understanding, for a studio that has closed, the person who signs is whoever now controls the company's assets, which in a bankruptcy may be a trustee rather than the founders; check with counsel. Our guide to licensing when a company is closing covers who has authority and what to do before the systems are shut down.

How should a studio read an unsolicited offer for its source code?

Treat an email offering to buy your source code as the start of a check, not as an offer. Before anything leaves the studio, you should know:

  1. Who the buyer is. If the sender is an intermediary, ask who will receive the code and whether you can approve that party by name.
  2. What the sample is. Mercor and Handshake both describe scoping the materials with the studio first, and Mercor signs an NDA before it runs the export. Don't send a full repository or a playable build before an NDA and written terms.
  3. What the license covers. Exclusivity, which uses are allowed, whether the buyer can relicense, and what happens to the code when the term ends. Our comparison of license terms across buyers sets these side by side.
  4. Where the number comes from. A figure in a cold email is not a price. Compare it with what buyers publish for studios: the ranges above are each buyer's own claim, not a quote for your game.

Our six checks for whether an AI data buyer is legitimate apply here as well.

Where we come in

A studio that decides to license usually holds several kinds of record (code, development history, gameplay, chat and tickets) that fit different buyers, and a repository with parts it can't license at all. We track the published criteria and terms of every major program, have direct contacts at the major data buyers and at AI labs, and go through the ownership, exclusivity and onward-licensing terms with you before you choose. Nothing about your studio is shared until you approve a specific, named buyer. Participating buyers may pay us referral fees, and we tell you which before any introduction. Studios pay us nothing, and you can apply to any buyer directly.

What to do next

Before you answer any buyer, put four lists in front of your technical lead and counsel:

  1. Titles and repositories: each game, whether it shipped, which engine and version it uses, and whether the repository holds a modified copy of the engine.
  2. Third-party code and content: console SDKs, middleware, asset-store and Fab purchases, licensed characters and music, and the license that covers each.
  3. Agreements: each publisher, co-development and contractor agreement, and what it says about who owns the code and assets.
  4. People's data: player telemetry, chat and support records, whether any game is directed to children, and any voice or motion-capture recordings.

If you use Unreal, decide whether to accept the October 29 EULA, and check that Fab assets marked NoAI are out of anything you would share. Then compare the programs on the records you can actually license, or check where you fit.

Programs in this post

See which buyers fit your company

Eight quick questions against every program in our buyer index. Participating buyers may pay us referral fees.