Know a company with years of records? Refer it and earn up to $100K
Hardware engineering records

EVT and DVT Test Reports: Can You License Them for AI?

Can a hardware company license EVT, DVT and PVT test reports and failure analysis without its CAD? Who names test records, export rules and what to remove.

Short answerChecked

Yes. A hardware company can license EVT and DVT test reports and failure analysis records without the CAD files, if it owns them and they hold no customer or export-controlled data. Buyers name them: Mercor's hardware listing lists measured test results and Handshake names test reports. No buyer has published a price for test reports alone; they add most value next to the design they tested.

Price for test reports alone
None publishedChecked 19 Nov 2026
Buyers that name test records
Mercor, HandshakeRead on their own pages
Simulation models with solved results in one lot
287 of 373Hilco Project Beacon
House keys on a lease folder and an inspection checklist
Key points
  • Test reports can be licensed without the CAD, but no buyer publishes a price for them alone.
  • Buyers name measured test results and test reports, usually beside the design they describe.
  • Test data on a defense article is ITAR technical data: the word "testing" is in the rule.
  • Failure analysis with its root cause and fix is the most useful part of a test archive.

Are EVT and DVT test reports and failure analysis records worth anything to AI companies without the CAD files?

They are worth something, but less on their own than beside the design. The table sets out what each build stage produces and what each record proves, with the buyer statements and rules that apply. Stage definitions follow the hardware quality company Instrumental.

Build stage or sourceWhat the record provesRecords it producesStated rule or priceDate checked
EVT (engineering validation test)Whether the combined looks-like and works-like design meets its requirementsTest plans, bring-up logs, functional and performance results, issue listsNo published price for EVT records alone19 Nov 2026
DVT (design validation test)Whether the production design, built with production parts and tools, passesReliability, environmental, drop and certification pre-test reports, failure analysisNo published price for DVT records alone19 Nov 2026
PVT (production validation test)Whether the line builds sellable units at yieldYield data, test station results, corrective actionsNo published price for PVT records alone19 Nov 2026
Mercor hardware listingA buyer wants test results with the designMeasured test results for designs (nice to have)Published range $45K to $1.35M for the whole company archive19 Nov 2026
Handshake AIA buyer names test reports for hardware companiesDesign documentation, specifications, test reportsNo range for hardware on its page19 Nov 2026
22 CFR 120.33 (ITAR)Test information on a defense article is controlledAny test data for a defense articleRule: leave it out of any license19 Nov 2026

Instrumental defines the stages this way: "The EVT build is the first time you combine looks-like and works-like into one form factor, with production intent materials and manufacturing processes." "The DVT build is supposed to be one configuration of your production-worthy design, made of components from production processes (and hard tools) and on a line following production procedures." At PVT "the units you are building are supposedly intended to be sold to customers, if they pass all of your test stations" (Instrumental).

No buyer has published a price for test reports on their own as of 19 November 2026. Every public figure we found prices a whole archive in which test results are one part.

Why would an AI company want test reports at all?

A CAD model shows what was designed. A test report shows whether it worked, and a failure analysis shows why it did not and what changed. That is the reasoning an engineering model cannot learn from geometry alone. Mercor's listing asks for designs with "the test results that go with them", and a buyer posting on Cad Crowd on 3 November wrote that "Revision histories, engineering reviews, simulations and physical test results are valuable where available".

The most useful test archives keep four things linked: the requirement, the test setup and method, the measured result with its pass or fail, and for failures the root cause and the design or process change that closed it. An archive where a DVT drop failure points to an ECO and a retest is worth more than a folder of PDFs with no thread between them.

Test records also carry something CAD cannot: the limits of a design. A thermal test that failed at one ambient temperature, a connector that cracked after a set number of cycles, a radio that lost range inside one enclosure material. Those are the facts an engineer needs before trusting a design tool, and they exist only in test archives. That is why buyers list test results next to the CAD rather than instead of it.

Can a hardware startup sell its firmware source code and test logs for AI training?

Yes, if the startup owns both and removes what it does not own. Firmware is named on Mercor's hardware listing next to measured test results, and a liquidator's lot lists 202 firmware projects beside its PCB and CAD files (Hilco). Test logs from bring-up and validation pair naturally with the firmware build they ran on, which makes the two more useful together than apart.

The blockers for firmware are different from the blockers for test logs: vendor SDK terms, open-source licenses in the tree and export classification of source code. Those are covered in licensing firmware and embedded code. Test logs mostly raise a simpler question: do they contain customer data, serial numbers tied to customers, or personal data from field units?

Are there export control issues with licensing test reports and engineering drawings?

Test reports avoid most of the problems that come with geometry, but not all. Under the ITAR, technical data covers information "required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance, or modification of defense articles" (22 CFR 120.33). Testing is in that list. A DVT report on a defense article is controlled exactly like its drawings.

For commercial products, test reports are usually EAR99 or not technology at all, and BIS says "EAR99 items do not require a license for export, reexport, or transfer (in country) in most situations" (BIS). The exception is detailed test methods for controlled items, which can be controlled technology. If so, sharing them with a foreign person inside the US is a deemed export (BIS). The ITAR and EAR checklist has the classification steps.

Who owns test reports made for a client, or by an outside lab?

