How the Open-Source Hardware Movement Extends Revision Principles to Physical Objects

Every manufactured object in the proprietary model is a closed revision loop. An engineering team designs a product, a company manufactures it, and a consumer purchases the output. The consumer can use the object but cannot legally or practically access its design. When the object breaks, the consumer is dependent on the manufacturer for repair. When the object fails to meet their needs, the consumer's only recourse is to purchase a different object. The knowledge embedded in the design is proprietary — it stays inside the company, or it is lost when the company discontinues the product or goes out of business.

This model has obvious advantages in the context of competitive market economies. Proprietary designs create incentives for investment in research and development. Companies that cannot capture value from their innovations have less reason to invest in creating them. Patents and trade secrets are intended to solve this problem by granting temporary monopolies in exchange for eventual disclosure.

The system has deep pathologies that become visible at civilizational scale. First, it directs revision capacity toward markets with purchasing power, leaving enormous categories of human need — appropriate technology for subsistence economies, medical devices for under-resourced health systems, scientific instruments for underfunded researchers — without iterative improvement. Second, it creates planned obsolescence as a feature rather than a bug: devices designed to be unrepairable concentrate repair profit in manufacturer-controlled service networks. Third, it causes knowledge extinction when companies fail or discontinue products, taking with them the accumulated design knowledge that would allow anyone else to maintain, repair, or improve the objects in circulation. Fourth, in critical infrastructure — medical devices, industrial equipment, communications hardware — proprietary control creates single points of failure and dependency that are security vulnerabilities at national scale.

Open-source hardware addresses all four pathologies by making the design itself a commons.

The conceptual foundation of open-source hardware comes directly from open-source software, which proved several counter-intuitive propositions about how revision works.

The first proposition is that transparency accelerates quality improvement. Proprietary software improves when its internal developers find and fix bugs. Open-source software improves when anyone who uses it and has the skill can find and fix bugs — a much larger and more diverse pool of attention. Linus's Law, named for Linux creator Linus Torvalds, states that "given enough eyeballs, all bugs are shallow." This is not universally true, but it describes a real phenomenon: many-eyes review catches errors that internal review misses.

The second proposition is that modularity enables distributed contribution. Software that is structured as separable components allows contributors to improve specific modules without needing to understand the whole system. Good open-source projects develop architectural patterns that maximize modularity, specifically to enable this distributed revision model. The same principle applies to hardware: designs that are composed of well-documented modules are more revisable than monolithic integrated designs.

The third proposition is that forking is not failure. In proprietary software, divergent development is called forking and treated as a crisis. In open-source software, forking is a normal event: someone takes an existing codebase and develops it in a new direction. Forks sometimes merge back, sometimes develop into separate products, and sometimes reveal that the original design had unnecessary constraints that the fork removes. The freedom to fork creates evolutionary pressure toward better design.

Each of these propositions transfers to hardware, with modifications that reflect the differences between information and matter.

The Open Source Hardware Association, founded in 2012, defined open-source hardware as hardware whose design is made publicly available so that anyone can study, modify, distribute, make, and sell the design or hardware based on that design. The definition mirrors the Free Software Foundation's four freedoms for software but applies them to physical design artifacts: schematics, PCB layouts, mechanical drawings, CAD files, bill of materials, and assembly instructions.

The ecosystem that has grown around this definition is heterogeneous, ranging from hobbyist communities to serious research institutions.

Arduino and its descendants remain the most widely cited success story. The original Arduino Uno, designed by Massimo Banzi and colleagues at the Interaction Design Institute in Ivrea, Italy, was released in 2005 with full schematics and an open-source integrated development environment. The design was immediately forked, modified, and extended by a global community. Adafruit, SparkFun, and dozens of other companies built businesses around manufacturing Arduino-compatible hardware, contributing improvements back to the common design pool. The result is an ecosystem of hundreds of microcontroller designs, all building on each other's work, that has lowered the barrier to electronics development for students, researchers, and entrepreneurs worldwide.

Open Source Ecology represents a more ambitious application: the Global Village Construction Set, a collection of fifty essential machines — tractor, bulldozer, CNC plasma cutter, 3D printer, bakery oven, and more — designed to enable small groups to build a modern technological civilization from raw materials. All designs are published under open licenses. The project is explicitly civilizational in ambition: to break the dependency of communities on complex global supply chains by enabling local manufacturing of sophisticated tools from published designs.

Open-source medical devices entered public consciousness during the COVID-19 pandemic, when global ventilator shortages prompted an emergency open-source response. Teams at MIT, Rice University, and dozens of independent groups published ventilator designs that could be manufactured locally from available components. Some of these designs were deployed in countries that could not access the commercial ventilator supply chain. The episode demonstrated both the potential and the current limitations of open hardware: the designs were rapidly produced and iteratively improved, but the absence of established regulatory pathways for open-source medical devices meant that deployment required emergency authorization that would not be available in non-crisis conditions.

Longer-term open medical hardware projects — the OpenBCI brain-computer interface, open-source prosthetic hands from e-NABLE, low-cost diagnostic devices from projects like Chai Biotechnology — are developing the ecosystem for sustainable open-source medical hardware beyond crisis response.

