Updated
For product engineering teams
Sell Hardware Engineering Data to AI Companies
Short answer
Often, yes, as a license, when you own the designs. Some programs want full assemblies in native CAD across several products. PCB files, firmware, simulations and test results can add value. Designs your customers own stay out.
To sell hardware engineering data to AI companies, your company licenses copies of real product designs. Some programs look for full assemblies in native CAD, plus the circuit boards, firmware and test results behind them. Native means the original file from your CAD tool. You keep owning the designs, and a program gets permission to use a copy.
This page is for companies that design physical products. We are a data agency. We match you with AI data programs and explain why each one fits. There is no charge to you from DillisData, because a referral fee from the program is how we get paid. We never hold your files.
- Native CAD, not meshes
- Customer designs stay out
- No files sent to us
What programs want
What do AI companies look for in hardware engineering companies?
Program rules vary and shift over time. Some want 20 to 2,000 employees and several product generations. The top three rows are the main ask. Lower rows can raise value.
| What some programs ask for | Where it tends to live | Why they want it |
|---|---|---|
| Full multi-part assemblies in native CAD, with feature trees | SOLIDWORKS, Creo, NX, CATIA, Onshape | A feature tree records each step of a build. A mesh only shows the final shape. |
| Designs the company owns, not customer IP | Windchill, Teamcenter or your vault | A program can only license what you have the right to license |
| Several products or product generations | Your vault, archive drives, old project folders | Shows how designs change as a team learns |
| PCB designs and Gerber files | Altium Designer, KiCad, Gerber output | A PCB is a circuit board. Gerber files tell the factory how to build it. |
| Drawings and bills of materials | Your CAD tool and vault | Links a design to how it gets made and what it costs in parts |
| Firmware | GitHub or another code host | Firmware is the code inside a device. It ties the circuit to what the product does. |
| FEA and CFD simulation files | Ansys Mechanical, Ansys Fluent | FEA tests stress in software. CFD tests air and fluid flow. |
| Measured test results for designs | Lab reports, test rigs, spreadsheets | Shows if the design held up in the real world |
Honest filter
Who is not a fit?
A lot of engineering files look useful and still fall short. These are the usual reasons for a pass.
Single parts or parts catalogs
A bracket on its own shows little. Some programs want parts working together in an assembly. A catalog of standard parts has the same problem.
Designs owned by your customers
Contract engineering firms feel this most. If a client paid for the design and owns it, you can't license it without that client's written OK.
Exported meshes with no native files
If all you kept are meshes, the steps behind the shape are gone. Some programs ask for more than that.
Defense and export-controlled work
The programs we track generally refuse this. A product with both civil and military uses needs a look from your export lead too.
Limits in the general programs
Those want about 50 desk staff, three or more years on file and at least five daily systems. They also look for firms located in the US, Australia, Canada or the EU. Others may start at 20 or 30 full-time people. English records are the norm.
Get a number without sharing a single file
Take the 2-minute quiz. It asks about your company, not your designs. You never upload a part or log in to your vault.
Rights and rules
Do you own your CAD files and firmware?
Ownership is the main question here. Some programs ask for designs you own, and owning the files on your drive is not the same thing. We are not lawyers. Ask yours to check the points below.
Work by your own employees
The Copyright Office's Circular 30 says work an employee makes as part of the job is work made for hire. The employer is treated as the author and owner. So staff designs are often the cleanest.
Work by outside contractors
This is where gaps show up. Hired-out work is "made for hire" only in nine listed categories, and only with a signed agreement. A transfer of copyright also needs a signed writing. Without that paper, the contractor may still hold rights. Find those contracts now.
Customer and partner programs
Paid development deals, NDAs and supply contracts can each limit your rights. Some give the customer the design. Others just forbid sharing. Sort your projects by contract before you count them.
Open-source code and vendor libraries
Firmware often holds outside code. Chip vendors' libraries and open-source parts come with their own license terms. Those parts are not yours to license as your own. Have your lawyer or lead engineer map them first.
ITAR and the EAR
ITAR technical data includes drawings and plans for defense goods. Inside the US, showing it to a foreign person is treated as an export. Commerce's rules treat controlled technology in a similar way. Have your export lead screen every product line.
Designs you want to keep secret
Trade secret law turns on reasonable steps to keep information secret. Think about products still on sale, or still in development. Older generations may be a safer place to start. Your lawyer should read the program's limits on use.
Value
What makes one design archive worth more than another?
AI data programs typically pay hardware firms $100K to $5M+, largely depending on the firm's size. It is not a promise. The estimate puts a number on it. Assembly count and completeness also count.
The whole product, not just the CAD
The best case is one product with its assembly, board, firmware, simulation and test results. Each piece explains the others. Scattered files are harder to use.
More assemblies, more generations
Rev A and rev C of the same product show what a team changed and why. Keep old revisions, and keep the notes that explain them.
Test results tied to designs
Plenty of models exist. Far fewer come with proof of how they performed. A failed test report can be useful too.
What you decide to hold back
You choose the scope. Keep in mind that leaving systems out lowers an offer. Protect what truly needs it, and no more.
How it works
How does licensing work for an engineering team?
People often search how to sell data to AI companies. In practice you are giving permission to use a copy, not selling your designs.
Answer the quiz
Share your size, location, systems and years of records. No CAD files, part numbers or vault logins.
2 minutesLook over your matches
We line your answers up with program rules and posted prices. You see an estimate, and 3 programs with the case for each.
Sort out the rights
Your lawyer and export lead review contracts, contractor paper and the program's terms. You write down what stays out, then sign with your chosen program directly.
Your team exports
We do not take custody of your files. Whoever runs your vault sends the agreed copy to the program. It removes personal details and pays you under its terms.
Public reports
Public reports so far
We found no public price for a hardware design archive. These reports cover other kinds of records. None involved DillisData.
A bankruptcy court auction of internal Spirit Airlines records ended with this Google bid winning. On Nov 5, 2026, the sale still lacked a judge's approval.
WIS/InvestigateTV, Nov 2026A captioning business that shut down says old work records earned it hundreds of thousands of dollars.
Fast Company via Slashdot, Apr 2026Companies still in business now get offers too, press reports say. Offers are not limited to startups that have closed down.
Business Insider via DNYUZ, Oct 2026Timing
The case for looking now
We won't invent a deadline. The real reasons to look are simple, and you can act on them or not.
What is rare today may not stay rare
Full native assemblies are hard to find on the open web. Demand can drop when a rival lab already has something similar.
Nobody can date the end
Labs may reach a point where they have enough, or they may change how they train. No one knows when that happens, or if it does.
Old vaults get lost
CAD licenses lapse, vaults get moved and old files stop opening. A product generation you can't open is one you can't license.
Find out if your archive is worth the legal review
Know the likely size of this before you pull old contracts. The figure comes from pricing that programs post, and it is no offer.
Questions
Questions owners ask
We only kept exported files or meshes for older products. Do those count?
They may count for little. Some programs ask for native CAD with feature trees, not only exported files. If you have native files for newer products, start there. Ask the program how it treats the older exports.
We are a contract engineering firm. Can we take part?
Only for work you own or have cleared. Client designs need that client's written OK. Your own internal products, tools and test fixtures may be a better place to start. Your lawyer can check each contract.
Do we need firmware and boards, or is CAD enough?
In the programs we track, native assemblies are the main ask. Boards, firmware, simulation and test results can add value beyond that. If you only do mechanical work, you can still check your estimate.
We have a mix of CAD tools from over the years. Is that a problem?
Not by itself. Teams switch tools all the time. What matters is that the native files still exist and can be opened. Have someone test a few old assemblies before you count them.
Our product is still on sale. Could this help a competitor?
It could be a risk, so treat it as one. You pick what goes in, and the contract sets limits on use. You could leave current products out. That can lower an offer, so weigh the two.
Does this include our patents?
A data license covers copies of your files. Whether it touches your patents depends on the wording. Ask your lawyer to check that it doesn't grant more than you meant to give.
Does DillisData look at our designs?
No. Our matching runs on your quiz answers. You sign with the program, and the files go between you and it. They never pass through us.
Your estimate
See what your product archive could earn
Answer a 2-minute quiz about your company. You get a number and 3 programs that fit. There is no obligation at any point.
No CAD files, no vault login, no charge from us