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
How much is my code worth?
How much is my code worth? A typical repo earns $1,000 to $1,500 per license from AI labs. Sell a license, keep the code, earn again.
Free to join. No public listing. A real estimate in minutes once Git is connected.
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
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 Quick answer
A typical repo earns about $1,000 to $1,500 per license. Value per license is source tokens × $100 per million plus history tokens × $40 per million. You sell a non-exclusive license and keep the code, so that amount can recur.
Applies to code you own Currency USD Verified 2026-10-10
Get a real per-repo estimate.
Get a valuation
Free to join. No public listing. A real estimate in minutes once Git is connected.
How is source code value calculated?
Code is valued by the token. A token is a short chunk of text, roughly three or four characters of code. AI labs pay $100 per million tokens of source code and $40 per million tokens of git history. Add the two together and you have the value of one license for that repo.
History is counted separately because it is a different kind of signal. The final source shows what the code is. The history shows how it got there: every change, fix and rewrite. A repo with a few years of commits usually holds many times more history tokens than source tokens, which is why history carries most of the value.
Third-party code is left out of the count. Vendored libraries, generated files and dependencies belong to someone else, so they are excluded from what is licensed. Only your own code and the history of how you changed it are counted.
The ballpark above uses per-repo ranges by depth. Your real figure comes from counting the tokens in your actual repos, and appears in minutes once you connect Git.
Counting tokens is mechanical, so there is no haggling and no pitch. The same repo gets the same count whoever owns it. What varies is how much code and history it holds, and how much buyers want that kind of code.
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
How much is a repo worth?
Most repos fall into one of three bands. These are conservative ballparks of what an owner takes home per license. A light repo is small with a short history. A typical repo is a real product with a few years of commits. A deep repo is long-lived, with a long history and tests.
| Depth | Looks like | Per repo, per license | 15 repos | Log scale, $100 to $10k |
|---|---|---|---|---|
| Light | Short history, small repo | $400 to $700 | $6,000 to $10,500 | |
| Typical | A real product, a few years of commits | $1,000 to $1,500 | $15,000 to $22,500 | |
| Deep | Long-lived, deep history, tests | $2,500 to $4,000 | $37,500 to $60,000 |
Illustrative, conservative · What you take home, per license · Verified 2026-10-10
Fifteen typical repos come to about $15,000 to $22,500 if each is licensed once. Licenses are non-exclusive, so that is not a ceiling.
Why are these ballparks conservative?
They are set below what many repos earn, so you are not disappointed by your real estimate. They describe what you take home per license, after the program’s share, with no fees taken from your part. A repo can fall outside its band in either direction. A long-lived monorepo can earn far more than the deep band. A tiny repo with a dozen commits can earn less than the light one.
What makes source code more valuable?
Four things move the number. Size helps, but depth and realism matter more, and none of them depend on whether the product made money.
- A
Source tokens
How much code there is. More real code means more tokens at the source rate.
Counted per repo - B
History depth and realism
Years of genuine commits, fixes and refactors. Squashed or generated history is worth far less.
Most of the value - C
Tests
Tests show what the code is meant to do and how it was checked. Labs use them to grade models.
Raises the grade - D
Buyer demand
Some languages and domains are scarcer than others. Demand decides how often a repo is licensed.
Sets how often
Some things make no difference at all: revenue, users, downloads, stars, design and whether the code still builds. A shelved product that never made money is valued exactly like one that did, if the code and history are the same size and quality.
How much have other owners earned?
Owners in the licensing program earned $6M in the last 60 days, across 11,069 licensed repos. One company alone licensed a few hundred repos in the same period. In both cases most of the value came from history.
These are program totals, published by the program and shown here as illustrative and conservative. They show that owners are being paid at scale, across hundreds of companies and thousands of repos. They do not predict what any one repo will earn. That depends on its tokens, its history and what buyers want when it is graded.
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
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.
Can the same code be licensed more than once?
Yes. Every license is non-exclusive, so a lab that licenses your repo does not stop another from licensing it too. Each time a license closes and the buyer pays, you are paid within 15 days, with no fee taken from your share.
How often a repo is licensed depends on demand, so no one can promise a number of licenses. What it means in practice is that the ballpark above is a per-license figure, and the same code can earn it again. You keep ownership throughout, and you can withdraw a codebase whenever you like.
When do I see my real figure?
Within minutes of connecting Git. Request access, sign the agreement and give read-only access to the repos you want valued. The token counts and a per-repo estimate appear straight away, with no obligation to license anything. If the figure is not worth it to you, withdraw the repos and that is the end of it.
For how the process works step by step, read how to sell source code. For why labs pay at all, read sell code for AI training.
What else do owners ask?
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.
Q.07When and how do I get paid?
Within 15 days each time a license closes and the buyer pays. No fees are taken from your share.
§ 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.