License¶
Overview¶
This project uses a dual-license model for hardware and software components.
The goal of this licensing structure is to:
- Allow free and open community usage
- Preserve open-source and open-hardware improvements
- Support commercial adoption
- Provide proprietary licensing options for organizations that require closed-source usage
Hardware Licensing¶
The hardware components of this project are licensed under either:
- CERN Open Hardware Licence Version 2 — Strongly Reciprocal (CERN-OHL-S-2.0) for open hardware use
- A separate KuoQuo Hardware Commercial License for proprietary or closed-source hardware usage
This applies to, but is not limited to:
- schematics
- PCB layouts
- fabrication files
- Gerber files
- CAD models
- enclosure designs
- mechanical designs
- BOMs
- manufacturing documentation
- assembly files
Hardware License Option A — Open Hardware License¶
We recommend using the CERN Open Hardware Licence Version 2 — Strongly Reciprocal (CERN-OHL-S-2.0).
Why CERN-OHL-S-2.0?¶
CERN-OHL-S-2.0 is an established copyleft hardware license specifically designed for open-source hardware projects.
It requires users who modify and distribute hardware designs or manufactured derivatives to provide corresponding design source files under the same license.
This means:
- Personal use: allowed
- Educational use: allowed
- Research use: allowed
- Commercial manufacturing: allowed if derivative hardware designs remain open under CERN-OHL-S-2.0
- Distribution of modified hardware: corresponding design files sharing required
CERN-OHL-S-2.0 Requirements¶
If you distribute modified hardware designs or manufactured derivatives:
- modified design files must remain under CERN-OHL-S-2.0
- corresponding design sources must be provided
- attribution and license notices must be preserved
- derivative hardware documentation must remain open
CERN Open Hardware Licence Version 2
Hardware License Option B — Commercial Proprietary Hardware License¶
Organizations that want to:
- keep hardware modifications closed source
- manufacture proprietary derivative hardware
- distribute hardware without CERN-OHL reciprocal obligations
- integrate designs into closed commercial products
- avoid disclosure of manufacturing or design changes
must obtain a separate KuoQuo Hardware Commercial License from KuoQuo.
Commercial Hardware License Includes¶
- Closed-source hardware usage rights
- Proprietary manufacturing rights
- OEM / white-label rights (optional)
- Redistribution rights (optional)
- Custom negotiated terms
- Priority engineering support (optional)
KuoQuo Hardware Commercial License
Software Licensing¶
The software components of this project are licensed under either:
- GNU Affero General Public License v3.0 (AGPLv3) for open/community use
- A separate Commercial Proprietary License for closed-source or proprietary usage
This applies to, but is not limited to:
- firmware
- backend services
- frontend applications
- SDKs and APIs
- automation scripts
- AI integrations
- embedded software
- tooling and utilities
Software License Option A — Community / Open Use License¶
We recommend using the GNU Affero General Public License v3.0 (AGPLv3).
Why AGPLv3?¶
AGPLv3 is an established copyleft license that requires users who modify and deploy the software over a network to provide source code of their modified version.
This means:
- Personal use: allowed
- Educational use: allowed
- Research use: allowed
- Commercial use: allowed if the deployed derivative work is open source under AGPLv3
- SaaS / hosted use: source code sharing required for modified versions
AGPLv3 Requirements¶
If you distribute or deploy modified versions of the software:
- modified source code must be made available
- derivative works must remain under AGPLv3
- copyright and license notices must be preserved
- network-accessible deployments must provide source access
GNU Affero General Public License v3.0
Software License Option B — Commercial Proprietary License¶
Organizations that want to:
- keep modifications closed source
- embed into proprietary products
- distribute without AGPL obligations
- use internally without copyleft disclosure risk
- integrate into commercial SaaS platforms without source disclosure
must obtain a separate Commercial License Agreement from KuoQuo.
Commercial Software License Includes¶
- Closed-source usage rights
- Proprietary deployment rights
- OEM / white-label rights (optional)
- Redistribution rights (optional)
- Priority support (optional)
- Custom negotiated terms
KuoQuo Commercial Software License
Practical Summary¶
| Use Case | AGPLv3 Software | CERN-OHL-S-2.0 Hardware | Requires Commercial License |
|---|---|---|---|
| Hobby / Personal Use | |||
| Student / Research Use | |||
| Open-source startup product | |||
| Commercial manufacturing with open mods | |||
| SaaS with private backend modifications | N/A | ||
| Proprietary enterprise integration | |||
| Closed-source hardware derivative | N/A | ||
| Proprietary firmware distribution | N/A | ||
| Closed-source consumer hardware product |
Disclaimer¶
This software, hardware designs, documentation, and related materials are provided "as is" without warranty of any kind, either express or implied.
To the maximum extent permitted by applicable law, KuoQuo and its contributors disclaim all warranties, including but not limited to:
- merchantability
- fitness for a particular purpose
- non-infringement
- accuracy or completeness of results
- manufacturability or production suitability
- reliability
- security
- regulatory compliance
In no event shall KuoQuo or its contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages, including but not limited to:
- loss of data
- loss of profits
- hardware failure
- manufacturing defects
- device malfunction
- regulatory non-compliance
- personal injury
- business interruption
- cybersecurity incidents
- certification failure
- product recalls
arising from the use of, inability to use, manufacture of, or distribution of this project and related materials, even if advised of the possibility of such damages.
Users assume full responsibility for all risks associated with:
- use
- manufacturing
- testing
- deployment
- certification
- regulatory approval
- integration into products or systems
- safety validation
- production and distribution