Can a semiconductor or electronics company license its design data to AI?
Part of it, yes. A design folder holds two piles: the work the company’s own team wrote, and files that belong to a foundry, a supplier or a customer. The first pile can be considered. The second cannot be licensed, and neither can anything an export rule controls.
What a chip or electronics company has that is licensable
| Schematics and board layouts | The company’s own circuit drawings and layouts, from first draft to the released revision. |
| Chip design code | Hardware description code written in house, with its history of changes, so the reasoning behind each revision is visible. |
| Verification runs and test benches | The tests written to check a design, what failed and how it was fixed. |
| Design review notes | Written comments from the people who reviewed a design before release, which show what was questioned and why. |
| Bug history and bring-up logs | What went wrong when the first real boards arrived and how the team traced it. Public code almost never shows this part. |
Two piles in one folder
Most owners assume a design folder is too secret to license, and some of it is. But the folder is not one pile. One part is work the company’s employees wrote. The other part is material that came from outside: a foundry’s design kit, a block licensed from another company, or a design made for a customer. The first can be listed. The second follows the terms it arrived under.
Who owns a design file
Work an employee did on the job usually belongs to the company. A contractor is different, because in the United States the company may not own that work unless a signed written agreement says so. A design built for a customer may belong to that customer, and a chip layout has its own protection in the United States, so someone confirms who holds it. Counsel checks each of these before a file is listed.
Export rules cover information too
In the United States, export controls apply to technical information and not only to things that are shipped, and development work before serial production is within their reach. Whether a given file is controlled depends on the chip and where it would be used, so export counsel reviews the list before anything leaves the company. Until that review is done, those files are left out.
Old secrets in old code
Passwords and keys have a habit of hiding in design code and scripts. The whole history of a folder is checked, not only the newest copy, because an old revision can still hold a login that works. The cleaned sample is shown to the company’s team for approval before it moves.
What cannot be licensed from a chip or electronics company
| Foundry design kits | These usually sit under a nondisclosure agreement with the supplier, so they are not the company’s to give. |
| Licensed blocks from other companies | A block bought or licensed from another firm has its own terms, which usually bar passing it on. |
| Designs made for a customer | A design built for a customer follows that customer’s contract and is left out unless the customer agrees. |
| Export-controlled technical data | Files covered by export rules stay out until export counsel has cleared them. |
How a sample might be chosen
Consider a company of 60 people that designs sensor boards. Most of its work sits on its own boards, with one customer design and a foundry kit in the same folder. The team lists the schematics, layouts, control code and review notes for the in-house boards, leaves out the kit and the customer design, and asks counsel about export status. The de-identified sample is one finished board, from schematic to bring-up log, with staff and customer names replaced by labels such as Employee 14 and Customer 3, and a test login blacked out. The head of engineering approves it before anyone outside sees it.
Questions owners ask about this
Is chip design data too sensitive to license at all?
Some of it is, and that part stays in the company. The files the team wrote itself, without supplier or customer terms attached, can be considered once ownership and export status are checked.
What if most of our work is on a customer’s design?
Then there may be little left to license, and it is better to know that early. The decision rests with the customer’s contract.
Do review notes matter more than the designs?
Often they are the part that is not available elsewhere. A finished design shows how it ended. The notes and the bug history show how it was reached.
Who decides whether a file is export controlled?
Export counsel does, looking at the chip, its use and its destination. That review happens before any file is listed.
Didn't find your question? Ask us directly.
Keep reading
Records to look at first
- Project and task history: Jira, Asana, Linear, Monday, Trello, ClickUp and Airtable comments and status changes, not task titles.
- Code and pull request history: The commit, the review and the failed fix before the working one, with secrets and borrowed code removed.
- CAD and engineering files: The design with its feature history, its simulation and its test, with customer designs and catalog parts left out.
Other industries
- Manufacturers: A job tied to its setup, its machine readings and its inspection result, with customer designs kept out.