Practical Answer - AI Hardware Supplier Control

Who Owns Firmware or Embedded Software Developed by a Chinese Supplier?

Last updated: July 2026

Paying for development work does not automatically answer who owns the firmware, who can reuse it, or who must deliver the source code.

In short

Firmware ownership depends on the written agreement, development records, invoices, purchase orders, and actual project facts. A founder should not assume that paying a Chinese supplier automatically transfers source code, embedded software, test scripts, drivers, or improvements.

The Direct Answer

Agree ownership, license rights, delivery format, reuse restrictions, improvements, escrow or repository access, and handoff obligations before development begins. Otherwise the supplier may argue that the firmware is its own reusable development asset.

Where Ownership Gaps Appear

Firmware often sits between engineering service, manufacturing enablement, and product IP. A supplier may write board-support code, modify sample code, integrate a camera module, adapt Bluetooth firmware, or create production test scripts.

If the contract only says prototype fee or engineering fee, it may not clearly transfer the code, restrict reuse, or require source-code delivery.

Define customer-owned code, supplier background code, third-party code, and project-specific improvements.

State whether source code, build files, test scripts, and documentation must be delivered.

Restrict reuse for other customers, sister factories, subcontractors, or supplier-branded products.

Align development agreement, invoice, PO, and NNN language.

Why a Development Agreement May Be Needed

A China NNN may protect early disclosure, but firmware development usually needs development or OEM terms. See /services/nnn-manufacturing-agreements-china/ for agreement structure and /services/ai-hardware-supplier-control-package-china/ for AI hardware technical asset control.

The goal is not only confidentiality. The goal is to make manufacturing portable if the founder later changes supplier, adds a second manufacturer, or brings firmware work back in-house.

Get Help

Request a Supplier Control Review

We review the supplier path, technical assets, agreement gaps, access boundaries, and handoff risks before deeper China prototype or OEM work.

Supplier Control Package Supplier Readiness Review

Frequently Asked Questions

Does paying a Chinese supplier mean I own the firmware?

Not necessarily. Payment is relevant, but ownership and delivery depend on the agreement, invoice, purchase order, development records, and the way background code and project code are defined.

Should the supplier deliver source code?

If manufacturing portability depends on the firmware, the agreement should specify whether source code, build files, test scripts, and related documentation must be delivered and when.

Can the supplier reuse firmware for other customers?

That should be addressed in writing. The agreement should restrict unauthorized reuse of customer-funded project code, product-specific logic, test scripts, and improvements.

LinkedIn Newsletter