Today
Firmware often contains hundreds of open-source components, and their license terms are rarely checked in full. A missing attribution or a copyleft component inside your own code can lead to injunction claims or to the duty to disclose source code. License notices for device and manual are put together by hand shortly before release and are outdated by the next update.
An example
Wallner+Hardt Sensortechnik is preparing the release of firmware 4.0 for its controller with a web interface. The agent reads the software bill of materials with 412 components and finds nine without a recognizable license, a library under GPL-3.0 linked into proprietary application code, and the Linux kernel under GPL-2.0 with no source code offer. It builds the license notice with copyright notices and license texts for the web interface and the manual. Development replaces the GPL-3.0 library with one under Apache-2.0, and the legal department releases the notice.
Your data, wherever it lives
Which components a firmware contains sits today in software bills of materials from the build, in folders on the file server and in development's component database; which firmware runs on which product sits in the PLM; approvals for third-party software in the wiki, manuals and earlier license notices in the DMS. demi reads, understands and links it all per version, with your rights. The AI checks a firmware in minutes instead of days, and the responsible person decides on every conflict.
Where the data lives today
- PLM
- Folders & drives
- Databases
- DMS & archive
- Wiki & intranet
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
Data sources in this case: development tools, PLM, file share, wiki and DMS. demi replaces nothing and links each firmware version's software bill of materials, with component, version, license and copyright notices, to the products and variants it runs on and to manual and license notice. Every component knows which versions and products it is in.
- 2 · PermitPermission Layer
Development, product management and the legal department see software bills of materials and findings. The named responsible person releases exceptions to the license policy, the legal department the license notice, and every release is recorded.
- 3 · ActIntelligence Layer
The agent reads bills of materials in formats such as SPDX or CycloneDX, checks each declared license against the license text actually found and against your license policy: allowed, allowed with conditions, forbidden. For each distribution channel it derives the duties, from attribution to a source code offer. It flags components without a recognizable license as open, never as free.
How it runs
- 1
With every build, demi reads the software bill of materials of the new firmware version.
- 2
The agent determines license and copyright notices per component and checks them against the license text.
- 3
It checks each license against your policy and flags conflicts, unknown licenses and new components.
- 4
It builds the license notice for device and manual and, where required, the offer for the source code.
- 5
Development resolves conflicts, the responsible person releases the version and the legal department the notice.
What changes
Every firmware shipped with a complete license notice
License conflicts caught before release, not after a legal claim
License duties per product and version at a glance
What does it bring you?
Check it with your own numbers
Every starting value is an assumption you can change. The calculation sits right below, step by step.
Your numbers
Result
+173 hfreed per year
Assumptions and calculation
demi checks the licenses of every firmware and builds the notice; you decide on conflicts.
8 h → 5.6 h per case
How we calculate
6 firmware releases × 8 h × 30% × 1.0 (manual) × 12 months = 173 h
Value per year, before demi costs
Freed per year+173 h
Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.
= Value per year, before demi costs
+$11,245
gained per year
173 h ÷ 1,760 h per role = 0.1 full-time roles
An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.
Combine with more cases and get the packageQuestions about this use case
Where does the software bill of materials come from?
From your build process, for example as an SPDX or CycloneDX file, or from your development's component lists. If neither exists, demi builds it from dependency files and license scan results. The same bill of materials also serves the technical file under the Cyber Resilience Act.
Does the AI decide whether a license is allowed?
No. Your license policy sets which licenses are allowed, allowed with conditions or forbidden. The agent applies it and shows every deviation with its location, and an authorized person releases exceptions. Legal questions are settled by your legal department.
What happens to components without a recognizable license?
They count as open, never as free to use. The agent shows where the component comes from and where it is included, and drafts the query to the supplier or the project. Until it is resolved, it stays on the version as a finding.
How do the license notices reach the customer?
In the form you set: as a file on the device, as a page in the web interface or as an appendix to the manual. With every new version the agent updates them and shows what changed before the legal department releases them.
