Catalogue No. 001Source code & git historyNon-exclusive, recurringLicensing open

Your old code is worth something.Find out how much.

Turn idle code into recurring revenue

AI labs pay to license real source code and the git history behind it. Licenses are non-exclusive, so you are paid every time your code is licensed. You keep ownership. Nothing upfront.

Get a valuation

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

Qualifies for licensing
  • Shelved products
  • Dead startups
  • Internal tools
  • R&D and prototypes
  • Side projects
  • Legacy systems
Lot 014Company ownedSpecimen

Invoicing platform, shelved 2024

48,210 lines and five years of real commits from a B2B product that never turned a profit. Tested and company owned.

Languages
TypeScript, Go
Lines of code
48,210
Commits
3,912
Source tokens
0.6M
History tokens
23.5M
Last commit
Mar 2024
Source 0.6M · 2.5%History 23.5M · 97.5%
Commits per quarterActivity stopped Q2 2024
Per license, USD0.6M × $100 + 23.5M × $40≈$1,000recurring
Illustrative lotNot a live listing
Earned, last 60 days
$6M
Repos licensed
11,069
Source code
$100/M
Git history
$40/M

Program figures · Illustrative, conservative · Verified 2026-10-10

Per license · illustrative
  • Lot 003Agency CRM · PHP, MySQL · 71.5M tokens≈ $2,950 per license
  • Lot 007Unity mobile game · C#, Unity · 12.9M tokens≈ $540 per license
  • Lot 011Browser extension · TypeScript · 10.1M tokens≈ $410 per license
  • Lot 014Invoicing platform · TypeScript, Go · 24.1M tokens≈ $1,000 per license
  • Lot 019Booking engine · Ruby on Rails · 29.9M tokens≈ $1,250 per license
  • Lot 022iOS fitness app · Swift · 30.8M tokens≈ $1,250 per license
  • Lot 026Android delivery app · Kotlin · 14.5M tokens≈ $610 per license
  • Lot 031Fintech startup · Kotlin, React · 88.6M tokens≈ $3,700 per license
  • Lot 035Discord bot · TypeScript · 10.6M tokens≈ $430 per license
Quick answer

Yes, you can sell your code and keep it. You sell a license, you keep the code, and you get paid again when it is licensed again. The buyers are AI labs that train coding models on real source and git history. A typical repo earns $1,000 to $1,500 per license.

Applies to code you own Currency USD Verified 2026-10-10
§ 01Demand

Why AI labs pay

  1. Reason 01

    Scarce input

    Real production code is the one input labs cannot generate synthetically. They pay for the real thing.

  2. Reason 02

    Rising demand

    Labs are licensing real-world codebases to train and evaluate coding models, and the appetite is growing.

  3. Reason 03

    History counts

    Commits, fixes and the way a codebase matured carry signal. You are paid for git history as well as the final source.

    Source 21%History 79% of licensed tokens
  • Reason 04

    Commercial success is irrelevant

    What matters is that the code is real and that you hold the rights.

    Shelved products, dead startups, internal tools, R&D and side projects all qualify.
§ 02Rates

The rates

Value per license is source tokens at $100 per million plus history tokens at $40 per million. Lot 014: 0.6M × $100 + 23.5M × $40 ≈ $1,000.

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

§ 03Proof

What owners earned

Across the programLast 60 days

$6M earned

Owners in the licensing program earned $6M in the last 60 days, across 11,069 licensed repos.

Earned
$6,000,000
Repos
11,069 licensed
Tokens
57.1B
Source 11.8B · 20.7%History 45.31B · 79.3%
One companyLast 60 days

$300K earned

One company licensed 326 repos through the program and earned $300,000 in the same 60 days. Most of its value came from history.

Earned
$300,000
Repos
326 licensed
Tokens
2.2B
Source 300.9M · 13.7%History 1.9B · 86.3%
Last verified 2026-10-10

Published program figures, shown as illustrative, conservative. What your repos earn depends on analysis of the code and on buyer demand.

Find out what your repos earn.

Get a valuation

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

§ 04The opportunity

Idle code, earning

  1. Idle code

    Found money

    Code you stopped working on can earn again. It is already written, with nothing to build, fix or clean up.

    Upfront cost $0
  2. Non-exclusive

    Paid repeatedly

    Licenses are non-exclusive. Each one that closes pays you, and the same repo can be licensed again.

    Payout Within 15 days
  3. Read-only

    You stay in control

    Pick the repos. Withdraw any time. Access is read-only, and your repository is never touched.

    Commitment None
§ 05The 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.
§ 06Ballpark

What could your repos earn?

Once you request access and connect your repos, you get a real per-repo estimate straight away, with no obligation to license anything.

15 repos
Typical repo depth

Totals across all the repos above. $100 per M source, $40 per M history.

Your lotBallparkDraft
Per license, USD

≈ $1,000 to $1,500 per repo, recurring, paid on every re-license.

15 repos × $1,000 to $1,500 · Typical depth

Ballpark per license: $15,000 to $22,500.

Illustrative only. A conservative per-repo ballpark by codebase depth. What you take home. Not a quote. Your real per-repo estimate appears when you connect Git.

Get a valuation
§ 07Procedure

How it works

  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
§ 09Questions

Questions owners ask

Q.01Do I keep ownership of my code?

Yes. You grant a non-exclusive license and keep ownership. You can keep using, changing and shipping it.

Q.02Can I continue using the code?

Yes, internally and in your own products. The license does not change that.

Q.03Is the license exclusive?

No. The same repo can be licensed more than once, and you are paid each time. How often depends on demand.

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.05What contributes to the value?

The token count of your source and of your git history, how deep and real that history is, tests, and buyer demand. History carries most of the value.

Q.06How long does the process take?

You see a real per-repo estimate within minutes of connecting Git. Licenses close in batches. You are paid within 15 days of the buyer paying.

§ 10  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