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

Can I sell my software's source code?

Sell software source code you own by licensing it to AI labs. Desktop, server and internal software qualify. Keep it and get paid each time.

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

Lot 019Company ownedSpecimen

Booking engine, retired 2022

74,300 lines. The booking engine behind a travel agency site for eight years, retired in a platform migration.

Languages
Ruby on Rails
Lines of code
74,300
Commits
4,860
Source tokens
0.9M
History tokens
29.0M
Last commit
Jun 2022
Source 0.9M · 3.0%History 29.0M · 97.0%
Commits per quarterActivity stopped Q2 2022
Per license, USD0.9M × $100 + 29.0M × $40≈$1,250recurring
Illustrative lotNot a live listing
Quick answer

Yes, desktop, server and internal software you own can be licensed to AI labs, on any stack and in any state. You sell a license and keep the software 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 software my company built?

Yes, if the company holds the rights, and the company signs. Most businesses that build software accumulate far more of it than they sell: internal systems, retired products, utilities, integrations and old versions of current products. All of it can be licensed to AI labs.

You keep the software and full use of it. Licensing a copy for training does not stop you selling the product, running it or rewriting it. The code stays private, and only a scrubbed review copy reaches buyers.

What about software we still sell?

It qualifies too. Licenses are non-exclusive and cover a copy used for training, so you keep selling, supporting and updating the product as before. Many companies start with retired versions and internal systems, then add current products once they are comfortable with the terms. You choose repo by repo, and you can withdraw a codebase at any time.

Large software estates tend to hold many repos: the main product, plugins, installers, test harnesses and internal tools. Each one is valued on its own tokens. A single product line can add up to dozens of repos, and each can be licensed more than once.

Qualifies
  • Desktop and server software
  • Internal systems and business tools
  • Retired products and old major versions
  • Libraries, SDKs and command line tools
Stays out
  • Software licensed in from a vendor
  • Code a client owns under contract
  • Customer data and production databases
§ 02What it is worth

How much is software 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 booking engine retired after eight years, shows the working. A typical repo earns about $1,000 to $1,500 per license, and a deep, long-lived one about $2,500 to $4,000. Licenses are non-exclusive, so the same repo can be licensed again and you are paid each time.

Sales figures and user counts 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.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.11Do I need the repo to be working?

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

§ 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