pre.dev
Third-party trackers cite an earnings example of $100 per million source tokens and $40 per million git-history tokens; this could not be verified on pre.dev's own pages and is not used as a valuation-model input.
pre.dev's /labs and /rl-tasks pages are buyer-facing; the seller route is /code-licensing.
What the provider says it does
pre.dev's code-licensing page accepts both individuals (a fractional CTO or solo dev with their own codebases) and agencies or companies with client or company codebases to license, creating a personal or organization account accordingly. Its documentation says every codebase is licensed directly from the team that built it under a signed agreement that lets pre.dev sublicense it to labs; a repository is delivered only while the owner's signed agreement is in place and the owner has not asked for it to be removed. Licenses to labs are non-exclusive by default, with terms and pricing set per engagement. pre.dev says secrets and personal data are removed from the full git history before the code is counted, graded, delivered or turned into tasks; contributors become pseudonyms; codebases are delivered under catalog IDs with no owner or repository name; and signed download links expire after seven days. It runs exposure checks that refuse repositories that are public, archived, forked from outside projects, or published on npm/PyPI. These are pre.dev's own statements and have not been independently verified.
- Business model
- Broker / transaction layerLicenses codebases from their owners under a signed agreement and sublicenses them to AI labs as training data and RL tasks.
- Seller intake
- Self-serve onboarding at https://pre.dev/code-licensing (individual or agency/company account)
- Contracting party
- Not publicly stated
- Data focus
- Private production codebases with full git history
- Data types considered
- Private repositories with branches and tagsPull requests with reviewsGit history
- Intended uses
- Training · Post-training · Evaluation
- Geography
- Not publicly stated
- Stated handling & privacy
- pre.dev says secrets and personal data are removed from the full git history before the code is counted, graded, delivered or turned into tasks, and contributors become pseudonyms.
- pre.dev says codebases are delivered under catalog IDs with no owner or repository name, via signed download links that expire after seven days.
- pre.dev says exposure checks refuse repositories that are public, archived, forked from outside projects, or published on npm/PyPI.
- Retention, deletion, resale
- A repository is delivered only while the owner's signed agreement is in place and the owner has not asked for it to be removed; the signed agreement lets pre.dev sublicense to labs
- Payment / licensing model
- Provider says terms and pricing are set per engagement; no public rate card was verified on its own pages
- Exclusivity
- Provider says licenses to labs are non-exclusive by default
- Referral program
- Not publicly confirmed
Sources
- pre.dev — License your codebases (opens in new tab)Provider website · reviewed 2026-10-17
- pre.dev docs — Trust and data handling (opens in new tab)Provider website · reviewed 2026-10-17