Bambu Lab killed an OrcaSlicer fork by lawyer letter. The fork was based on Bambu's own AGPL code.

Bambu Lab’s lawyers shut down an OrcaSlicer fork on May 1. The project, OrcaSlicer-bambulab maintained by Polish developer Pawel Jarczak, restored the cloud printing and authentication features that Bambu’s recent firmware locked away from third-party software. Jarczak says he received a cease-and-desist accusing him of “impersonating Bambu Studio, bypassing authorization controls, reverse engineering, and Terms of Use violations.” He pulled the code rather than fight.

The repo is now an empty README with a farewell note. Tom’s Hardware reported the takedown on April 29. The wider story is the one Bambu Lab clearly didn’t want told: the fork was built on top of Bambu Studio, which is published under the AGPL-3.0 license. AGPL is the most aggressive copyleft on common open-source projects, designed to keep network-deployed software free. Bambu published its slicer under that license and is now arguing that a fork of the same source can’t ship.

What Jarczak’s fork actually did

Bambu’s recent firmware update introduced Bambu Connect, a middleware layer that limits how third-party slicers can talk to a Bambu printer. Cloud uploads, remote print start, and webcam streaming all routed through Connect’s authentication. OrcaSlicer (the upstream project that Jarczak’s fork was based on) lost direct access to those features as soon as the firmware shipped, and Bambu Lab buyers who’d been using OrcaSlicer for months were locked into Bambu Studio if they wanted full functionality.

Jarczak rebuilt the cloud path. His fork added an integration layer over Bambu Studio’s own AGPL’d source so OrcaSlicer could authenticate with the Bambu cloud and use the same remote-print API. According to his GitHub note, “the removed repository did not redistribute Bambu Lab’s proprietary networking plugin binaries”, only public source plus his own glue code. The capability he was using, he argues, “existed within Bambu Lab’s own Linux workflow and hadn’t yet been disabled by the company.”

The AGPL angle

This is where the dispute gets interesting. Bambu Studio is under AGPL-3.0, the same license Warp open-sourced its terminal under last week. AGPL grants downstream users the right to fork, modify, and redistribute as long as derivative works also publish their source. That’s the deal Bambu accepted when it picked the license.

Bambu Lab’s claims, per Jarczak’s account, weren’t grounded in copyright. They were grounded in Terms of Use, impersonation, and reverse engineering. That distinction matters: a copyright infringement claim against an AGPL fork is hard to win, but Terms-of-Use and DMCA-circumvention claims have lower bars and longer reach. Jarczak asked Bambu’s lawyers to “identify specifically which files or code paths were problematic and provide the exact legal basis for their objection.” He says the clarification never came.

He also asked permission to publish the correspondence. Bambu refused. So the public record now consists of Jarczak’s summary on GitHub, Bambu Lab’s silence in response to multiple outlets including XDA Developers, and a community forum where Bambu owners are asking what happens to the slicer they bought their printer to use.

Why this looks like vendor lock-in dressed as a security update

Bambu Lab framed Bambu Connect as a security feature. The line, when the firmware shipped earlier this year, was that Connect prevents arbitrary commands from being sent to printers. That’s true, but it’s also a deflection. The same authentication system that blocks “arbitrary commands” blocks every third-party slicer, every home automation script, and every alternate frontend. The security framing turns into a sales channel for Bambu Studio.

The pattern matches the thermostat-and-printer playbook of the last decade. Sell hardware at a competitive price. Ship firmware that depends on the manufacturer’s cloud. Lock out alternatives by claiming security. Threaten the people who write the alternatives. Bambu is now in the middle of step four. Nest, John Deere, and HP have already finished the playbook, and the customer reaction in each case was identical: a slow erosion of trust that takes years to undo.

The OrcaSlicer project itself is unaffected. The fork that got shut down was Jarczak’s; the upstream OrcaSlicer is still alive, still under AGPL, and still ships builds that work with non-Bambu printers. The casualty is the bridge between the two ecosystems, and the people who lose access are the ones who already paid Bambu Lab a four-figure invoice for hardware.

What this means for you

If you own a Bambu Lab printer and you were using OrcaSlicer with it, your options have narrowed. Either you stay on the older firmware that predates Bambu Connect, or you switch to Bambu Studio. There’s no third path in production right now, and based on Bambu’s posture, there isn’t going to be one without a court intervening.

If you’re shopping for a 3D printer and you cared about software freedom, this episode is the data point you needed. Prusa, Voron, and the open-frame Cartesian community remain credible alternatives, and a printer whose firmware doesn’t fight your slicer choice is worth a small premium.

If you’re an open-source maintainer of a project that touches Bambu hardware, talk to a lawyer before you push the next commit. The lesson Jarczak’s takedown teaches isn’t that Bambu wins on the merits. It’s that fighting Bambu costs more than the project earns, and a chilling effect doesn’t need a court ruling to be effective.