Bambu Lab has threatened legal action against a developer who restored direct cloud access in OrcaSlicer, reopening remote monitoring and filament recognition features the company had pushed behind its own Bambu Connect app. The dispute is less about a single fork of open-source software than about who gets to control the daily workflow around the Bambu Lab 3D printer ecosystem.
The developer, Pawel Jarczak, shut down the OrcaSlicer-BambuLab project after the warnings. He says the code relied on public sources and that Bambu Lab had not fully closed the access route it later complained about. That is the awkward part for Bambu Lab: once you publish software under an open license, users tend to assume the door works both ways.
What Bambu Lab accused the developer of
Bambu Lab reportedly raised three complaints: reverse engineering software to impersonate Bambu Studio, violating terms of use, and bypassing authentication. Jarczak rejects all of that and points to a licensing wrinkle that makes the argument messier than a typical ”protect the platform” statement.
Bambu Studio is distributed under AGPL-3.0, the same copyleft license used by PrusaSlicer. Since Bambu Studio is built on PrusaSlicer code, its core must stay open; only the network plug-in that links printers to Bambu’s cloud is closed. That split is precisely why open-source communities get touchy when a company starts fencing off features that users had already integrated into their own tools.
Why OrcaSlicer mattered to Bambu users
OrcaSlicer began in 2022 as a fork of Bambu Studio, which itself descends from PrusaSlicer. It quickly became a favorite because the community moved faster than the official software, shipping features such as cleaner side seams, new infill patterns, automatic supports for overhangs, and built-in calibration tests before they reached Bambu’s own slicer.
Bambu Lab’s January 2025 move cut that direct cloud access and forced users through Bambu Connect, a middleman that allowed file transfer and device visibility but blocked meaningful control changes. For a printer line that leans heavily on cloud services, that is not a minor inconvenience – it is the difference between a smooth workflow and manual re-entry of settings on the machine itself.
The company said its servers were seeing about 30 million ”unauthorized” requests per day, which it framed as a security problem. The number explains the clampdown, but it also shows how dependent Bambu Lab’s ecosystem had become on third-party tools that users clearly preferred to the official path.
The next target could be BMCU
Jarczak also says his Bambu Multi-Color Unit firmware project is now at risk, and he is shifting his attention toward Klipper-based printers instead. That would be a small but telling loss for Bambu Lab: the company can restrict access, but the more it narrows the funnel, the more motivated experienced users become to leave the funnel entirely.
The interesting question now is whether Bambu Lab keeps tightening control or accepts that its best users want compatibility, not a walled garden with a nicer paint job. If the company keeps treating community tools like intruders, expect more forks, more workarounds, and fewer reasons for power users to stay loyal.