DataPacts

Hardware and Product Engineering Companies Licensing CAD and Test Data to AI

Checked

At a glance

A hardware or product engineering company can license designs, circuit boards, firmware and test results it owns to AI companies, but customer-owned designs, third-party parts and code, and export rules for defense and dual-use products decide how much of a design vault can leave the company.

Independent reference. Every buyer is covered on the same terms, every figure carries its source and check date, and no buyer pays to be listed or placed higher.

Request an independent introduction

Tell us what data your company holds. We reply with the buyers that fit and what their terms leave out. Your details reach a buyer only after you agree to a named introduction.

IndependentYour details stay with us until you agreeNot selling is a valid outcome

Mercor's Hardware Engineering listing names circuit designs, PCB designs and measured test results, and Handshake AI names test reports (checked 2026-11-09, Mercor re-read 2026-11-17).

Buyers are listed alphabetically, never by payout, and every figure is the stating party's dated claim. No buyer states a price per file or per board, and deciding not to license is a valid outcome. Hardware and product designs are one sector in AI training data licensing.

What a Hardware Company Holds Across a Product's Life

A hardware company's records follow its product from mechanical design through circuit boards, firmware and simulation to measured test results, and buyers' pages name each stage in their own words. The table compares five record families, as of 2026-11-17, with the party that names each and its check date.

Record family What buyers' pages name Named by (stated by, checked) First limit Source
Mechanical design native multi-part CAD assemblies with feature trees; CAD assemblies and drawings; "CAD designs"; design documentation Mercor Hardware listing (2026-11-17); Labelbox Prism "CAD" (2026-11-16); AfterQuery (2026-11-09); Handshake AI (2026-11-09) customer-owned designs Mercor listings feed, hardware; prism.labelbox.com; afterquery.com; joinhandshake.com
Circuit and board design circuit designs; "PCB designs and Gerber files"; Altium and KiCad among tools Mercor Hardware listing (2026-11-17) customer-owned boards; licensed third-party IP Mercor listings feed, hardware
Firmware "Firmware" (nice to have) Mercor Hardware listing (2026-11-17) licensed and open-source code terms, not checked here Mercor listings feed, hardware
Simulation files "FEA and CFD simulation files"; simulation and test files; ANSYS among tools Mercor Hardware listing (2026-11-17) tool license terms, not checked here Mercor listings feed, hardware
Test and validation results "Measured test results for designs"; test reports Mercor Hardware listing (2026-11-17); Handshake AI (2026-11-09) customer data in results; export rules for defense products Mercor listings feed, hardware; joinhandshake.com

Native-file, feature-tree and file-type questions, and the rights of staff, contractors and clients over a design, are answered once, so this page does not repeat them. Firmware is a code question, and its terms are not checked here. The full treatment is under CAD and engineering files as AI training data.

Buyer Statements That Name Hardware Designs, Circuit Boards and Test Results

Five program statements name hardware designs, circuit boards or test results on the buyers' own pages, checked 2026-11-09 and, for Mercor's two listings, read again on 2026-11-17. The table compares them alphabetically, as of 2026-11-17, each value the party's own statement.

Program Role What it names for hardware Size or threshold stated Source
AfterQuery Data Partnerships B "codebases, financial models and CAD designs" among business data already processed (launch post 2026-10-23) several teams across several systems and a few years of history afterquery.com/data-partnerships
Handshake AI Data Partnerships B "Hardware & engineering" among 11 industries; design documentation, specifications, test reports; AutoCAD among sources no minimum (Data Partnerships page) vs 20+ full-time employees and 3+ years (license and referral pages) joinhandshake.com/ai/data-partnerships
Labelbox Prism B "CAD" among the systems named no size rule stated prism.labelbox.com
Mercor Hardware Engineering Company listing B CAD assemblies and drawings, circuit designs, simulation and test files included; PCB designs and Gerber files, firmware, FEA and CFD files and measured test results nice to have; designs the company owns, not customer IP 20 to 2,000 employees Mercor listings feed, hardware
Mercor Semiconductor & Materials Company listing B nice to have "Chip or device designs with their verification and test results"; licensed third-party IP not a fit 10 to 2,000 employees Mercor listings feed, semiconductor

