Sell a GitHub repository you own by licensing it to AI labs. Connect it read-only, keep the repo and get paid each time it is licensed.
Free to join. No public listing. A real estimate in minutes once Git is connected.
Browser extension, shelved 2024
6,050 lines. A tab manager with 20,000 installs, shelved when its author changed jobs. Private repo, one author.
Yes, you can license a private GitHub repository you own to AI labs by connecting it read-only. You sell a license and keep the repo, so it can be paid for again each time it is licensed, and a typical repo earns about $1,000 to $1,500 per license.
Yes. If you own the code in a repository, you can license it, and GitHub is the easiest place for it to be. You connect your account with read-only access, pick the repos you want to include, and a real per-repo estimate appears within minutes. GitLab and Bitbucket work the same way.
Nothing about the repository changes. It stays in your account, under your name, with your history. A scrubbed review copy is made for grading, and that copy is what buyers see. You keep pushing to the repo, using it and shipping it as before.
Private repos are what labs want most. Public code is already easy for anyone to find, so a private repo with a long, real history is far more useful. Public repos you wrote yourself can still be included. Forks are a different matter: only the commits you wrote are yours, and repos that are mostly someone else’s work add little.
Nothing you would notice. Read-only access lets the program copy the repos you select with their history. It cannot push, delete, change settings or see repos you did not pick. You can revoke the access from your GitHub settings whenever you like. The copy is scrubbed of secrets and personal data, graded and taken to buyers in batches. Your repo keeps its name, visibility, stars and issues, and nobody outside sees it.
GitHub organizations work the same way as personal accounts. If the repos belong to a company organization, someone with authority signs for the company and an owner grants the read-only access. You can include some repos from an organization and leave others out.
Stars and followers do not set the price. Tokens do. Value per license is source tokens at $100 per million plus history tokens at $40 per million, and history usually carries most of the value. A repo with thousands of commits is worth more than a larger repo with a handful of squashed ones.
A typical repo earns about $1,000 to $1,500 per license. A small repo with a short history earns about $400 to $700, and a long-lived repo with tests about $2,500 to $4,000. Licenses are non-exclusive, so the same repo can be licensed again and you are paid each time. The specimen lot above, a shelved browser extension with one author, shows the working.
Do not squash or rewrite history before you connect. The real commit history is part of what you are paid for. Secrets that were committed years ago are found and stripped from the review copy for you. For the full method, read how much is my code worth. For why labs want private repos, read sell code for AI training.
| Depth | Looks like | Per repo, per license | Log scale, $100 to $10k |
|---|---|---|---|
| Light | Short history, small repo | $400 to $700 | |
| Typical | A real product, a few years of commits | $1,000 to $1,500 | |
| Deep | Long-lived, deep history, tests | $2,500 to $4,000 |
Illustrative, conservative · What you take home, per license · Verified 2026-10-10
$100/M
per million tokens
$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
Free to join. No public listing. A real estimate in minutes once Git is connected.
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.
No clean-up needed. Submit the repos as they are. Secrets and personal data are stripped from the review copy for you.
Say who you are. You get set up and sent everything you need. Once you connect Git, you see a real per-repo estimate.
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.
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.
Yes, internally and in your own products. The license does not change that.
That is fine. Third-party code is excluded from what is licensed. Your own code and history are what count.
No. There is no listing. Buyers see a scrubbed review copy.
Keys, tokens, credentials and personal data are removed from the review copy of both code and history and verified before a buyer sees anything. Your repository is untouched.
Request access. Connect Git. See a real per-repo estimate in minutes, then decide.
Free to join. Nothing upfront. You can withdraw a codebase at any time.