Bambu Lab threatens OrcaSlicer fork developer over cloud access dispute

Bambu Lab’s move against a fork of OrcaSlicer could change the way Bambu owners print day to day, especially anyone who relies on cloud features, remote control, or third-party slicer workflows to keep a farm or a single machine running smoothly. The dispute is not about OrcaSlicer itself, but about OrcaSlicer-BambuLab, a separate fork created by Polish developer Pawel Jarczak to reconnect the slicer to Bambu Lab’s cloud infrastructure after newer software changes limited remote printer functions.

Bambu Lab said on May 8, 2026 that the fork tried to impersonate an official Bambu Studio client by injecting falsified identity metadata into network communications. The company said that behavior could create DDoS-like load patterns and threaten the stability of its private cloud infrastructure. It also drew a hard line between software licensing and service access, saying Bambu Studio is AGPL-3.0 licensed and can be modified and redistributed, but access to Bambu’s cloud is controlled by a user agreement, not the AGPL.

Jarczak pushed back in the repository README, saying Bambu Lab accused him of reverse engineering, impersonation, and violating terms of use. He said he used only publicly available source code and removed the repository voluntarily after receiving legal threats. He also said the company’s public accusations were one-sided and were not first presented to him in the same forum, leaving him unable to answer them there.

For Bambu users, the practical issue is bigger than the legal sparring. If your workflow depends on OrcaSlicer, the cloud, or remote printer functions, this dispute sharpens the lock-in question: how much control does Bambu want to keep, and how much freedom can users expect if they build around open-source tools? Bambu told users that Bambu Connect, Lan Mode, and Developer Mode are still available for advanced users who do not want to use the cloud, but the company’s cloud-first shift has already pushed some owners to isolate their printers, stop firmware updates, and lock them into Developer mode.

That reaction was already building before this fight. Jeff Geerling wrote on May 12, 2026 that he had blocked his Bambu printer from the internet, stopped firmware updates, locked it into Developer mode, and switched to OrcaSlicer. He called Bambu’s approach an abuse of the open-source social contract. By May 11, All3DP said the takedown had only given the fork a bigger audience. For Bambu owners and OrcaSlicer users alike, the message is blunt: the cloud may still work today, but trust, access, and long-term support now feel less like a given and more like something you have to plan around.