pre.dev vs Turing (Project Lazarus)
Both pay companies for internal business records used to train AI. The main differences on their published terms are below; the real answer comes from putting both offers side by side.
Key differences
- They pay differently: pre.dev: pays per repository (software code); Turing (Project Lazarus): pays a one-time amount for your records.
- Published ranges: pre.dev $740–$6K, Turing (Project Lazarus) up to $1M (each buyer's own figure, not an offer).
Side by side
| pre.dev | Turing (Project Lazarus) | |
|---|---|---|
| Type | Pays per repository (software code) | Pays a one-time amount for your records |
| Who qualifies | No minimum published | No minimum published |
| Accepts | operating, closing, closed | operating, closing, closed |
| How it pays | per-sale, pre.dev shows per-repo payouts and per-token rates; it says one repo can pay more than once under the same agreement. | upfront: one payment, no retainer or recurring commitment; Turing confirms the figure after sampling. |
| Published range | Page headline shows $6,000 for a repo; example repo values shown range from $740 to $4,180 and are labeled as examples. Rates shown: $100 per million tokens of source, $40 per million tokens of Git history. | Turing's own figure: a single payout of up to $1M, scaled to how complete, rare and well-preserved the record is. Not an offer. Source: lazarus.turing.com, as of October 2026. |
| When it pays | Net 15 after funds land | Not published. Turing says it confirms the figure after sampling, usually within a week. |
| Exclusivity | non-exclusive by default; you keep the code | not stated |
| Data handling | Not described for code licensing. | The company sets the scope and what is redacted or never leaves its environment. Turing works from a copy, removes personal data and secrets before training, processes in an isolated (air-gapped) environment, works within the company's sign-off process, and states SOC 2 Type II and an NDA from first contact. |
| Good fit if | You own private code you can legally license and want to keep using it while licensing copies to AI labs. | Your company (operating, winding down or closed) has years of working records, such as chat, code, tickets and wikis, and wants one payment rather than ongoing revenue. |
You can apply to both at once. Nothing you submit commits you, and two offers make it easier to judge either one. See comparing offers.
Apply to pre.dev Apply to Turing (Project Lazarus)
pre.dev: We have not joined this buyer's referral program. If we do, it may pay us a fee when a company we sent signs, and this page will say so.
Turing (Project Lazarus): We have not joined this buyer's referral program. If we do, it may pay us a fee when a company we sent signs, and this page will say so.
Sources
- pre.dev home page, code licensing section, accessed 2026-10-15
- pre.dev code licensing sign-up, accessed 2026-10-15
- Project Lazarus | Turing, accessed 2026-10-27