Our agency has old code: can we sell it? License the internal tools and products you own to AI labs, keep the code and get paid each time.
Free to join. No public listing. A real estimate in minutes once Git is connected.
Agency CRM, retired 2024
120,340 lines. Six years of in-house client management for a 40-person agency, replaced by an off-the-shelf tool.
Yes, if the agency holds the rights. Internal tools and products built on your own account usually qualify, while client work usually belongs to the client unless the contract says otherwise. You sell a license and keep the code, so the same repo can earn again, and a typical repo earns about $1,000 to $1,500 per license.
Sometimes. It depends on who owns it, and that is decided by your contracts. Most agency agreements assign the work to the client once it is paid for. If yours do, that code is not yours to license, however long it has sat on your servers. Some contracts keep the IP with the agency and give the client a license instead. Code built under those terms can qualify.
The easier wins are usually closer to home. Agencies build a lot of software for themselves: the CRM that ran the studio for six years, the deploy scripts, the reporting dashboards, the starter kit every project began from, the product you built between client jobs and then shelved. That code is yours, and it is exactly what AI labs want, because it was written by working developers under real deadlines.
If you are not sure who owns a repo, check the contract before you put it forward. You only submit code you hold the rights to, and you decide repo by repo.
Look for the IP or ownership clause in the contract or statement of work. If it assigns all work product to the client on payment, the client owns it. If it says the agency keeps ownership and grants the client a license, the agency can license it too. Many agencies also keep the rights to their own reusable components, even inside client projects, through a carve-out for pre-existing or general-purpose code. Where a repo mixes both, only the parts you own count, and it is usually simpler to leave that repo out. When in doubt, ask the client or a lawyer before you submit.
Agency code is often worth more than owners expect, because agencies keep everything. A studio that has been running for ten years can have dozens of repos with long, busy histories. Value per license is set by tokens: source code pays $100 per million tokens and git history pays $40 per million. History usually carries most of the value, and agency repos tend to have a lot of it.
A typical repo earns about $1,000 to $1,500 per license. Ten typical repos come to about $10,000 to $15,000 if each is licensed once. Licenses are non-exclusive, so the same repos can be licensed again and you are paid each time. The specimen lot above, a retired agency CRM, shows the working for one deep repo.
Commercial success does not matter. A tool that only ever served your own team counts the same as a product with paying users. What matters is that the code is real and the agency holds the rights. For the full method, read how much is my code worth, and for why labs pay at all, read sell code for AI training.
| Depth | Looks like | Per repo, per license | 10 repos | Log scale, $100 to $10k |
|---|---|---|---|---|
| Light | Short history, small repo | $400 to $700 | $4,000 to $7,000 | |
| Typical | A real product, a few years of commits | $1,000 to $1,500 | $10,000 to $15,000 | |
| Deep | Long-lived, deep history, tests | $2,500 to $4,000 | $25,000 to $40,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. You grant a non-exclusive license and keep ownership. You can keep using, changing and shipping it.
Yes. Only submit code you hold the rights to. Client work usually belongs to the client unless your contract says otherwise.
Holding the rights to what you submit, and keeping third-party code and customer data out of the repos you select.
That is fine. Third-party code is excluded from what is licensed. Your own code and history are what count.
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.