Updated
For chip and materials teams
Sell Semiconductor Data to AI Companies
Short answer
Often, yes, as a license, if you own the records. Some programs ask for 1,000+ runs that link recipes to measured results, with failed builds kept. Data owned by a customer or foundry stays out. Export rules can stop a deal, so ask your lawyer first.
To sell semiconductor data to AI companies, you sign a license on copied run records. The most useful ones tie each recipe to a measured result. A recipe is the set of settings a tool follows. Think of a license as permission to use a copy. Your company still owns the records.
This page is for chip makers, device makers and materials companies. We cover what programs want, which teams fall short and how export rules come in. We are a data agency, so we match you with programs and explain each fit. We bill your company nothing. Programs pay DillisData a referral fee.
- Failed runs count
- Foundry data stays out
- We never hold records
What programs want
What do AI companies look for in semiconductor companies?
No two programs match, and their lists change. Some ask for 10 to 2,000 employees and several years of runs. The first four rows below are the core of that ask. Other rows can add value.
| What some programs ask for | Where it tends to live | Why they want it |
|---|---|---|
| Run or build records you own, with settings linked to measured performance | Opcenter Execution Semiconductor or another MES, process databases | Cause and effect. This setting led to that result. |
| 1,000+ runs, builds, wafers or experiments | Fab databases, lab folders, test files | One run is an anecdote. Many runs show a pattern. |
| Every build kept, failed ones included, with dates | Lot history, lab notebooks, archive drives | Failures teach what doesn't work |
| Data that hasn't been published | Internal reports, process files | A public result is one a lab can already read |
| Lab notebooks with notes on why builds failed | Paper or electronic notebooks, engineer write-ups | Shows how a trained person reasons about a bad result |
| The same recipe built again on different days | Lot history, tool records | Shows how much a process drifts when nothing should change |
| Measurements under more than one condition | Test files, JMP projects | Shows how a part behaves at other temperatures or loads |
| Yield, metrology and equipment logs | Exensio, tool logs sent over SEMI GEM | Yield is the share of good parts. Metrology is exact measuring. |
| Chip or device designs with verification and test results | Fusion Compiler, VCS and similar design tools | Links a design to proof of whether it worked |
Honest filter
Who is not a fit?
Ownership decides most of this. If these lines describe your records, a program will likely pass. Better to learn that today.
Data owned by a customer or foundry partner
If you ran the wafers for a customer, the results may be theirs. If a foundry gave you process files under contract, those may not be yours either. Read those deals first.
Published papers and datasheets only
Anyone can already read these. Some programs want the runs behind the paper, not the paper.
Licensed third-party IP
Design blocks, libraries and tools you pay for belong to their vendors. A run or design that leans on them needs care. Your lawyer can say what can be split out.
Defense and export-controlled work
The programs we track generally say no to this. In this field, it can reach much further than you might guess, so read the next section.
Runs with no results attached
Settings with no measured outcome miss what some programs ask for. If recipes and test data can't be linked, be upfront about that with any program.
The usual general limits
Some general programs want about 50 desk staff, with 5+ daily systems and three or more years on file. They also want a base in Australia, the EU, the US or Canada. English is usually expected.
Count your runs, then get a number
The quiz takes 2 minutes. It asks about your company and systems. It never asks for a recipe, a wafer map or a file.
Rights and rules
Do export rules or foundry contracts block this?
They can. This field has real legal limits. We are not lawyers, and none of this is legal advice. Your export lead and your lawyer belong in this before you sign.
Export rules on chip technology
The Commerce Department's list of controlled items has a category just for electronics. Listed items get a code. BIS, the agency in charge, explains how to classify yours. Know the code before any process data leaves your systems.
Sharing inside the US can count
Under the export rules, releasing controlled technology to a foreign person in the US has a name: a deemed export. It is treated as going to that person's home country. A program's staff may come from many places. BIS says a license may be needed first.
Defense parts
If any work falls under ITAR, the US rules for defense goods, keep it out. Its technical data includes drawings, plans and instructions for those goods.
Chip layouts have their own protection
A mask work is the layered pattern of a chip. Federal law protects it apart from copyright. The owner is generally the creator, or the employer for work made on the job. So a customer's layout may not be yours to license, even if you built it.
Your own trade secrets
Recipes are often a company's main edge. Trade secret law depends on reasonable steps to keep them secret. So your lawyer should read how a program stores, limits and shares what it gets. You can also leave your newest process nodes out.
People's details in lab records
Notebooks and logs name engineers and operators. Programs say they scrub personal details, though no method is perfect. HR files and medical notes should stay out.
Value
What makes one fab's records worth more?
AI data programs typically pay chip and materials firms $100K to $5M+, largely depending on each company's size. No one can promise that. Use the estimate for a number. Past size, depth matters.
Clean links from recipe to result
This is the heart of it. A run with its settings, tool, date and result is worth far more than loose facts in four places.
A complete record, bad days included
Keep every build. A data set with only good lots hides what causes failure. If you have thrown out scrap records, say so up front.
Why people thought it failed
An engineer's note on a bad lot is rare. Numbers show what happened. The note shows how a person reasoned through it.
Years of history and more systems
Several years of runs help. Leaving systems out lowers an offer, so hold that cost against what each exclusion protects.
How it works
How does a license work for a chip company?
If you came here to learn how to sell data to AI companies, note the word license. You keep your records and permit use of a copy.
Take the quiz
Answer questions on size, years of records, systems and location. No recipes, no files, no logins.
2 minutesReview 3 programs that fit
Your answers get tested against program rules and posted prices. You see your estimate and the reasons behind each match.
Clear it inside your company
Your export lead screens the data. Your lawyer reads customer and foundry deals, plus the program's terms. You pick what stays out, then sign with the program directly.
Your team sends the copy
We do not take custody of records. The transfer runs only between you and the program. The program strips personal details, then pays you as its terms say.
Public reports
The public record so far
We found no public price for a chip or materials company. These reports are the nearest proof that records carry value. None is a DillisData deal.
Spirit Airlines' internal records drew this winning bid from Google at a bankruptcy auction. Court approval was still pending on Nov 5, 2026.
WIS/InvestigateTV, Nov 2026What Alphabet, Amazon, Microsoft and Meta planned for 2026 capital spending, as of April. It shows AI demand, but it goes mostly to chips and data centers, not data.
Sherwood News, Apr 2026Labs want real records for training agents, says one report. It adds that no company has published tests of how much real data helps. Treat this as a live bet.
MIT Technology Review, Oct 2026Timing
The plain case for checking now
We can't name a deadline. Three plain reasons still make it worth a look.
Scarce data draws the interest
Run records with failures kept are hard to find. If a rival lab already holds something close, there can be less demand for yours.
The market may shift
Nobody knows how long today's prices hold. Labs may gather enough, or train some other way.
Old lots vanish
Fab systems get replaced, and old tool logs get purged to save space. Before you delete an archive, find out if anyone would pay to use it.
Is your run history worth a legal review?
Find out before anyone starts on export screening. The quiz is free, and it asks for nothing you would need to clear.
Questions
Questions owners ask
We are fabless. Do our records count?
They might. Your designs, verification and test results can be yours. Foundry process files and third-party design blocks usually are not. Read your foundry and vendor deals, and ask your lawyer what can be separated.
We make materials, not chips. Is this page for us?
Yes, if you hold run records you own. Some programs treat materials the same way, with the recipe tied to a measured result. The same rules on failed runs and publishing apply.
We already published some of this. Does it all fall out?
The published part may not count, since some programs want data that hasn't been published. The full run history behind a paper can be different. Be open with the program about what is already public.
Why would anyone want our failed builds?
A model that only sees wins can't learn what causes a loss. So some programs ask you to keep every build, failed ones included, with dates. Scrap records that look useless to you may be what they want.
We do some government work. Are we out?
Not always, but expect a close look. Defense and export-controlled work is not a fit, so that part must stay out. Ask your export lead if the rest can truly be split from it. Some programs may still say no.
Could a rival learn our process?
That is a fair worry. What goes in is your call, and the contract sets the limits. Read each program's terms on who can see your records. If a recipe is your edge, leave it out and accept a lower offer.
Does DillisData ever see our run data?
No. We work from your quiz answers and never receive a record. You and the program handle the signing and the transfer.
Your estimate
See what your run history could earn
The quiz gives you a figure from posted program pricing, and it is no offer. Take it to your export lead and your lawyer, then decide.
No files, no recipes, no charge from us