LicenseTheData.comA field guide to business-data licensing
Home/Comparisons

Public evidence · 13 October 2026

Replay vs Turing Project Lazarus

Managed intermediary meets direct licensing. Neither advertised amounts nor a public seller route establish what your business will receive.

Jump to the terms ledger ↓

Research comparison; limited public terms. Pair-level evidence and scenario review is pending. Published fields alone do not meet our indexing threshold. This page is noindex and absent from the sitemap, not a negative verdict.

The terms ledger.

Headquarters or contact location is not seller eligibility. Response, acceptance and payout stages are not interchangeable.

Published descriptions and unresolved contract terms
CriterionReplayTuring Project Lazarus
Operating recordsPublished
CRM, support, threads, code/commits, docs, financial records, presentations and product analytics
Source ↗
Published
Communications, tickets, wikis, databases and code; code not required and not bought alone
Source ↗
Company eligibilityPublished
Advertised employee bands: 20–50, 50–250, 250+. Not a verified hard minimum.
Source ↗
Published
Any company with real operating history and an authorized representative; operating, winding-down or closed.
Source ↗
Seller geographyUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Published
Most regions; strongest demand US/UK/Canada/EU; export restrictions apply.
Source ↗
Published compensationProvider claim
Advertised size bands: $10K–$100K, $100K–$1M, $1M+. USD context; typically upfront cash plus perpetual revenue share, percentage not published.
Source ↗
Provider claim
Single payout up to $1M; USD context; not recurring royalties or a guaranteed offer.
Source ↗
Fees & net proceedsUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Unknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Timeline & payment triggerProvider claim
120 minutes refers to seller effort, not payment speed; payout deadline not published.
Source ↗
Provider claim
Intake call within one business day; valuation usually within a week of access. Neither is a payout deadline.
Source ↗
Preparation & seller effortPublished
Value → offer → export/de-identify → payout.
Source ↗
Published
NDA → intake → representative sampling/valuation → one contract.
Source ↗
Ownership & permitted usePublished
Retains underlying data, code and IP; cleaned version licensed.
Source ↗
Published
Retains underlying ownership; defined rights to prepared record.
Source ↗
Privacy & approvalProvider claim
Deletion from Replay on request if not continuing; separate commercial agreement governs liability and downstream terms.
Source ↗
Provider claim
Named team, scoped access, air-gapped processing; personal data/secrets removed before model use. SOC 2 Type II claimed.
Source ↗
ExclusivityUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Unknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Retention & deletionUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Unknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
HQ / published contactPublished
Delaware corporation; contact Brooklyn, NY, US. Not independently verified operational HQ.
Source ↗
Unknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.

Operating records

ReplayPublished
CRM, support, threads, code/commits, docs, financial records, presentations and product analytics
Source ↗
Turing Project LazarusPublished
Communications, tickets, wikis, databases and code; code not required and not bought alone
Source ↗

Company eligibility

ReplayPublished
Advertised employee bands: 20–50, 50–250, 250+. Not a verified hard minimum.
Source ↗
Turing Project LazarusPublished
Any company with real operating history and an authorized representative; operating, winding-down or closed.
Source ↗

Seller geography

ReplayUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Turing Project LazarusPublished
Most regions; strongest demand US/UK/Canada/EU; export restrictions apply.
Source ↗

Published compensation

ReplayProvider claim
Advertised size bands: $10K–$100K, $100K–$1M, $1M+. USD context; typically upfront cash plus perpetual revenue share, percentage not published.
Source ↗
Turing Project LazarusProvider claim
Single payout up to $1M; USD context; not recurring royalties or a guaranteed offer.
Source ↗

Fees & net proceeds

ReplayUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Turing Project LazarusUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.

Timeline & payment trigger

ReplayProvider claim
120 minutes refers to seller effort, not payment speed; payout deadline not published.
Source ↗
Turing Project LazarusProvider claim
Intake call within one business day; valuation usually within a week of access. Neither is a payout deadline.
Source ↗

Preparation & seller effort

ReplayPublished
Value → offer → export/de-identify → payout.
Source ↗
Turing Project LazarusPublished
NDA → intake → representative sampling/valuation → one contract.
Source ↗

Ownership & permitted use

ReplayPublished
Retains underlying data, code and IP; cleaned version licensed.
Source ↗
Turing Project LazarusPublished
Retains underlying ownership; defined rights to prepared record.
Source ↗

Privacy & approval

ReplayProvider claim
Deletion from Replay on request if not continuing; separate commercial agreement governs liability and downstream terms.
Source ↗
Turing Project LazarusProvider claim
Named team, scoped access, air-gapped processing; personal data/secrets removed before model use. SOC 2 Type II claimed.
Source ↗

Exclusivity

ReplayUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Turing Project LazarusUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.

Retention & deletion

ReplayUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Turing Project LazarusUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.

HQ / published contact

ReplayPublished
Delaware corporation; contact Brooklyn, NY, US. Not independently verified operational HQ.
Source ↗
Turing Project LazarusUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.

Which difference matters to your company?

Revenue model

For recurring upside versus a single transaction, Replay describes upfront cash plus perpetual revenue share; Turing Lazarus explicitly describes one payout. Ask how contingent share payments are calculated and audited.

Replay: source 1 ↗ source 2 ↗ source 3 ↗ Turing Project Lazarus: source 1 ↗ Public descriptions, not tested seller outcomes.

Data fit

For your existing records, start with category fit: Replay lists CRM, support, threads, code/commits, docs, financial records, presentations and product analytics; Turing Project Lazarus lists Communications, tickets, wikis, databases and code; code not required and not bought alone. Ask each which subset has active demand before preparing exports.

Replay: source 1 ↗ source 2 ↗ source 3 ↗ Turing Project Lazarus: source 1 ↗ Public descriptions, not tested seller outcomes.

Payment trigger

Replay: 120 minutes refers to seller effort, not payment speed; payout deadline not published. Turing Project Lazarus: Intake call within one business day; valuation usually within a week of access. Neither is a payout deadline. These clocks measure different stages, not equivalent payout deadlines; ask for a written acceptance-to-payment interval.

Replay: source 1 ↗ source 2 ↗ source 3 ↗ Turing Project Lazarus: source 1 ↗ Public descriptions, not tested seller outcomes.

Shared diligence, not shared guarantees.

Both routes need lawful rights to the material. Removing names does not remove confidentiality obligations or re-identification risk. Require sample approval, buyer-use restrictions, precise payment triggers and downstream retention/deletion terms.

Seller-outcome evidence

Replay: No independently audited operating-business payout established in this research. Provider cases and partnership confirmations do not establish a typical seller outcome.

Turing Project Lazarus: No independently audited operating-business payout established in this research. Provider cases and partnership confirmations do not establish a typical seller outcome.

Put two routes side by side.

Choose two different providers. No income ranking.

Sources & unknowns.

Source claims were inspected on 13 October 2026. No intake was submitted or transaction tested. Unknowns are not zero fees, universal eligibility or unrestricted rights.

Read the evidence and indexing methodology →