Frequently asked questions
Short answers, with links to the guide that covers each topic in depth.
Related reading: what open-source hardware is, choosing a license and OSHWA certification explained.
The basics
What is open-source hardware?
Hardware whose design files are published so that anyone can study, modify, distribute, make and sell the design or hardware based on it. The community definition, hosted by the Open Source Hardware Association, lists twelve criteria. Our guide "What open-source hardware is" walks through them.
Does open hardware have to be free?
No. The design is open; the physical product can be sold at any price. Most open hardware companies earn their living by selling assembled, tested units, kits and support.
Is a published schematic enough?
Usually not. A PDF schematic helps with repair, but the definition asks for design files in the format you'd use to change them, such as the native EDA project and the PCB layout, plus a license that allows making and selling.
Which files should I publish?
Native design files and exports such as Gerbers and PDFs, a bill of materials, mechanical CAD, firmware source, assembly and user documentation, and license files. The publishing guide has a repository layout you can copy.
Licenses
Which license should I use?
It depends mainly on whether you want derivatives to stay open. CERN-OHL-S v2 keeps them open, CERN-OHL-W v2 keeps your part open while allowing closed additions, and CERN-OHL-P v2 or Solderpad allow anything with attribution. The license chooser on the homepage asks the deciding questions.
Can I use the GPL or a Creative Commons license for hardware?
People do, and it's better than no license. These licenses weren't written for physical products, though, and don't deal well with manufacturing or patents. A hardware license is a better fit for design files, with Creative Commons for documentation and a software license for firmware.
Can I use a non-commercial license?
You can, but the result isn't open-source hardware, because the definition requires that anyone may make and sell the design. NC and ND licenses also don't qualify for OSHWA certification.
Does an open license stop someone from copying my product?
No. Copying the design is exactly what an open license allows. What it doesn't allow is using your trademark, and reciprocal licenses require copies with changes to be published. The business models guide covers living with clones.
Certification
Do I need certification to call my project open-source hardware?
No. A project that meets the definition is open-source hardware either way. OSHWA's certification is an optional, free program that lets you show a logo and a unique ID.
What does the OSHWA logo mean on a product?
That the creator has registered the project with the Open Source Hardware Association and agreed that it meets the definition. It's not a safety, quality or regulatory mark.
Does Open-Hardware.org certify products?
No. This site is an independent guide. It doesn't certify, test or endorse products and doesn't represent OSHWA or any other organization.
About this site
Who writes these guides?
The Open-Hardware.org Team. The site was relaunched in 2026 under new, independent management and has no connection to earlier owners of the domain.
Is anything here legal advice?
No. The guides and the chooser explain licenses in plain words to help you narrow your options. For a decision involving a company, a grant or patents, ask a lawyer.
How do I report a mistake?
Email contact@open-hardware.org with the page and the correction, ideally with a link to the source.