The controversy around Bambu Lab and an independent developer has highlighted tensions that can arise where proprietary services and open-source components meet. The non-profit Software Freedom Conservancy (SFC) opened an inquiry after Bambu Lab issued a cease-and-desist to developer Paweł Jarczak, the author of an OrcaSlicer fork known as OrcaSlicer-bambulab. Jarczak’s fork re-enabled certain cloud printing capabilities without relying on Bambu Lab’s official cloud service, Bambu Connect, and the resulting legal warning prompted observers across the 3D printing community to weigh in.
At the technical core of the dispute is a module Bambu Lab calls bambu_networking, which the company treats as proprietary. Jarczak reconstructed the protocol used by that module and produced a Rust-based implementation to connect community tools to printers without using Bambu Connect. Bambu Lab contends this work amounts to reverse engineering of a protected protocol and invoked both its Terms of Service and references to the DMCA and other protections. The SFC, by contrast, argues the module is part of software distributed under AGPLv3, meaning additional restrictions that limit users’ rights would conflict with the license’s copyleft requirements.
License foundations and lineage
Understanding why the license question matters requires a quick look at software ancestry. Bambu Studio’s slicer traces back to PrusaSlicer, which itself came from Slic3r. The original Slic3r was released under AGPLv3, an affero general public license variant designed to close network-access loopholes in copyleft terms. The SFC’s position is that any derivative work built upon that codebase inherits the same obligations. If a component necessary to run the product—like bambu_networking—is distributed alongside AGPLv3-licensed code but then treated as proprietary, that separation can violate the license’s requirement that recipients keep the same freedoms intact.
What the developer changed
Jarczak’s fork did not invent a new slicing engine; it modified how the client communicates with Bambu printers. By examining and reusing elements available in AGPL-licensed sources, and by writing a separate Rust implementation of the network protocol, the fork restored features some users had lost access to when Bambu Lab tightened its cloud controls. Supporters say this is precisely the kind of user empowerment that AGPLv3 intends to protect. Critics aligned with Bambu Lab argue that interacting with their cloud in ways not approved in the Terms of Service could present security or support risks.
Bambu Lab’s public stance
In statements reported to the press, Bambu Lab emphasized that its AGPL obligations do not permit actions that circumvent applicable protocols or technical protections guarding their cloud services. The company also signaled a preference for dialogue over litigation while saying it has implemented interim measures and plans further security hardening in future releases, advising users to update to the latest software. Bambu Lab framed the fork as a potential impersonation of official clients and raised concerns about arbitrary commands being sent to printers if modified clients are allowed unfettered access.
Community reaction and stakes
Responses from the 3D printing ecosystem were swift. The dispute drew public criticism from Joseph Prusa, the creator of PrusaSlicer, who flagged potential AGPLv3 violations and expressed security worries. Right-to-repair advocates and well-known independent figures joined support efforts: YouTuber Louis Rossmann pledged to assist with legal costs—offering up to $10,000—and reported plans to host the fork under the FULU Foundation GitHub, while Gamers Nexus matched that contribution. These interventions underscored broader alarm about a trend toward tying hardware to proprietary cloud services after a sale, and about how license choices shape what vendors can and cannot do.
Why this matters for users
The controversy touches on two related but distinct rights: the freedom to modify software that a user runs locally, and a vendor’s right to control access to its cloud infrastructure. AGPLv3 protects the former by requiring that network-capable derivatives share source and not add restrictions, while a service operator may legitimately restrict access to a hosted cloud. The SFC’s inquiry centers on whether Bambu Lab’s packaging of an essential networking component as proprietary effectively imposed new limits on users of AGPL-licensed code.
For owners of Bambu printers and the wider maker community, the episode is a reminder to watch license terms, keep software updates current, and consider the trade-offs of cloud-dependent features. The dispute has not ended in a court ruling, but it has already reshaped conversations about open-source compliance, user autonomy and how companies weave together proprietary services and community-built code.
