Bambu Lab and the AGPL Dispute, Explained
Published · Updated · Ecosystem, software licensing · figures as of July 18, 2026
Short version
The Software Freedom Conservancy (SFC), a nonprofit that enforces open-source licenses, says Bambu Lab violates the AGPLv3 license that governs Bambu Studio, by shipping the slicer with proprietary networking libraries and no corresponding source, and by pressuring a developer into removing an OrcaSlicer fork. Bambu walked back the legal pressure in May ("that was not the outcome we wanted") but has not released the disputed code. The SFC set out to raise $250,007 by July 17 to fund staff and a project called baltobu, and it hit the goal a day early. As of July 18 the counter stands at roughly $275,400 and is still climbing. Nothing about this changes how your printer works today, but the outcome will shape the third-party software ecosystem around Bambu machines.
Transparency note: BambuHub earns affiliate commissions when readers buy Bambu hardware through some links on this site. This article contains no affiliate links, and we lay out both positions as plainly as we can.
The 60-second licensing background
Bambu Studio is a fork of PrusaSlicer, which itself descends from Slic3r, software released under the AGPLv3 license. AGPLv3 is a "copyleft" license: you may build on the code, including commercially, but the combined work you distribute must also be offered under AGPLv3, with complete corresponding source code. The license's own words require that "the entire work, as a whole" carries the license. You cannot take copyleft code, bolt proprietary pieces onto it, and ship the result closed.
What the SFC alleges
- Missing source code. Bambu Studio ships with proprietary networking libraries (
libbambu_networking.so,bambu_networking.dll,libbambu_networking.dylib) that handle the connection to Bambu's cloud and printers. The SFC's position: those libraries are part of the combined AGPLv3 work, so their source must be published. It is not. - Restricting user rights. Developer Paweł Jarczak built an OrcaSlicer fork that integrated with Bambu's services. Bambu demanded its removal, citing its terms of service; Jarczak took it down "under protest." The SFC argues AGPLv3 §10 forbids imposing "further restrictions" on rights the license grants, and that terms of service cannot override a copyleft license.
Bambu's side, and the partial walk-back
Bambu's stance, as reflected in the SFC's account, is that its terms of service govern access to its network services, and that the networking libraries are separate proprietary components. On May 23, after public pressure, Bambu withdrew the legal threat against Jarczak, saying the "reference to terms of service, legal context, and a potential C&D understandably came across as a legal threat. That was not the outcome we wanted" (via Notebookcheck). What Bambu has not done, as of this writing: released the disputed library source, or committed to a licensing remedy. We could not find a comprehensive public statement from Bambu addressing the AGPL question itself, and will update this piece if one lands.
What "baltobu" actually is
The SFC's response is practical rather than (so far) a lawsuit. Project baltobu (short for "Bringing Affero Licensed Things (On)to Bambu Users") has three legs: reverse-engineering the proprietary networking libraries, maintaining Jarczak's OrcaSlicer fork so Bambu owners keep a fully free slicer option, and developing a Bambu Studio replacement dubbed viscose. In short: if the vendor will not open the code, build an open equivalent alongside it.
The fundraiser
To staff that work long-term, the SFC set a goal of $250,007, running two months from the May 18 announcement to July 17. It looked tight: as late as July 14 the public counter still showed roughly $173,600, about $76,400 short. Then the final stretch closed the gap. The SFC says the funds pay for dedicated staff time on software right-to-repair work, with the Bambu situation as the flagship case.
Update, July 18, 2026: goal reached, and then some. The SFC announced on July 16, a day before the deadline, that the fundraiser had hit its $250,007 target. Donations kept coming: as of July 18 the counter shows an additional $25,403 on top of the goal, roughly $275,400 in total. The SFC says the money funds dedicated staff and litigation counsel for its right-to-repair work, with baltobu as the flagship project, and it has opened a public baltobu mailing list as the project's first visible step. No new statement from Bambu Lab so far; we will keep this page updated.
What this means for Bambu owners
- Today: nothing changes. Your printer prints, Bambu Studio slices, cloud services run. This is a licensing dispute, not an outage.
- Medium term: the dispute decides how much room third-party tools like OrcaSlicer have to interoperate with Bambu's ecosystem, exactly the tools many owners rely on.
- Long term: it is a test case for whether hardware companies can build on copyleft software while keeping the connective tissue proprietary. The answer will matter well beyond Bambu.
The bottom line
Strip the heat away and the disagreement is narrow: the SFC says the networking libraries are legally part of an AGPLv3 work and must be opened; Bambu treats them as separate proprietary components governed by its terms of service. Courts have rarely tested AGPLv3 at this depth, which is why a nonprofit crowdfunding an engineering answer, rather than only a legal one, is the most pragmatic move on the board. The July 17 deadline answered how much the community is willing to pay to find out: more than the asking price.
Sources: Software Freedom Conservancy, "Comprehensive Response to Bambu's AGPLv3 Violations" (May 18, 2026) for the allegations, baltobu/viscose scope, and fundraiser terms; SFC news post "Right to Repair Fundraiser Goal Reached" (July 16, 2026) and the sfconservancy.org counter (checked July 18, 2026) for the outcome figures and mailing-list launch; Notebookcheck (May 23, 2026) for Bambu's withdrawal of the legal threat and quoted statement. The SFC is a party to the dispute; where Bambu's position is described, it is as reflected in the SFC's account and press coverage, since Bambu has not published a comprehensive statement we could cite. Figures and status are dated and will change.