Updated November 2026
pre.dev review: what it pays for your private code
pre.dev is a fit if you are a developer, agency or company with private code repositories, and it does not cover email, CRM or other company records, because it licenses code only. Owners with those records should take our quiz. pre.dev headlines $6,000 per repo, which is what its sliders show at 20M source tokens and 100M tokens of git history, while its four example repos run from $740 to $4,180.1,2,3,4
Our score
Not ranked
Not in our seller ranking
pre.dev's public terms do not cover seller payouts or licensing code to labs.5
Key facts
pre.dev in its own words and others'
| Fact | Value and source |
|---|---|
| pre.dev: what it licenses | Private Git repositories the owner picks after connecting a Git account, for AI labs to train coding models. Code only |
| pre.dev: rate card | $100 per million tokens of source code and $40 per million tokens of git history |
| pre.dev: deal terms | "Non-exclusive by default. You keep the code, keep shipping it, and it can pay more than once." One agreement, signed once |
| pre.dev: cleaning the code | Authors become pseudonyms, the company name is rewritten, three secret scanners run over every file version, git history is rewritten to remove secrets and personal data, and delivery is through expiring signed links |
| pre.dev: company | PREDEV CORP, 2140 S Dupont Hwy, Camden, DE 19934. Delaware law |
| pre.dev: scale claim | 10,000+ private codebases, rounded down, as of September 27, 2026. No buyer is named |
Is this for my business?
pre.dev suits anyone holding private repositories
pre.dev takes individuals such as a fractional CTO or solo developer, and agencies or companies with client or company codebases. The signup lists no headcount, years or region requirement, so a one-person shop can apply.2
pre.dev checks that every repo is not public, not a fork, not archived and not a published package, and you connect a Git account and pick which repos to offer. Companies that want to license code along with Slack, tickets and business apps have other routes: Collinear licenses both repositories and business app history.6,1,7
What does it pay?
pre.dev's $6,000 headline is a default calculator setting
pre.dev's rate card is $100 per million tokens of source code and $40 per million tokens of git history, and a token is a small chunk of text. The $6,000 headline is what the page shows at its starting settings of 20M source tokens and 100M tokens of history: 20 x $100 + 100 x $40 = $2,000 + $4,000 = $6,000.8,3
pre.dev's four sample repos are valued at $4,180, $2,640, $1,905 and $740, all below that headline, and the page labels them as example grades. Yours come from your own repos once they are analyzed, and the rates apply to size, so a smaller repo earns less and a larger one earns more at the same rates.4,8
pre.dev says it pays Net 15 after funds land, on a license it calls non-exclusive by default, where you keep the code and it can pay more than once. One agreement, signed once, covers the deals after it.3,9
What happens to my code?
What pre.dev strips out, and what labs receive
pre.dev says authors become pseudonyms, the company name is rewritten, three secret scanners run over every file version, git history is rewritten to remove secrets and personal data, and delivery uses expiring signed links.10
pre.dev's own pages differ on what labs get. The home page FAQ says labs get tasks, not repository access, while the Labs page offers those tasks or the codebases themselves with full git history, so ask which applies to your repos.11,12
What is missing?
We found no public pre.dev seller agreement
pre.dev's public terms say nothing about seller payouts or licensing code to labs, and the pages we read state no retention period and no seller fees. Read the agreement you are asked to sign before you connect a repo. pre.dev says it holds 10,000+ private codebases, rounded down, as of September 27, 2026, and names no buyer.5,13,14
Who is behind it?
Who runs pre.dev
Check first
How to check pre.dev, or any buyer
The same checks for every company we profile. We state facts; you decide.
- 1.Find the company behind the ad: a legal name, a registered address and named people.
- 2.Ask for a written offer and a sample agreement before you send any data.
- 3.Ask who removes personal data, by what method, and approve it before anything is exported.
- 4.Ask which AI labs will receive the data, and whether you will be told.
- 5.Ask how they are paid: by you, by the buyer, or from a share of your deal.
- 6.Get terms from at least one other buyer before you answer.
Reader reviews
What people who worked with pre.dev say
n/a/10
None yet
A written summary appears once enough reviews are published. It will quote both praise and complaints.
No reviews yet. Be the first.
If you have sold data to, hired, or worked for pre.dev, your review helps the next person decide.
FAQ
Questions, answered with sources
pre.dev licenses private code repositories and their git history only. Owners with email, CRM or company files need a different buyer, and our quiz shows which ones take those records.1
pre.dev accepts individuals such as a fractional CTO or solo developer, as well as agencies and companies. The signup lists no headcount requirement.2
pre.dev says its license is non-exclusive by default, so you keep the code, keep shipping it, and it can pay more than once.9
pre.dev says it pays Net 15 after funds land, which means about 15 days after the money from a lab reaches it. The page does not say how long that first step takes.3
pre.dev turns away repos that are public, forks, archived or published packages. Every repo passes that check before listing.6
Every business is different, so this one is best talked through with the buyer you're working with. Their team goes over it with you before anything is signed.
Before you sign
Questions to talk through with your buyer
Every business is different, so these are best talked through with the buyer you're working with. Their team goes over them with you before anything is signed.
Questions for this kind of business
- Can we read the seller agreement before we connect a Git account?
- How long do you and the labs keep our code, and how is deletion confirmed?
- Do client contracts or open-source licenses limit what we can license?
- Who owns this data: the company, an estate, or someone else?
- Do customer, supplier or platform contracts, NDAs or API terms restrict this?
Questions for any buyer
- Is the license exclusive, and for how long?
- Can you sublicense the data, and to whom?
- Which AI labs will receive it, and will you tell us?
- How long do you keep it, and how is it deleted?
- What is your liability cap, and who indemnifies whom?
- Will the contract ban re-identification of people in the data?
- Who removes personal data, by what method, and do we approve it first?