Catalogue No. 001By asset typeVerified 2026-10-10Licensing open

Can I sell game source code?

Sell game source code, Unity projects included, by licensing it to AI labs. Keep the game and its rights, and get paid each time it is licensed.

Free to join. No public listing. A real estimate in minutes once Git is connected.

Lot 007Studio ownedSpecimen

Unity mobile game, pulled 2023

31,480 lines and 40 hand-built puzzle levels. Pulled from both stores when ad revenue dried up. Studio owned.

Languages
C#, Unity
Lines of code
31,480
Commits
1,206
Source tokens
0.4M
History tokens
12.5M
Last commit
Aug 2023
Source 0.4M · 3.1%History 12.5M · 96.9%
Commits per quarterActivity stopped Q3 2023
Per license, USD0.4M × $100 + 12.5M × $40≈$540recurring
Illustrative lotNot a live listing
Quick answer

Yes, game code you own, from Unity and Unreal projects to custom engines, can be licensed to AI labs. You sell a license and keep the game and its code, so it can earn again, and a typical repo earns about $1,000 to $1,500 per license.

Applies to code you own Currency USD Verified 2026-10-10
§ 01Who this is for

Can I license a Unity game's source code?

Yes, if the studio or you hold the rights. AI labs license the code you wrote: C# scripts, gameplay systems, tools, shaders and build pipelines, with their history. Your game stays yours, and you can keep selling it or relaunch it later.

This suits games pulled from the stores, prototypes from game jams that grew, and titles that never shipped. What counts is code. Art, audio and level files are not what labs pay for, and you can leave them out.

Can I license a game that never shipped?

Yes. A game that never reached a store can be worth as much as one that did, because the value is in the code and its history. Long prototypes are often rich in exactly what labs want: systems rewritten several times, tools built along the way and bugs fixed late at night. If the game was made with a publisher, check the contract, since some publishers own the code they funded.

Engine code bought from an asset store or licensed from a vendor is not yours, so it is excluded from what is licensed. Your own gameplay code, tools and the history of how you built them are what count. Modding tools and level editors you wrote qualify too.

Qualifies
  • Unity C# projects, live or pulled
  • Unreal, Godot and custom engine code
  • Editor tools and build pipelines
  • Unreleased games and long-running prototypes
Stays out
  • Games a publisher owns under contract
  • Asset store packages and licensed plugins
  • Art, audio and other non-code assets
§ 02What it is worth

How much is game source code worth?

Value per license is source tokens at $100 per million plus history tokens at $40 per million. The specimen lot above, a Unity puzzle game pulled in 2023, shows the working. A typical repo earns about $1,000 to $1,500 per license, and a small game jam project about $400 to $700. Licenses are non-exclusive, so the same repo can be licensed again and you are paid each time.

Store sales and player numbers make no difference. For the method, read how much is my code worth. For why labs pay, read sell code for AI training.

Per-repo ballpark by depth, per license, USD
DepthLooks likePer repo, per licenseLog scale, $100 to $10k
LightShort history, small repo$400 to $700
TypicalA real product, a few years of commits$1,000 to $1,500
DeepLong-lived, deep history, tests$2,500 to $4,000

Illustrative, conservative · What you take home, per license · Verified 2026-10-10

Rate A · Source code

$100/M

per million tokens

Rate B · Git history

$40/M

per million tokens

Value per license = source tokens × $100/M + history tokens × $40/M

Rates can change on 30 days' notice, never retroactively · Paid within 15 days of the buyer paying

Illustrative, conservative · Last verified 2026-10-10

Find out what your repos earn.

Get a valuation

Free to join. No public listing. A real estimate in minutes once Git is connected.

§ 03The IP question

“But this is proprietary code.”

And it is yours, which is exactly what makes it licensable. You decide what is shared: only the repos you choose, only code you hold the rights to. Secrets, customer data and third-party code stay out. Within the repos you submit, secrets and personal data are stripped from the review copy before anything reaches a buyer.

  1. Fact 01You pick what is shared.
  2. Fact 02You keep full ownership.
  3. Fact 03Secrets are stripped for you.
§ 04What to do next

What do I do next?

No clean-up needed. Submit the repos as they are. Secrets and personal data are stripped from the review copy for you.

  1. Step one

    Request access

    Say who you are. You get set up and sent everything you need. Once you connect Git, you see a real per-repo estimate.

    Time A few minutes
  2. Step two

    Sign and connect

    Read the agreement and sign once. Give read-only access to GitHub, GitLab or Bitbucket and pick only the repos you want to license. Submit them as they are.

    Access Read-only
  3. Step three

    Get paid, repeatedly

    Your code is scrubbed and graded on the review copy, then taken to buyers in batches. Each time a license closes and the buyer pays, you are paid within 15 days.

    Payout Within 15 days
§ 05Questions

What else do owners ask?

Q.04Do I need to own the IP?

Yes. Only submit code you hold the rights to. Client work usually belongs to the client unless your contract says otherwise.

Q.11Do I need the repo to be working?

No. Shelved, unfinished and abandoned code qualifies if it is real and yours.

Q.12What if the code uses open source libraries?

That is fine. Third-party code is excluded from what is licensed. Your own code and history are what count.

§ 07  ClosingCatalogue No. 001Licensing open

What is your code worth?

Request access. Connect Git. See a real per-repo estimate in minutes, then decide.

Get a valuation

Free to join. Nothing upfront. You can withdraw a codebase at any time.

Get a valuation