Open scientific instruments represent a particularly important frontier. The cost of laboratory equipment is a significant driver of inequality in global research. A commercial mass spectrometer costs hundreds of thousands of dollars. Open-source alternatives, built from published designs using commercially available components, can be produced for a fraction of that cost. The Open Hardware Repository at CERN maintains designs for scientific instruments that allow research institutions worldwide to access equipment previously restricted to well-funded laboratories. The potential redistribution of scientific research capacity — toward institutions in Africa, Latin America, Southeast Asia — represents a civilizational shift in where scientific knowledge is generated and by whom.

The critique of open-source hardware that takes its strongest form is the fabrication constraint: information is infinitely reproducible at zero marginal cost, but physical objects require materials, energy, and skills that are not equally distributed. Knowing how to build a ventilator does not help a hospital that lacks the machining tools, electronic components, or technically skilled personnel to build one.

This is a real constraint, not a dismissible objection. The open-source software model works because the infrastructure for running software — computers and internet connections — is increasingly ubiquitous. The equivalent infrastructure for manufacturing hardware is not.

But two developments are changing the calculus. First, digital fabrication tools are becoming cheaper and more widely available. The cost of a desktop 3D printer capable of producing structural plastic parts fell from tens of thousands of dollars in 2010 to a few hundred dollars by the mid-2020s. CNC routers, laser cutters, and vinyl cutters have followed similar price trajectories. These tools, combined with published designs, enable a new category of local manufacturer: someone who does not design products but who can produce them reliably from design files obtained online. This is the makespace or fablab model, now represented by thousands of community workshops worldwide, including in countries previously without access to precision manufacturing.

Second, and more important over the medium term, the separation of design from manufacturing that open hardware enables is itself a new kind of infrastructure. When a design is a global commons, it can be manufactured wherever fabrication capability exists. The hospital in Lagos or Nairobi that cannot design a diagnostic device might be able to manufacture one from published specifications once it has a basic machining workshop. The farmer in Myanmar who cannot engineer a seed planter can adapt a published design to local materials and soil conditions. The design commons reduces the knowledge barrier to local manufacturing without eliminating the capital requirements — and it positions local manufacturing as a site of design contribution rather than passive consumption.

Open-source hardware confronts intellectual property law as a structural obstacle. Software copyright is well-understood: code is copyrightable, and open-source licenses like GPL and MIT use copyright law to enforce sharing requirements. Hardware is more legally ambiguous. Physical objects are not copyrightable; their functional designs may be patentable; the creative expression in their CAD files may be copyrightable; trade dress may be protected separately.

This legal ambiguity means that the open hardware movement has developed its own licensing frameworks — the CERN Open Hardware Licence, the TAPR Open Hardware License, and others — that attempt to create enforceable sharing requirements using the available legal tools, primarily copyright in the design files. The CERN OHL, developed by the European Organization for Nuclear Research and the Open Hardware Repository, distinguishes between permissive, weakly reciprocal, and strongly reciprocal versions, mirroring the BSD/MIT/GPL spectrum in software licensing.

These frameworks are imperfect but functional. The more significant friction is patent law. A comprehensive patent portfolio can block open implementation of a technology even when the design files are openly published. Medical device fields, where incumbent manufacturers hold broad patent portfolios, represent the most significant obstacle to open hardware development. Clearing the patent landscape for open medical devices requires either licensing negotiations, design-arounds that achieve equivalent function without infringing specific patents, or — where public health emergencies can be demonstrated — compulsory licensing under TRIPS flexibilities in international trade law.

The civilizational importance of open-source hardware is best understood not as a technical question but as a question about who gets to participate in revision.

In the proprietary hardware model, the capacity to revise physical technology is concentrated in corporations in wealthy countries, addressing the needs of consumers with purchasing power. The rest of the world receives the outputs of this revision process but does not participate in shaping it. Technologies are designed for the markets that fund their development, then sold to everyone else as-is.

Open hardware redistributes revision capacity. When the design of a water pump, a medical device, or a communication system is a global commons, the revision loop is open to anyone who identifies a problem and has the skill to address it. A farmer who modifies an open-source seed planter to work with local soil conditions and publishes the modification contributes to the design commons. A biomedical engineer at an underfunded research hospital who improves an open diagnostic device and shares the improvement has participated in a global revision process that, in the proprietary model, she would have been entirely excluded from.

This redistribution is not charity. It is a structural change in who produces knowledge about how things should work. The knowledge produced by people trying to solve problems with limited resources — appropriate technology for real constraints — is often knowledge that is missing from products designed for wealthy markets with abundant resources. The innovations that emerge from open hardware communities in contexts of material constraint are frequently more durable, more repairable, and more efficient than their proprietary counterparts.

The larger revision that open-source hardware represents is the revision of the relationship between maker and made. The proprietary model produces consumers: people who use things designed by others, in forms they cannot change, at prices they cannot influence, dependent on supply chains they cannot see. Open hardware produces participants: people who can understand what they use, modify it for their needs, contribute improvements, and build the capacity to make new things from existing knowledge.

That shift — from consumer to participant in the material world — is Law 5 operating at the level of civilization's relationship to its own infrastructure. The object is never finished. The design is always open. And the revision is available to anyone who can use it.