Prusa Research releases Open Community License v1.1 with modular plugin system

Prusa Research has released version 1.1 of its Open Community License (OCL), introducing a modular plugin system that allows creators to attach specific conditions-such as attribution, micro-business revenue thresholds, and R&D-only use-without rewriting the entire license. The update, now live on GitHub and available as a selectable option on Printables, also tightens copyleft provisions so derivatives must be distributed under OCL, reducing license fragmentation. Prusa reports thousands of projects published under OCL v1.0 since the CORE One CAD files were released five months ago, including work from UC Berkeley and MIT research groups. The company has also released printable parts for the INDX upgrade for the CORE One+ under the new license.

This update addresses a recurring tension in the open-hardware ecosystem: the mismatch between permissive open-source ideals and the practical needs of creators who want to share designs while protecting against large-scale commercial exploitation without compensation. OCL v1.1's plugin architecture-with options like Micro Business (under €1M annual revenue) and Research & Development-gives licensors a structured alternative to drafting custom licenses, which often create legal ambiguity. The move strengthens Prusa's position as the dominant platform in the polymer material extrusion segment for prosumer and small-business users, where Printables serves as both a community hub and a de facto distribution channel. By making OCL more adaptable, Prusa reduces the incentive for creators to migrate to restrictive proprietary licenses or abandon open sharing altogether, reinforcing the value of its ecosystem against competitors like Bambu Lab and Creality.

For Prusa, the practical test is adoption: whether the plugin system actually reduces license proliferation or simply adds another layer of complexity that most creators ignore. The company must also address persistent community criticism that OCL is not a true open-source license due to its use restrictions-a tension that v1.1 does not resolve but attempts to manage through modularity. Users evaluating OCL v1.1 should verify that the plugin combinations they select are internally consistent and enforceable under their local jurisdiction, particularly for cross-border sharing.