Matching network 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.
| Criterion | Nomad Data | Turing Project Lazarus |
|---|---|---|
| Operating records | Published General commercial datasets and expertise Source ↗ | Published Communications, tickets, wikis, databases and code; code not required and not bought alone Source ↗ |
| Company eligibility | Published Match data supply to buyer question; negotiate directly Source ↗ | Published Any company with real operating history and an authorized representative; operating, winding-down or closed. Source ↗ |
| Seller geography | Unknown Not published / not established Not established in inspected sources: Not published. Ask the provider; missing terms do not establish acceptance, free fees or a payment deadline. Inspection URLs remain in the profile source list. | Published Most regions; strongest demand US/UK/Canada/EU; export restrictions apply. Source ↗ |
| Published compensation | Provider claim Direct buyer contract, seller keeps 100% of sale Source ↗ | Provider claim Single payout up to $1M; USD context; not recurring royalties or a guaranteed offer. Source ↗ |
| Fees & net proceeds | Published No usage or transaction fees stated; other subscription costs not established 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 trigger | Provider claim No buyer match, contract or payout SLA Source ↗ | Provider claim Intake call within one business day; valuation usually within a week of access. Neither is a payout deadline. Source ↗ |
| Preparation & seller effort | Published Data Sellers / seller connection route Source ↗ | Published NDA → intake → representative sampling/valuation → one contract. Source ↗ |
| Ownership & permitted use | Unknown Not published / not established Not established in inspected sources; confirm in contract. | Published Retains underlying ownership; defined rights to prepared record. Source ↗ |
| Privacy & approval | Provider claim Nomad says it does not need access to seller data; buyer-specific agreements still require diligence. Source ↗ | Provider claim Named team, scoped access, air-gapped processing; personal data/secrets removed before model use. SOC 2 Type II claimed. Source ↗ |
| Exclusivity | Unknown Not published / not established Not established in inspected sources; confirm in contract. | Unknown Not published / not established Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted. |
| Retention & deletion | Unknown Not published / not established Not established in inspected sources; confirm in contract. | 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 contact | Unknown Not published / not established Not established in inspected sources; confirm in contract. | Unknown Not published / not established Not established in inspected sources. Ask for the actual agreement; unknown does not mean free, unrestricted or accepted. |
If you already have a marketable data product, compare distribution rather than headline payouts: Nomad Data is matching network, while Turing Project Lazarus is direct licensing. Listing or matching creates no purchase commitment; ask who actually signs and pays.
For your existing records, start with category fit: Nomad Data lists General commercial datasets and expertise; 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.
Nomad Data: No buyer match, contract or payout SLA 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.
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.
Nomad Data: No independently verified operating-business seller payout found. Marketplace listing or matching is not a purchase commitment.
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.