Sell your private code history to AI labs.
Commits, pull requests and code review from working teams are some of the most requested training data. Allied prices your repositories, scans out secrets and author details, and brokers the license.
What labs look for in code repository data
Commits and pull requests
Changes with their messages, diffs and linked issues.
Review threads
Reviewer comments and the revisions that followed.
Issues and CI results
Bug reports, fixes and test outcomes tied to specific changes.
What is removed before delivery
Keys, tokens and credentials (scanned and stripped), author names and emails, internal hostnames, and customer names in code or comments. You can exclude any repository.
You approve an anonymized sample before anything reaches the lab, and anything you exclude stays out.
What drives the price
- Number, size and age of repositories
- Volume of pull requests and review comments
- Languages and frameworks
- Test coverage and CI history
Most offers combine several systems. Estimate the value of all of yours
Code repositories questions
Does licensing our code expose our IP?
You choose which repositories are in scope, and the license limits use to model training and evaluation with no right to redistribute. Many sellers keep core proprietary systems out and license the rest.
How do you handle secrets in the history?
Every commit is scanned for keys, tokens and credentials, which are removed before delivery. We will tell you what the scan finds so you can rotate it.
Do archived repositories count?
Yes. Older codebases with long histories are often worth more than new ones.
See what your code repository history is worth.
The estimate takes two minutes and asks for no contact details. The offer request form takes about three.