- Firmware is licensed today as part of a hardware archive, not on its own: no buyer publishes a firmware price.
- Vendor SDKs and HALs usually carry their own license; most cannot be passed to an AI buyer.
- GPL code in the tree changes what you can license; MIT and BSD code mostly does not.
- Source code for controlled items is controlled technology under the EAR, and releasing it can be a deemed export.
Can a hardware startup sell its firmware source code and test logs for AI training?
Yes, within limits set by who wrote each part of the code and what it controls. The table shows what buyers and sellers say in public about firmware and the rules that decide what can go into a license.
| Source or rule | What it says | Records affected | Stated terms or price | Date checked |
|---|---|---|---|---|
| Mercor hardware listing | Firmware is a nice-to-have for hardware companies | Firmware with the CAD and PCB designs it runs on | Published range $45K to $1.35M for the whole archive | 19 Nov 2026 |
| Hilco Global, Project Beacon | A closed company's firmware is sold inside its engineering lot | 202 firmware projects across 16 product programs, 11 with identified firmware | No price; NDA sale process | 19 Nov 2026 |
| Nordic Semiconductor SDK license | Software must only be used with Nordic chips; binaries may not be reverse engineered | Nordic SDK code and binaries inside your tree | Rule: exclude unless Nordic agrees | 19 Nov 2026 |
| GNU GPL version 3 | A conveyed modified work is licensed as a whole under the GPL | GPL components and code built on them | Rule: separate before licensing | 19 Nov 2026 |
| FreeRTOS kernel (MIT) | Permission to use, copy and sell copies, with the notice kept | FreeRTOS kernel files | Rule: keep the notice | 19 Nov 2026 |
| EAR (BIS) | Releasing controlled source code to a foreign person in the US is a deemed export | Firmware for items with an ECCN | Rule: classify first | 19 Nov 2026 |
Hilco describes the closed company's archive as "16 product programs, including 11 with identified firmware" (Hilco). No buyer has published a price for firmware on its own as of 19 November 2026. Firmware appears in public only as part of a larger hardware archive or as general source code. Test logs pair with the build they ran on; see EVT and DVT test reports.
Can we include vendor SDKs, HALs and RTOS code in a firmware license?
Mostly not the vendor's code, and this is the most common blocker in embedded trees. Chip vendors ship SDKs, drivers and hardware abstraction layers under their own licenses. Nordic's license is a clear example: "This software, with or without modification, must only be used with a Nordic Semiconductor ASA integrated circuit", and "Any software provided in binary form under this license must not be reverse engineered, decompiled, modified and/or disassembled" (Nordic SDK license). Training a model on that code is not using it with a Nordic chip, so leave it out unless Nordic agrees in writing.
Open RTOS kernels are often easier. The FreeRTOS kernel is MIT licensed: "Permission is hereby granted, free of charge, to any person obtaining a copy of this software" (FreeRTOS). Even so, you do not own it, it is public already, and a buyer gains little from it. The practical rule: license the code your engineers wrote, list every third-party directory, and exclude the rest.
Vendor code is often mixed into your own files, not kept in a separate folder. Engineers copy example projects, edit generated configuration files and patch drivers in place. A composition scan finds whole files, but it can miss pasted snippets, so ask the engineers who built each product where vendor code went. Where your changes sit inside a vendor file, the safe course is to exclude that file and describe the change in the documentation instead.
What happens if our firmware contains GPL or other open-source code?
It changes the license for the parts built on it. The GPL says "You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy" (GNU GPL v3). You cannot put GPL code, or your changes to it, under a private AI license with use limits. Separate it before you license, or license only the modules that do not depend on it.
Run a software composition scan over every repository and record the license of each directory. Permissive code (MIT, BSD, Apache) can usually stay in the tree with its notices, but it adds little value because it is public. The same steps apply to application code; selling source code for AI training covers ownership checks for repositories.
How do we license our PCB designs, schematics and Gerber files to AI companies together with the firmware?
As one linked record. Buyers value firmware most when it sits next to the board it runs on: the schematic, layout, BOM and the bring-up notes. Mercor's listing names "PCB designs and Gerber files" and firmware side by side as nice-to-haves, and the Project Beacon lot counts "193 PCB/schematic design projects, including 856 schematic sheets" beside its firmware. Keep the link visible: which firmware version shipped on which board revision.
Gerbers alone are a fabrication image; buyers want the editable source. The Altium and KiCad guide covers PCB ownership and export, and a posted budget of $5,000 to $10,000 for 100 or more KiCad projects shows the item price when boards are sold one by one (getFreelancer job post, November 2026).
Are there export control issues with licensing our firmware and engineering drawings to an AI company?
Yes, for some products. Firmware for a defense article is ITAR software, and the drawings around it are ITAR technical data, which "includes information in the form of blueprints, drawings, photographs, plans, instructions, or documentation" (22 CFR 120.33). Leave those programs out.
For commercial products, the question is the ECCN. Firmware for an EAR99 product usually needs no license; BIS says EAR99 items need one only for prohibited or restricted end users, end uses or destinations (BIS). Firmware for a controlled item, for example one with controlled encryption, is controlled source code, and BIS says "A deemed export refers to the sharing or release of controlled technology or source code to a foreign person within the United States" (BIS). Ask the buyer who will see the code. The ITAR and EAR checklist and the chip design guide cover classification.
Who owns firmware we wrote for a client?
Usually the client, if your contract assigns deliverables. Code your employees write for your own products belongs to your company as a work made for hire, "A work prepared by an employee within the scope of his or her employment" (U.S. Copyright Office). Code written for a client under a design services contract is usually assigned to that client. Shared libraries you built before the project, and kept the rights to, are often yours. Read each contract before a repository goes into scope.
Our hardware company is closing. Who would buy our CAD files, firmware and engineering records?
Hardware data programmes, which take firmware as part of an archive, and liquidators, who sell the archive as a lot. In Project Beacon the firmware sits inside "Proprietary engineering corpus spanning embedded software, electronics design, simulation and modeling, mechanical CAD, and dated engineering design history" (Hilco). Before you open-source anything at shutdown, read open source or sell the code: publishing removes most of what a buyer would pay for. The hardware startup shutdown guide covers who signs.
I am a liquidator. Can firmware and engineering archives be sold to AI companies as an asset of the estate?
Yes. Firmware, PCB projects, simulation models and CAD files can be estate assets, and a liquidator already markets one such archive as a counted lot. The checks are the same as for an operating company, done by the person in control: remove vendor SDK code and GPL code, drop customer-owned and export-controlled programs, and keep the repository history. Estate records for trustees and assignees covers how a records sale runs.
What should a hardware company check before signing a data license for its firmware, CAD files and test results?
Use this list on every repository before it goes into scope.
- Authorship: which code your staff wrote, which a contractor wrote, and which a client owns.
- Third-party code: vendor SDKs, HALs, RTOS and libraries, each with its license.
- Open source: GPL and other copyleft code separated from what you license.
- Export: the ECCN or EAR99 status of each product, and ITAR programs excluded.
- Secrets: keys, certificates and passwords removed from the code and its history.
- Terms: training use only, no resale, deletion at the end, an audit right, and payment timing.
This page is general information, not legal advice.
What makes a firmware archive more useful to an AI buyer?
A firmware archive is more than its latest source tree. What a model can learn from embedded code is how engineers made it work on real hardware: the bring-up fixes, the timing bugs, the workarounds for a chip erratum, the change that cut power draw. That story sits in the history and the links, not in the final files.
- Full version history with commit messages, not a zip of the last release.
- Build configurations and toolchain versions, so the code can be compiled as it shipped.
- The board revision and BOM each firmware version targeted.
- Issue tracker and code review threads linked to the commits that closed them.
- Bring-up notes, test logs and validation results for each release.
- A list of every third-party directory with its license, and what was removed.
Hilco's listing makes the same point from the seller's side: it describes "Related code, schematics, simulation, CAD and correspondence" as what sets the archive apart (Hilco). Secrets are the main risk in history: signing keys, device certificates, cloud credentials and test passwords. Scan the full history, not only the current tree, and rotate anything that was ever committed.
What is the first step for a company that wants to license its firmware?
List the repositories, the products and board revisions each one served, the years of history, and who wrote the code. Mark vendor SDKs, open-source directories, client code and export-controlled products. That list shows how much of the archive is yours to license. Firmware is usually worth more offered together with the PCB and CAD records; the hardware engineering data hub shows how buyers count them. 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.
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
Do AI companies buy old product design files and firmware from hardware companies that are closing down?
Yes, as part of an archive. A liquidator is selling a closed wireless-power company's 202 firmware projects together with its PCB, simulation and CAD files through an NDA sale process. No price is published. Keep the repository history and the link between each firmware version and the board it shipped on.
Can we license firmware built on a chip vendor's SDK?
You can license the code your engineers wrote, but usually not the vendor's SDK. Nordic's SDK license, for example, says the software must only be used with Nordic chips and that binaries must not be reverse engineered. Exclude vendor directories and binaries, or get the vendor's written agreement, before the code goes to a buyer.
Is firmware for an encryption product export controlled when licensed for AI training?
It can be. Source code for an item with an ECCN can be controlled technology, and BIS treats releasing controlled source code to a foreign person in the US as a deemed export. Classify the product first. If it is controlled, ask who at the buyer will see the code, or leave it out.
I am the lawyer for an embedded systems firm. Can it license its firmware archive, and what should the contract say?
It can license code it owns. The contract should list the repositories in scope, state that vendor SDKs, open-source code and client code are excluded, limit use to training, bar resale and sublicensing, require deletion at the end, and confirm the export classification. Ask the buyer to confirm who can access the code.
A buyer offered to license our firmware repositories for $25,000. What should we check before we sign?
No buyer has published a price for firmware alone, so check the terms more than the number. Confirm which repositories and years are in scope, whether the license is exclusive, whether the buyer may resell the code, and what happens to models at the end. Also ask whether the firmware is worth more licensed later with your CAD and PCB archive.
Does GPL code in our firmware stop us licensing the rest?
Not by itself. The GPL governs the GPL code and works built on it, which must be licensed as a whole under the GPL. Code that is separate and does not depend on it can be licensed on your own terms. Run a composition scan, separate the copyleft parts, and license only what you own outright.
Sources and further reading
- Mercor: Hardware Engineering Company listing (listing data, read November 19, 2026)
- Hilco Global: Project Beacon, wireless powering tech code and technical data assets
- Nordic Semiconductor: nRF Connect SDK license (LicenseRef-Nordic-5-Clause)
- GNU General Public License, version 3
- FreeRTOS Kernel: license file (MIT)
- eCFR: 22 CFR 120.33, technical data (ITAR)
- Bureau of Industry and Security: Deemed exports
- Bureau of Industry and Security: Classify your item (EAR99)
- U.S. Copyright Office: Circular 30, Works Made for Hire
