Guide
Selling a game studio's data
Updated October 2026
Games are some of the most complex software ever built. A studio's codebase, task history and design documents show how large teams turn ideas into working systems, which makes them valuable for training AI that writes and fixes code.
What has value
- Source code and full version history (GitHub, GitLab, Perforce)
- Jira or similar task history, especially when tickets link to code changes
- Design documents, specs and technical documentation
- Art and assets the studio owns outright
- Team communication on Slack, Discord or Teams
- Builds, tools and pipelines
Why linked history matters
The most useful archives let you follow a problem from a bug report to the ticket, the code change and the fix. That chain is what AI developers use to build realistic coding tasks.
Unreleased and cancelled games count too
A game does not need to have shipped. Years of development on a cancelled title can still be a large, valuable archive, as long as the studio or its estate owns the rights.
What is excluded
Licensed engine source and third-party assets you do not have the right to share, middleware under restrictive licences, personal data and HR records.
FAQ
Can a codebase be sold on its own?
Often yes. Large codebases with long histories can be licensed without the rest of the company's records.
What about engine code like Unreal or Unity?
Engine source and other licensed third-party code are excluded. Your own game code, tools and documentation can usually be included.
Our studio has shut down. Is it too late?
Not if the repositories, tickets and documents still exist. Export them as soon as possible.
Find out what your company data is worth.
Get my free valuation