A dispute involving Bambu Lab and a small fork of OrcaSlicer has intensified debate over how a hardware vendor should manage cloud access when its desktop software incorporates open-source code. In a critical account, technology writer Jeff Geerling accused Bambu Lab of using legal and public pressure against a developer whose fork enabled printer features without the company's standard cloud delivery path.
The controversy sits within a layered software lineage. OrcaSlicer is derived from Bambu Studio, which in turn traces to PrusaSlicer and Slic3r; the projects are described as licensed under version 3 of the GNU Affero General Public License. Geerling said he had already isolated his own Bambu P1S from the internet, stopped firmware updates, enabled Developer mode and replaced Bambu Studio with OrcaSlicer to retain local control.
According to the account, the disputed fork, called OrcaSlicer-bambulab, used code from the Linux version of Bambu Studio to access features without routing print delivery through Bambu's cloud. Geerling said Bambu threatened its developer with legal action and publicly characterized the implementation as falsifying identity metadata so that requests appeared to come from the official client. He rejected the implication that the developer had created an impersonation attack, arguing that the behavior came from upstream, AGPL-licensed code.
Bambu's position, quoted in the article, was that widespread or faulty use of this method could produce large volumes of traffic indistinguishable from its official client. The company framed that as a structural vulnerability for its servers. Geerling disputed the security logic and argued that a public client identifier should not serve as a primary defense against abusive traffic. He also criticized the company for declining his request to publish the full correspondence.
The account acknowledges that a request to remove Bambu's name from the fork could have raised a more conventional trademark question. Its larger objection is that the company used infrastructure and security claims against a developer who had previously helped users with Linux and Wayland issues. Geerling said the fork appeared to have very limited adoption before the cease-and-desist action.
The article also reports that repair advocate Louis Rossmann offered $10,000 to support a legal defense, should the developer choose to contest the threat. No court outcome or independent legal analysis is supplied.
Because the available evidence is Geerling's own commentary, the allegations and interpretations should be read as one party's account, while Bambu's quoted rationale represents the response included there. The episode nevertheless highlights a persistent tension: customers may expect local control over purchased hardware, while vendors operating cloud services may seek tight control over which clients can connect to their infrastructure.
