When two of the most-watched names in hardware media each put $10,000 behind a single developer's legal defense, the dispute has stopped being a niche licensing argument. That's where Bambu Lab finds itself in mid-2026: under formal investigation by the Software Freedom Conservancy for AGPLv3 violations, with GamersNexus and Louis Rossmann bankrolling the other side. Here's how a firmware update turned into an open-source crisis, and what it means if you build your own machines.
What Authorization Control Did
The roots go back to January 2025, when Bambu Lab announced that future firmware would add an authorization and authentication layer to its printers, citing security. In practice, “Authorization Control” gated core printer functions — print start, motion control, fan and hotend control, AMS configuration, calibration, and remote video — behind a Bambu-issued authentication path, and blocked communication from unofficial third-party software.
The most visible casualty was OrcaSlicer, the open-source slicer that had worked closely with Bambu hardware; its developer declined to adopt Bambu’s gateway, calling it no meaningful benefit to users. Accessories like BIQU’s Panda Touch broke too. Bambu justified the lockdown by citing what it said were up to 30 million unauthorized requests per day to its servers, plus DDoS attacks. The company has stated that figure; critics dispute it.
Why It Became an AGPLv3 Problem
Bambu Studio, the company’s slicer, is built on open-source software licensed under the AGPLv3 — a license that requires distributing source code for the software you ship, and forbids imposing additional restrictions on the rights it grants. The Software Freedom Conservancy’s investigation centers on two alleged violations: that Bambu distributed a proprietary networking library (libbambu_networking) without releasing its source, and that its legal threats against a community developer amounted to imposing further restrictions the license prohibits.
That developer is Paweł Jarczak, who built an OrcaSlicer fork that restored direct printer and cloud control by deriving it from Bambu’s own published AGPL source. Bambu argued the fork mimicked official traffic and contributed to server outages; Jarczak countered that his method came straight from code Bambu had already released. When Bambu escalated to a cease-and-desist, the licensing question moved from forums to lawyers.
The Investigation and the War Chest
The Software Freedom Conservancy — a nonprofit that enforces open-source licenses — opened a formal investigation and launched a project called baltobu to reverse-engineer the networking library, maintain Jarczak’s fork, and build a replacement for Bambu Studio. Jarczak joined as a collaborator. The SFC’s fundraiser to staff the effort targets $250,007, and had passed $60,000 early on.
The community response was loud and well-funded:
- GamersNexus published a piece bluntly titled “Fuck You, Bambu Lab,” pledged $10,000, rehosted the contested code, and announced it was switching to Prusa hardware — putting in an order of roughly $5,000.
- Louis Rossmann, the right-to-repair advocate, offered $10,000 (which Jarczak declined) and pointed his 2.5-million-strong audience at the issue.
- The FULU Foundation formally republished the fork, and Snapmaker reportedly donated equipment to the developer.
In other words, the people Bambu most needed on its side — reviewers, repair advocates, and open-source maintainers — lined up against it.
What Prusa Gains
The clearest beneficiary is Prusa Research. Its Core One leans on exactly the attributes Bambu is being criticized for lacking: open firmware, slicer freedom, and no cloud dependency. GamersNexus’s public switch is the headline example, but the broader shift is that “open” has become an actual purchasing argument in 2026, not just a hobbyist value. The self-build world — Voron, RatRig, and the wider Klipper ecosystem — has spent years building printers that no vendor can remotely restrict, and the Bambu situation is the strongest validation of that approach to date.
Why This Matters for Self-Builders
If you run a Voron, a RatRig, or any Klipper machine, none of this can happen to you. That’s the whole point. Your firmware is open, your slicer is your choice, and no authentication server stands between you and your own printer.
We’ve kept our ecosystem hubs deliberately self-build-only for this reason: a printer you fully own can’t have features revoked in a firmware update. For Bambu owners feeling boxed in, the practical response is the one the community has documented all year: open firmware and self-build exit ramps, including full Klipper conversions of closed machines. A printer you build yourself is one no update can take back.