Why it is useful for AI training
Agents that help engineers debug a failing test or prepare a design review need to see how real teams reason: which test failed, what the review asked, how a yield problem was traced to its cause. Chip companies keep this work in house, so public text holds little of it. Years of review notes and test logs show that reasoning step by step.
Test and yield logs are the notebook of a production line: each entry records what was tried, what failed and what changed next.
What sets the price
- Test and yield logs linked to the review or change that followed them.
- Design review notes and failure analysis reports with the reasoning written out.
- Procedures and checklists with their revision history.
- Several years of records from the same systems.
- Mostly English records, and a contact who can work in English.
Priced with the rest of your archive. The estimate on this page prices the documents, test logs and project records of a manufacturer on their own, without design files, code, email or chat, and with no regulated data inside.
What blocks a deal, and the fix
- Export-controlled designs and technical data
- They stay out. We ask about export status at screening, and a record that is controlled, or whose status is unclear, is not licensed.
- Customer, foundry and partner material held under confidentiality terms
- Customer designs, customer test results and information a partner shared in confidence stay out. We read those agreements at screening.
- Design blocks and tools licensed from others
- Licensed blocks, and outputs a tool license restricts, are checked at screening and left out where the terms forbid it.
- Health, clinical or personal data about individuals
- It stays out. The estimate on this page assumes none is inside, and records about children are not accepted.
What owners overlook
- Failed tests and the notes on why they failed teach more than a passing result.
- A procedure's change history shows how a team learned from a fault.
- Review comments show what experienced engineers check first, which no datasheet records.
Market evidence
- AI companies are buying old work messages and records from companies as training data.Forbes, (opens in a new tab)
- Published programs flag regulated data, such as health, financial or personal information, at screening, and remove client identities before delivery.Rightmark,
How a deal works
Appraise
Answer a few questions about what you have. See an indicative range, what sets it and what would raise it. No files, no access.About a minute
Verify title
We confirm the company controls the archive, check personal data and third-party rights, and assemble the ownership pack the deal needs.Before any offer
Route
The archive goes to the route that fits it: an exclusive lump sum for a term, or a non-exclusive revenue share.Sign and get paid
You approve the agreement and its scope before anything moves. We never hold your passwords: transfers use scoped, revocable connections your admins approve, or exports.Payment about 2 to 13 weeks after signing
Questions
How much are semiconductor engineering records worth?
They are priced like the rest of a company archive, which published programs list at $185,000 to $1M+. Documents, test logs and project records on their own, as in the estimate on this page (One archive: 80 staff, 8 years, 3 tool types), come to $310,000 to $660,000 at Medium confidence. Rightmark's public deal records hold no sale of semiconductor engineering records yet. Indicative estimate, not an offer.
Source: Rightmark,
Can we license chip designs?
Not export-controlled designs or technical data: those stay out. Other design files are reviewed one by one for export status and third-party rights before anything moves. Code and scripts the company owns can go through our source code route.
Do customer and foundry agreements matter?
Yes. Customer designs, customer test results and information a foundry or partner shared in confidence stay out. We read those agreements at screening and leave out what they cover.
Can we keep using the records ourselves?
Yes. You keep your copy and keep using your systems; the buyer gets a de-identified copy for training. On an exclusive lump sum you cannot license the same data to others for the term and scope; on a revenue share you can.
What do we warrant about the records?
That the company owns or controls the records it licenses and can authorize their export. Export status and confidentiality terms are checked at screening, and controlled or covered records stay out.
How long until we are paid?
Screening takes a few days and the data inventory moves at your pace. Payment usually arrives 2 to 13 weeks after signing, an inferred guide, depending on the buyer.