Compensation for eligible code and bundled artifacts; confirm terms. Rights-holding founders and engineering leaders; current review required. Confirm the final scope and acceptance terms before providing records.
This profile checks the public program and its stated terms. It does not authenticate a particular sender, audit completed deals, or certify security practices. No owner rating or paid-outcome estimate is assigned.
How evidence is checked · Commercial disclosureWhat is Turing (Project Lazarus)’s company-data program?
Turing's Project Lazarus pays for eligible private software and related operational artifacts used in AI training. Its official announcement includes both legacy and modern codebases with surrounding work history. Official program ↗
Who is the counterparty?
Turing (Project Lazarus) is categorized here as direct licensing. This describes the published route, not necessarily the entity that trains an AI model. Confirm the contracting company, its authority to license the records and the ultimate permitted recipients. A real company can still be impersonated; reach its program through the official source linked here.
Which records does it describe?
Private codebases, Pull requests, Jira tickets, Product requirements, Architecture documents, Support threads. Official program ↗
What does that mean for your archive?
Map these categories to the systems and date ranges your company actually retains. Include linked decisions and outcomes where available, but identify customer restrictions, personal information, third-party content and privileged material separately. A match with a listed category is a reason to ask about eligibility, not approval to send an export.
Which companies may qualify?
Founders and engineering leaders with rights to private code and associated records. Indexed program text mentions operating and winding-down companies, but the live page did not expose full eligibility text in this check. Official program ↗
How much does Turing (Project Lazarus) publish?
Legacy code: $10K–$100K+; modern code: up to $10K per codebase (official program announcement; eligibility-dependent). Official program ↗
How should you interpret that figure?
Published bands, illustrative calculators and quoted examples are different types of evidence. None is a guaranteed price for your company. Where no range has been verified, do not fill the gap with another provider’s estimate. Request a written proposal identifying the records, rights, deductions and conditions behind the amount.
When and how is payment described?
The official announcement describes compensation for eligible code and bundled artifacts. Indexed program text describes one payment; the precise current structure and settlement terms need direct confirmation. Official program ↗
What does this business model mean for an owner?
A stated licensing program does not make every submission payable. Ask which milestone creates the payment obligation, who decides acceptance, how a rejected dataset is handled, and whether exclusivity starts before any money is due.
Which evidence is available, and what is still open?
These labels describe disclosure, not quality scores. “Verify in writing” means this review does not establish the term for your transaction.
| Criterion | Evidence status | Owner check |
|---|---|---|
| Program identity | Official source linked | Use the provider’s own domain to verify the sender and contracting entity. |
| Record fit | Categories described | Private codebases, Pull requests, Jira tickets. Ask for a bounded scope. |
| Eligibility | Published description | Founders and engineering leaders with rights to private code and associated records. Indexed program text mentions operating and winding-down companies, but the live page did not expose full eligibility text in this check. |
| Price visibility | Attributed public claim | Legacy code: $10K–$100K+; modern code: up to $10K per codebase (official program announcement; eligibility-dependent) |
| Payment mechanics | Published description | The official announcement describes compensation for eligible code and bundled artifacts. Indexed program text describes one payment; the precise current structure and settlement terms need direct confirmation. |
| Exclusivity and downstream rights | Verify in writing | Confirm duration, permitted uses, sublicensing and whether competing licenses are allowed. |
| Acceptance and deletion | Verify in writing | Specify rejection rules, access expiry, retention and deletion of samples and rejected records. |
What is not yet established?
- The program landing page was accessible but its substantive live text could not be extracted, so current thresholds and terms remain partly unverified.
- Confirm whether non-code records qualify alone, retained ownership, accepted jurisdictions and the exact payment trigger.
How should you start the conversation?
Begin with a non-sensitive description of your company, systems, approximate history and record categories. Ask for the legal entity name and proposed use before providing samples. Use a separately scoped sample with agreed handling terms; a request for broad administrator access deserves a specific explanation and a limited-access alternative.
Questions to resolve before signing
- Which exact records and time periods are included, and which are excluded?
- Who accepts the data, using what test, and by what deadline?
- What amount reaches us after fees and costs, and when is it due?
- Which customers or labs may receive copies, and for which uses?
- Can we license the same records elsewhere, and what happens if no buyer is found?
- How are samples, rejected records and retained copies deleted or restricted?
Which alternatives are worth comparing?
These are comparison routes, not ranked recommendations. Similar program models come first; eligibility and current demand can still differ. Compare the same record scope with each provider.
| Provider / model | Payment | Published figure | Fit to investigate |
|---|---|---|---|
| Turing (Project Lazarus)Direct licensing | Compensation for eligible code and bundled artifacts; confirm terms | Legacy code: $10K–$100K+; modern code: up to $10K per codebaseofficial program announcement; eligibility-dependent | Rights-holding founders and engineering leaders; current review required Source ↗ |
| AppenDirect licensing | Negotiated fee on acceptance; preparation costs covered | Not publicly verified | Enterprises with operational history; wind-downs considered Source ↗ |
| CorpusDirect licensing | On delivery confirmation; larger deals may use tranches | $100K–$2M+ across published company-size bandsprovider-reported engagement ranges | Enterprise archives; published size examples start at 25 staff Source ↗ |
| Google Content Offer PilotDirect licensing | Negotiated delivery fee; non-exclusive licensing | Not publicly verified | Invited content owners with sufficient rights; applications reviewed Source ↗ |
| LH2 AI LabsDirect licensing | Source licensing described; owner compensation terms unpublished | Not publicly verified | Source institutions include enterprises, hospitals and factories Source ↗ |
See all 25 providers side by side · Read the detailed two-provider comparisons
Have a proposal from Turing (Project Lazarus)?
Record the amount, scope, payment trigger and open terms in the local comparison worksheet. It organizes the information you enter; it does not value your archive, contact providers or publish individual offers.
Sources & further reading
Provider statements are attributed claims, not audited outcomes. Reviewed 19 October 2026.