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

Public evidence · 13 October 2026

Mercor vs Turing Project Lazarus

Direct licensing 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
CriterionMercorTuring Project Lazarus
Operating recordsPublished
Slack, Gmail, Salesforce, GitHub, Notion, contracts, clinical notes and QA logs
Source ↗
Published
Communications, tickets, wikis, databases and code; code not required and not bought alone
Source ↗
Company eligibilityUnknown
Not published / not established
Not established in inspected sources: No numerical employee minimum published on inspected data page. Ask the provider; missing terms do not establish acceptance, free fees or a payment deadline. Inspection URLs remain in the profile source list.
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
Individually quoted; no public dollar rate card.
Source ↗
Provider claim
Single payout up to $1M; USD context; not recurring royalties or a guaranteed offer.
Source ↗
Fees & net proceedsPublished
No upfront/setup fees or deductions; provider covers extraction, anonymization and transfer.
Source ↗
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
Wire upon delivery of anonymized dataset to buyer; typically 2–4 weeks from signed agreement.
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
Scope → connect 100+ supported tools → extraction/de-identification → delivery/payment.
Source ↗
Published
NDA → intake → representative sampling/valuation → one contract.
Source ↗
Ownership & permitted useUnknown
Not published / not established
Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted.
Published
Retains underlying ownership; defined rights to prepared record.
Source ↗
Privacy & approvalProvider claim
No data leaves until approval; encryption, access logs, session-isolated credentials; SOC 2 Type II claimed, audit not inspected.
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
San Francisco, CA named in program footer; US.
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

MercorPublished
Slack, Gmail, Salesforce, GitHub, Notion, contracts, clinical notes and QA logs
Source ↗
Turing Project LazarusPublished
Communications, tickets, wikis, databases and code; code not required and not bought alone
Source ↗

Company eligibility

MercorUnknown
Not published / not established
Not established in inspected sources: No numerical employee minimum published on inspected data page. Ask the provider; missing terms do not establish acceptance, free fees or a payment deadline. Inspection URLs remain in the profile source list.
Turing Project LazarusPublished
Any company with real operating history and an authorized representative; operating, winding-down or closed.
Source ↗

Seller geography

MercorUnknown
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

MercorProvider claim
Individually quoted; no public dollar rate card.
Source ↗
Turing Project LazarusProvider claim
Single payout up to $1M; USD context; not recurring royalties or a guaranteed offer.
Source ↗

Fees & net proceeds

MercorPublished
No upfront/setup fees or deductions; provider covers extraction, anonymization and transfer.
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.

Timeline & payment trigger

MercorProvider claim
Wire upon delivery of anonymized dataset to buyer; typically 2–4 weeks from signed agreement.
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

MercorPublished
Scope → connect 100+ supported tools → extraction/de-identification → delivery/payment.
Source ↗
Turing Project LazarusPublished
NDA → intake → representative sampling/valuation → one contract.
Source ↗

Ownership & permitted use

MercorUnknown
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
Retains underlying ownership; defined rights to prepared record.
Source ↗

Privacy & approval

MercorProvider claim
No data leaves until approval; encryption, access logs, session-isolated credentials; SOC 2 Type II claimed, audit not inspected.
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

MercorUnknown
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

MercorUnknown
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

MercorPublished
San Francisco, CA named in program footer; US.
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?

Payment trigger

If cash timing matters, Mercor publishes wire on buyer delivery, typically 2–4 weeks after signing. Turing Project Lazarus: Intake call within one business day; valuation usually within a week of access. Neither is a payout deadline.

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

Data fit

For your existing records, start with category fit: Mercor lists Slack, Gmail, Salesforce, GitHub, Notion, contracts, clinical notes and QA logs; 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.

Mercor: source 1 ↗ source 2 ↗ 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

Mercor: 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 →