A cloud-access modification for OrcaSlicer triggered backlash after Bambu Lab demanded its removal, reigniting debate over open-source freedoms, proprietary cloud control, and printer security.
A growing conflict between open-source software freedoms and proprietary cloud infrastructure has erupted after Bambu Lab demanded the removal of an unofficial cloud-access modification for OrcaSlicer.
Independent programmer Pawel Jarczak developed the modification to restore direct cloud connectivity between OrcaSlicer and Bambu Lab printers. The company alleged the implementation impersonated BambuStudio, bypassed authorisation controls, violated Terms of Use, involved reverse engineering, and could allow arbitrary commands to be sent to printers.
“Bambu Lab contacted me directly and demanded the removal of the solution,” Jarczak stated, adding that the company referenced legal action and a cease-and-desist letter.
The dispute has triggered backlash across the open-source community, with critics arguing users should retain the freedom to modify software and hardware they own. Several users reportedly stated they would stop using Bambu Lab products over concerns surrounding platform restrictions and vendor control.
BambuStudio itself is open source, based on PrusaSlicer and ultimately Slic3r, enabling developers to create forks such as OrcaSlicer.
However, Bambu Lab defended its actions by distinguishing open-source software from privately operated cloud infrastructure. The company stated, “A license for code is not a pass to our cloud infrastructure,” stressing that access to its cloud services is governed by user agreements rather than AGPL licensing.
