Bambu Lab, widely regarded as making the best and most accessible 3D printers on the market, has found itself at the center of a firestorm that could reshape the entire open-source 3D printing ecosystem. The controversy began with a single private message on Reddit, sent from Bambu’s official account to a developer named Paweł Jarczak. In that message, the company asked Jarczak to delete code he had published on GitHub — code that allowed users to control their Bambu printers without using Bambu’s own software. That request, and the way it was delivered, ignited a furious backlash from the open-source community, drawing in prominent YouTubers, legal experts, and thousands of advocates who now see Bambu as a threat to the principles of open hardware and software.
The spark: A DM that backfired
On April 22nd, Bambu Lab contacted Jarczak via Reddit private message. The initial tone was polite, with Bambu explaining that it planned to change its cloud authentication and that Jarczak’s code — a fork of the popular OrcaSlicer — would soon be incompatible. The message concluded with a request: “we kindly ask you to consider removing the current connection approach, as it mimics official Bambu Lab software.” Jarczak, a developer who had previously contributed to the 3D printing community by enabling cheaper multicolor printing alternatives, responded that he was willing to remove his project. But he asked to be properly acknowledged for what he described as revealing a “significant security gap” and requested a free flagship H2D printer as compensation.
Bambu’s reply escalated the situation. Instead of recognizing Jarczak’s work, the company stated that it had already prepared a cease and desist letter and warned him about Section 1201 of the Digital Millennium Copyright Act, which punishes circumvention of digital locks. The company’s language turned confrontational: “We wanted to speak with you first and handle this in a constructive way. That said, we can’t allow this approach to continue.” Jarczak, who had voluntarily taken down his code in good faith, left a note on his GitHub repository explaining that he had been threatened and treated like a criminal. That note went viral, and the internet responded with outrage.
The community strikes back
The reaction was swift and coordinated. Consumer rights advocate Louis Rossmann publicly pledged $10,000 to defend Jarczak in court, stating, “I’ll put up $10,000 to teach Bambu Labs a lesson.” Maker and YouTuber Jeff Geerling announced he would never buy another Bambu printer and offered to contribute financially. The tech hardware site GamersNexus, known for its investigative reporting, pledged $10,000 as well, with editor-in-chief Steve Burke openly taunting Bambu: “Go ahead, Bambu: Sue us.” GamersNexus also revealed that it had been planning to purchase $150,000 worth of Bambu hardware for a 3D printing project, but halted those plans in response to the company’s actions. The Software Freedom Conservancy, a nonprofit that enforces open-source licenses, joined the fray, hosting a project to reverse-engineer Bambu’s code and promising to act as a watchdog. “They’re bad actors, straight-up, and the community should do whatever we can,” said Bradley Kühn, the father of the AGPL open-source license and a policy fellow at the Conservancy.
Kühn publicly identified two specific violations of the AGPL license that Bambu had allegedly committed. First, Bambu’s proprietary networking plug-in — which is dynamically linked to the open-source Bambu Studio slicer — should be considered “Corresponding Source” under the AGPL, meaning its source code must be released. Second, Bambu pressured Jarczak to remove his code while falsely claiming its terms of service overrode his rights under the AGPL. Jarczak published a 30-point technical analysis detailing how intimately the proprietary plug-in communicates with open-source components, arguing that the AGPL requires Bambu to share the entire system. However, legal experts note that the AGPL has never been tested in court for such cases, leaving the issue in a gray area.
The core issue: Open source vs. corporate control
At the heart of the conflict is the tension between open-source ideals and corporate business models. Bambu Studio is built on a fork of PrusaSlicer, which itself is derived from Slic3r — both products of the open-source RepRap community. Bambu freely uses this code under the AGPL license, which requires that any modified version be released under the same license. However, Bambu has introduced a proprietary authentication system that prevents forks like OrcaSlicer from directly controlling its printers without going through Bambu’s cloud. Jarczak’s code circumvented that system by essentially “impersonating” Bambu Studio to gain access — a trick that worked because Bambu’s cloud relied on a simple string identifier rather than robust server-side authorization.
Bambu argues that its actions are about security. The company claims that Jarczak’s fork exposed its infrastructure to DDoS attacks and unauthorized access. In a statement to The Verge, Bambu’s head of PR, Nadia Yaakoubi, noted that the networking plugin is “separately delivered” and not covered by the AGPL’s “Corresponding Source” definition. The company also pointed to millions of “abnormal requests” that it attributes to Jarczak’s code. But Jarczak and his supporters counter that Bambu could easily implement proper authentication measures — such as token scopes, rate limiting, and abuse detection — without resorting to legal threats. “If Bambu’s infrastructure treats that as dangerous, that is a server-side authorization and architecture problem, not proof that I attacked their infrastructure,” Jarczak told The Verge.
The open-source community sees this as a classic case of corporate enshittification: Bambu built its success on community-created code, and now it wants to lock users into its own ecosystem, potentially charging for subscriptions or locking out third-party accessories like the cheaper Biqu BCMU multicolor system. The fear is that Bambu will follow the model of inkjet printer companies that use proprietary cartridges to maximize profit. Bambu did not deny these possibilities when asked directly. The company’s initial DM to Jarczak, filled with veiled threats, only deepened the distrust. “Go fuck yourself, Bambu,” became a rallying cry, encapsulating the fury of a community that feels betrayed.
Legal limbo and the fallback to public pressure
Because the AGPL has rarely been tested in court, the outcome of any legal battle is uncertain. Lawyers specializing in open-source licensing, like Kyle Mitchell and Heather Meeker, note that the definition of “Corresponding Source” is ambiguous, and the issue of whether Bambu’s cloud services must be shared along with its software is unresolved. “There are no definitive answers to be found, just positions to take,” Mitchell said. Meeker added that only the original copyright holders of the code — which could be multiple entities — have standing to sue for license violations. The Software Freedom Conservancy is currently fighting a similar case against Vizio under GPLv2, set for trial in August, which could set a precedent.
In the absence of a clear legal path, the battle is being fought in the court of public opinion. Thousands of open-source advocates have rallied behind Jarczak, who initially did not want to be a hero. “People are trying to make me into some kind of hero here, but I am not that,” he said. The Software Freedom Conservancy aims to raise $250,000 to hire staff to “liberate AGPLv3-violating 3D printers.” Louis Rossmann’s group has already pledged $15,000. Bambu, meanwhile, has tried to soften its stance, telling The Verge that it regrets the tone of its communication and is focusing on “strengthening our own infrastructure and protection measures moving forward.” It also said it plans to close the authentication loophole but has not provided a timeline. Bradley Kühn offered a blunt solution: “They should release all the code, even if the AGPL doesn’t require it, because their business is selling hardware anyway!” Alternatively, Bambu could rewrite its software from scratch — a massive undertaking that would abandon the open-source foundation on which its success was built.
Jarczak himself does not want Bambu to go fully proprietary. “I do not think ‘fully closed’ would be better for users. It would just be more honest,” he said. For now, the 3D printing world watches as a single private message threatens to drag one of the industry’s brightest stars into a prolonged conflict that could redefine the relationship between hardware makers and the communities that support them. The outcome may determine whether open-source licenses remain a shield for innovation or become a tool for corporate control.
Source: The Verge News