B = buyer or licensee program. "Not stated" does not mean allowed.

Mercor's program page names eight target industries (legal, healthcare, finance and insurance, professional services, manufacturing, retail and e-commerce, real estate, logistics) and leaves out hardware and engineering, while its Hardware Engineering listing, published 2026-10-17, names circuit designs, PCB designs and Gerber files.

Mercor states USD 45,000 to 1,350,000 for that listing, "Depends on assembly count and completeness" (checked 2026-11-09), which is a claim and not an offer. Handshake AI's and Labelbox Prism's own figures sit with the other programs under payouts and program terms compared.

Customer Designs, Reference Designs and Licensed Parts Inside a Product File

A product file mixes the company's own design with customer designs, third-party parts and licensed code, and the buyer pages that name hardware ask for the company's own.

Mercor's Hardware listing requires "Designs the company owns, not customer IP" and lists "Designs owned by your customers" and "Single parts or parts catalogs" as not a fit (read 2026-11-17).

Mercor also names product design consultancies among its industries while excluding customer-owned designs, so a consultancy licenses only what it owns. Its scoping questions ask which CAD system and how many assemblies, whether the company or its customers own the designs, whether simulation or test results are kept, and which industries the products serve.

Customer NDAs add a duty on top of ownership. Under 18 U.S.C. 1839(5), misappropriation of a trade secret includes disclosure without consent by a person who knew it was acquired under a duty to maintain its secrecy.

The standard clauses of customer and contract-manufacturer agreements are not summarized here. Customer approval is covered under customer consent and confidentiality clauses, which set out what to review first. See customer consent and confidentiality clauses.

Three further layers sit inside a product file, and none is checked against published terms on this page:

  • licensed and open-source code inside firmware
  • component vendors' datasheets and reference designs received under NDA
  • CAD, EDA and simulation tool license terms over files made in them

Mercor's Semiconductor & Materials listing states licensed third-party IP as not a fit (read 2026-11-17). The same test applies to a product file, and parts and code the company only licenses fall under company data that cannot be licensed.

Unreleased Products and Irrevocable Licenses: What a Design License Puts at Stake

An unreleased design is valuable because competitors do not have it, and a license to an AI buyer changes who holds a copy of it. Under 18 U.S.C. 1839(3), a trade secret rests on reasonable measures to keep the information secret and on independent economic value from not being generally known.

License terms decide what happens to that secrecy. micro1's Data License Master Terms, last updated 2026-11-12 and read 2026-11-17, state a worldwide, nonexclusive, irrevocable, perpetual license that may be sublicensed through multiple tiers (s.1.2), and no duty to delete or retrain Licensee Materials (s.4.4).

Labelbox Prism states that its license is exclusive by default, that a kill clause forces deletion within 30 days and that "Models already trained on the data cannot be unlearned" (checked 2026-11-09). A design that reaches a model therefore stays there.

The US, EU, UK and Japanese conditions are compared under trade secrets and confidential information in AI data licensing.

Defense, Drone and Dual-Use Product Lines: When a Design File Needs Authorization

Drawings, test information and related software for defense articles are ITAR technical data, so a company that makes aerospace, drone or robotics products starts its export check before it scopes a license.

Mercor's Hardware listing names aerospace, robotics, EV and drone makers among its industries and states automotive, aerospace, robotics and industrial equipment as the priority (read 2026-11-17).

Under 22 CFR 120.31(a)(1), a defense article includes technical data recorded or stored in any physical form, and models or mockups that reveal it.

Under 120.33(a)(1), technical data is information required for design, development, production, manufacture, assembly, operation, repair, testing, maintenance or modification of defense articles, including blueprints and drawings, and (a)(4) adds software directly related to defense articles.