Your own staff's reports on your own products belong to your company: the Copyright Office describes a work made for hire as "A work prepared by an employee within the scope of his or her employment" (U.S. Copyright Office). Two cases need care. Reports you produced for a client under a services contract usually follow the contract's assignment of deliverables, so they belong to the client unless the contract says otherwise. Reports from an outside test lab often carry the lab's terms and the lab's own data.

Certification pre-tests and reports from a notified body or test house can also hold that body's methods or marks. Leave them out unless the terms allow sharing. The design consultancy ownership guide covers client-made work in detail.

We are a 60-person hardware company with 15 years of SolidWorks assemblies, PCB designs and test reports. What is that archive worth?

The archive as a whole sits in the band of the largest published hardware range, $45K to $1.35M per company, which requires native CAD assemblies with feature trees and names measured test results as a nice-to-have. Test reports linked to those assemblies raise the value inside the range. On their own they have no published price. The hardware engineering data hub shows every public figure side by side.

Our hardware company is closing. Who would buy our CAD files, firmware and engineering records, including test reports?

The same programmes that buy from operating companies, and liquidators selling the archive as one lot. In Hilco's Project Beacon listing, simulation models are counted with their results, "373 FEMM magnetics / coil simulation models, including 287 with solved-result files" (Hilco): a sign that records with results attached are what get counted. Export the test database and the shared drives with their folder structure before systems close. The hardware startup shutdown guide covers who signs at each stage.

What should a hardware company check before signing a data license for its CAD files and test results?

Check these before any report leaves the company.

  • Programs: drop any defense or export-controlled program, and any program a customer owns.
  • Labs: remove outside lab reports whose terms bar sharing.
  • People: remove engineer names, emails and signatures if the buyer does not need them.
  • Field data: remove customer names, addresses and serial numbers tied to customers in RMA and field-failure records.
  • Links: keep the requirement, test, result and fix connected, with stable IDs.
  • Terms: training use only, no resale, deletion at the end, and an audit right.

This page is general information, not legal advice.

How should a test archive be organized before it is licensed?

Most hardware companies keep test records in three or four places: a test database or spreadsheet, a shared drive of PDF reports, an issue tracker, and the change orders in the PDM or PLM system. A buyer can use them only if the links between them survive the export. The steps below keep those links without moving any file out of the company until a license is signed.

  • Give every product, build stage (EVT, DVT, PVT) and board or assembly revision a stable ID, and use it in every file name.
  • Export the test database with its raw measurements, limits and pass or fail results, not only the summary charts.
  • Keep the test plan with each report, so the method and the conditions travel with the result.
  • Link each failure to its analysis, root cause, change order and retest.
  • Note which reports came from outside labs and under what terms.
  • Write a one-page manifest: products, stages, years, report counts and what was removed.

A manifest like that is also how a buyer judges the archive before it sees any data. Counting reports by product and stage tells a buyer more than a folder size does, in the same way a liquidator counts projects and files rather than gigabytes.

What is the first step for a company that wants to license its test records?

Count the reports by product and build stage, and mark which belong to customers or defense programs. Then decide whether to offer them with the CAD archive or alone; with the CAD is usually worth more, as the hardware engineering data hub explains. We help you license your data. Origin Data Partners is an independent data partner. Your company decides what is shared and signs any license itself, and a buyer may pay Origin when a deal closes. The two-minute estimate is the first step, and nothing leaves your systems until you decide.

Origin Data Partners works with companies that own data and helps get it bought. We are independent of the services on this page, and a buyer may pay us when a deal closes (how Origin is paid). See what your data is worth.

Common questions

Can we license failure analysis reports without the design files they refer to?

Yes, if the company owns them and they hold no customer or export-controlled data. They are worth more with the design, because the design shows what failed. No buyer publishes a price for failure analysis alone. Keep the root cause and the fix in each record, since that is the reasoning a model learns from.

Is DVT test data on a defense product covered by the ITAR?

Yes. The ITAR defines technical data as information required for the design, production, testing and other work on defense articles, including documentation. A DVT report on a defense article is controlled like its drawings and stays out of any AI license. Commercial products are usually EAR99, but classify each program before you include it.

I am the lawyer for a product design consultancy. Can my client license its engineering test reports to AI companies without the CAD, and what should the contract say?

It can license reports on its own products, and reports made for clients only with their written consent, provided none holds lab-restricted or export-controlled data. The contract should list the programs and years in scope, state that no CAD is included, limit use to training, bar resale and sublicensing, require deletion at the end, give an audit right and put responsibility for any later-found restricted data in writing.

A buyer offered $20,000 for our DVT and reliability test archive. Is the offer fair?

No buyer has published a price for test reports alone, so there is no public benchmark for that offer. Compare it with what the whole engineering archive could support: the largest published hardware range is $45K to $1.35M per company and treats test results as a nice-to-have. Licensing tests separately can lower the value of the CAD later.

Do PVT yield and test station records have value to AI companies?

They can, as part of a hardware or manufacturing archive, because they connect a design to how it was built and tested at volume. No buyer prices them on their own. They often hold supplier and contract manufacturer data, so check your manufacturing agreement before you include them.

Should we include RMA and field failure records with our test reports?

They are useful because they show how designs failed in real use, but they carry the most personal and customer data. Remove customer names, contact details and serial numbers tied to customers first. Keep the failure mode, the root cause and the fix. Check whether any record belongs to a customer under a support contract.

Sources and further reading

What is your company’s data worth?

AI companies pay $20K to $5M for company records. Six questions, no files.