Buyer profile · One-time payment
Turing (Project Lazarus)
Turing's Project Lazarus pays a single amount for a company's operating record (team communication, code and engineering history, wikis and runbooks) to train frontier AI models.
Good fit if: 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.
The facts
Every row is from Turing (Project Lazarus)'s own pages, checked 2026-10-25. "Not stated" means we did not find it published.
| Type | Pays a one-time amount for your records |
|---|---|
| What it takes | Team communication: threads, channels and decision context; Source code, code reviews, tickets and iteration history; Wikis, runbooks, schemas and internal knowledge; Records of how decisions and trade-offs were made; Areas named: software and engineering, finance and accounting, customer support, sales and CRM, legal and contracts, operations and logistics |
| Who qualifies | Most regions; strongest demand in the U.S., UK, Canada and the EU. Turing flags data-export restrictions early.. Any company with a real operating history and someone authorized to transfer the data; active, winding-down and closed companies, across industries. Source code is not stated as required. |
| Company status accepted | operating, closing, closed |
| How it pays | upfront: one payment, no retainer or recurring commitment; Turing confirms the figure after sampling. |
| Published range | 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. (buyer's label: up to (buyer's own figure, not an offer)) |
| When it pays | Not published. Turing says it confirms the figure after sampling, usually within a week. |
| Fees to you | Not stated |
| Exclusivity | not stated |
| Data handling | 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. |
How its process works
- Intake call under NDA, usually scheduled within one business day
- Sampling: Turing reviews a representative slice, usually within a week
- Offer: a single valuation and one contract
What to check before you sign
- Program site content could not be read (renders only in a browser); details come from Turing's blog
- No data handling, payment timing or contract terms published
- Code may include third-party or open-source components the seller cannot license; confirm with a lawyer
- Closed companies may need trustee or court approval to sell assets
Questions to ask Turing (Project Lazarus)
- Who signs the agreement with us, and in which state is that company registered?
- When exactly are we paid, and what has to happen first?
- Is the license exclusive? For how long, and in which uses?
- Who de-identifies the records, where, and can we review the result?
- What happens to the copy when the license ends?
More on this in questions to ask a buyer and comparing offers.
What we could not confirm
- Rates previously taken from Turing's March 2026 newsletter (per codebase, per pull request, per artifact) are no longer on the Lazarus page; replaced with the page's 'up to $1M' single payout (checked in a browser Oct 27, 2026)
Sources
- Project Lazarus | Turing, accessed 2026-10-27
Turing (Project Lazarus) is named only to identify it. It has not reviewed or endorsed this page. Corrections: paul@minimusbrands.biz.