Bambu Lab pressures OrcaSlicer fork that restored direct cloud printing

Bambu Lab’s latest software move hit the part of ownership that matters most day to day: the button you press to send a file to your printer. Paweł Jarczak’s OrcaSlicer-bambulab fork briefly brought back direct cloud printing for Bambu owners, then disappeared after Bambu Lab contacted him and the repository was pulled in full. For users who had built their workflow around OrcaSlicer, the change meant the old send-and-print path was back for a moment and then gone again.

The clash traces back to January 16, 2025, when Bambu Lab said it was introducing an authorization and authentication protection mechanism for printer connection and control, then updated that post on January 20 for OrcaSlicer users. Bambu’s own January materials said Bambu Connect was the intended bridge for third-party workflows under the new model. In Bambu’s wiki, Developer Mode was described as a LAN-only option that does not require authorization verification and preserves third-party control without modification, but it does not connect to Bambu Cloud. Bambu Connect, meanwhile, is positioned as the secure interface for printer control and monitoring, with the wiki saying it uses a new network plugin and can handle firmware updates, remote video streaming, and file downloads. Windows and macOS builds are listed, while Linux remains under development.

Jarczak’s fork went straight at the pain point Bambu users complained about most: the extra hop through Bambu Connect just to get back to the cloud-print workflow they had before. According to the repository notice, the code, releases, tags, and related materials were removed after direct contact from Bambu Lab about the removed network integration path. Jarczak said Bambu Lab accused the fork of impersonating Bambu Studio, bypassing authorization controls, violating terms of use, reverse engineering software, and enabling modified forks to send arbitrary commands to printers. He asked for more detail, got broader accusations instead, and pulled the project down rather than keep fighting. He also argued that Bambu Studio is covered by AGPL-3.0 and that the cloud-printing plugin relies on non-free libraries, so the fork did not redistribute proprietary code.

The reaction in the maker community was immediate. Users on Reddit and the Bambu Lab Community Forum argued that a company they already trust with expensive hardware was now tightening software control too, while others defended the security rationale. Bambu’s own forum posts said direct access for OrcaSlicer would not continue and users would need Bambu Connect instead. Similar takedown-style notices also hit mirrors and forks from jmil and PolItKy, reinforcing the message that Bambu wants integrations routed through approved paths, not reopened direct cloud access. For Bambu owners, that turns a slicer update into a bigger question: how much of a printer’s useful life is truly owned, and how much is rented behind someone else’s permission layer.