Section 120.33(b) excludes general system descriptions and public domain information. Under 120.34(a)(5), information available through patents at any patent office is public domain, and an unreleased design is not published (eCFR text as of 2026-11-13, read 2026-11-17).

Releasing technical data to a foreign person in the United States is an export under 22 CFR 120.50(a)(2), and technology subject to the EAR released to a foreign person in the US is a deemed export under 15 CFR 734.13(b). micro1's s.5.7(g) has the licensor represent and warrant that the Data contains no export-controlled, classified or ITAR or EAR restricted material unless an Order Form agrees otherwise, with remediation at no cost to the licensee (terms updated 2026-11-12).

No export classification of any product or file is stated here. The rules are set out under export controls on technical data.

Benefits, Risks, Downsides and Alternatives for a Hardware Company

Licensing can earn income from designs and test records a hardware company already keeps, but customer terms, unreleased-product secrecy and export rules limit what can go, and not licensing is a valid outcome.

Benefits

  • Buyers name these records on their own pages: designs, circuit boards, simulation files and test reports (checked 2026-11-09, Mercor re-read 2026-11-17).
  • The company's own designs across several product generations are what Mercor's Hardware listing asks for.
  • A nonexclusive grant, as in micro1's s.1.2, leaves the company free to keep using its designs.

Risks

  • Breach of customer secrecy duties, since 18 U.S.C. 1839(5) reaches disclosure under a duty of secrecy.
  • Release of ITAR technical data or controlled technology to a foreign person, an export or deemed export.
  • Designs absorbed by a model cannot be unlearned, as Labelbox Prism states.
  • Security incidents at buyers: the California Attorney General report on Mercor lists unauthorized access through compromised LiteLLM versions, with breach dates 2026-03-24 and 2026-03-30.

Downsides

  • An exclusive license by default at Labelbox Prism.
  • An irrevocable, perpetual license at micro1.
  • Scoping work to separate customer, third-party and controlled files before any offer.
  • No price per file or per board on record.

Alternatives

Where Hardware Licensing Meets Engineering Firms, Manufacturers, Chip Makers and the Seller Path

Hardware companies share design files with engineering firms, shop-floor records with manufacturers and chip designs with semiconductor companies, and the industry index sets out what limits each sector.

The index of data licensing by industry covers engineering and architecture firms licensing data with the building-side designs, manufacturers licensing industrial data with the shop-floor records, and semiconductor companies licensing process data with the chip-side records. Pages on automotive companies licensing data and energy and utility companies licensing data follow.

Firmware is source code, covered under selling or licensing source code. Device logs are sensor, IoT and telemetry data, and robot makers also produce robotics data for AI training. The full map of AI training data law by jurisdiction sits beside them.

  1. Check data sale readiness.
  2. List the design vault in a data inventory for an AI data sale.
  3. Sign NDAs before sharing data with an AI buyer.
  4. Work through choosing a buyer for your data.
  5. Negotiate the clauses of AI data licensing agreements.

This page is information, not legal advice or an export classification.

Buyer Pages Named on This Page

Each buyer above has its own page with dates and sources.

Frequently Asked Questions

Can a hardware company license circuit board designs to AI companies?

Mercor's Hardware Engineering listing names circuit designs, PCB designs and Gerber files, for designs the company owns and not customer IP. It lists Altium and KiCad among its tools (feed read 2026-11-17).

How much do AI companies pay hardware companies for CAD and test data?

No price per file or per board is on record. Mercor states USD 45,000 to 1,350,000 for its Hardware Engineering listing, depending on assembly count and completeness (feed read 2026-11-17), a claim and not an offer. The wider picture is under what company data is worth to AI companies.

Is a hardware design file an export?

Releasing it to a foreign person can be, if it is ITAR technical data or technology subject to the EAR. Release in the US is an export under 22 CFR 120.50(a)(2) or a deemed export under 15 CFR 734.13(b); whether authorization is needed depends on classification.

Can a contract design firm license the designs it made for customers?

Not without the customer's agreement. Mercor lists designs owned by customers as not a fit (read 2026-11-17).