Commercial Licensing FAQ

Is the repository dual-licensed GPL or commercial by default?

No. The public community edition is licensed under GPL-3.0-or-later. Commercial rights require a separate negotiated and executed agreement.

Does COMMERCIAL-LICENSE.md grant proprietary rights?

No. It is an invitation to discuss terms and grants no additional rights by itself.

Why offer a commercial path?

Organizations may need proprietary integration, OEM or white-label redistribution, private branches, contractual support, warranty, training, or engineering services that are not provided by the public GPL grant.

What can a commercial agreement cover?

Only rights controlled by the relevant copyright holder. Third-party dependencies, contributor-owned material, standards, and historical grants remain subject to their applicable terms.

Do historical Apache rights disappear?

No. Revisions up to and including 9440f08b6909ef2dc93dd483cfdcb4e1e86077d0 retain their historical Apache-2.0 grants on archive/apache-2.0-final. Later community revisions and current release binaries are not offered as an Apache-or-GPL choice.

Does a commercial agreement certify the product?

Not automatically. Licensing, support, warranty, validation, conformance assessment, calibration, functional safety, cybersecurity approval, and engineering acceptance are separate contractual and technical subjects.