Companies Buying Data

Buyer Database › Turing (Project Lazarus)

Turing (Project Lazarus): What It Pays for Business Data, Who Fits, and How to Reach It

Turing (Project Lazarus) is a buyer programme (codebases & defunct-company archives). It publishes a payout of Legacy codebases typically $10K-$100K+; modern codebases $1,000 per PR up to $10K per codebase; org artifacts $50 each bundled (Mar 2026 published rates) for companies that fit its floor: Founders/engineering leaders with private codebases; defunct startups for the archives track. Every figure on this profile is Turing (Project Lazarus)'s own published figure, checked 2026-11-10, and is not an offer.

Book the 7-Minute Fit Interview

What Turing (Project Lazarus) buys

Software/engineering (FinTech, pharma, manufacturing, SaaS archives)

Published payout and fit floor

Published payoutLegacy codebases typically $10K-$100K+; modern codebases $1,000 per PR up to $10K per codebase; org artifacts $50 each bundled (Mar 2026 published rates)
Fit floorFounders/engineering leaders with private codebases; defunct startups for the archives track
YearsNot published
IndustriesSoftware/engineering (FinTech, pharma, manufacturing, SaaS archives)
How to engageApply via Turing's Project Lazarus page
Sourcehttps://www.turing.com/blog/agi-advance-newsletter-57
Checked2026-11-10 · Status: verified_secondary

Published ranges are each buyer's own figures, checked on the date shown. They are not an offer, quote, valuation, or guarantee of payment. AIData.Broker's compilation of public figures puts the median published offer at about $280,000 per company and the median public sale at about $31,600 — most companies should expect an actual offer, if any, only after a buyer reviews a metadata-only manifest, and it may be below published ranges or none at all.

Terms and watch-outs

CONFLICT FLAG: AIData.Broker's Nov 7, 2026 buyer graphic lists Turing (Lazarus) as 'revenue share' with no figure, after Turing replaced earlier figures - the Mar 2026 per-item rates above may be superseded. Verify current terms on the Lazarus page before relying on them.

Why owners consider Turing (Project Lazarus)

Owners compare Turing (Project Lazarus)'s published terms against the other buyers in this database before applying anywhere — a single-buyer application gets a single-buyer price, and published terms differ on payout structure, exclusivity, and who covers de-identification.

One manifest instead of one application

A single-buyer application gets a single-buyer price. Book the fit interview, build one metadata-only manifest, and let every buyer you fit - including Turing (Project Lazarus) - review the same manifest before you sign anything.

Book the Fit Interview

Frequently asked questions

What does Turing (Project Lazarus) pay for business data?

Turing (Project Lazarus) publishes: Legacy codebases typically $10K-$100K+; modern codebases $1,000 per PR up to $10K per codebase; org artifacts $50 each bundled (Mar 2026 published rates). Published ranges are each buyer's own figures, checked on the date shown. They are not an offer, quote, valuation, or guarantee of payment. AIData.Broker's compilation of public figures puts the median published offer at about $280,000 per company and the median public sale at about $31,600 — most companies should expect an actual offer, if any, only after a buyer reviews a metadata-only manifest, and it may be below published ranges or none at all.

Who fits Turing (Project Lazarus)?

Its published floor is: Founders/engineering leaders with private codebases; defunct startups for the archives track; years: Not published. This site's introduction service is built for 20+ staff, 3+ years, 5+ systems - a buyer with a higher floor will apply its own floor.

How do I reach Turing (Project Lazarus)?

Apply via Turing's Project Lazarus page. Or book one fit interview here and have matching buyers - including Turing (Project Lazarus) if you fit - review the same manifest.

Source - checked 2026-11-10: https://www.turing.com/blog/agi-advance-newsletter-57 (see profile notes for the dated secondary compilations used where a programme page is script-rendered). Corrections: About.