Bambu Lab vs.
OrcaSlicer:
When a Legal Threat
Meets Open-Source Law
A solo developer restored what Bambu Lab took away. Bambu's response was a cease-and-desist letter — wielded against code that Bambu itself was obligated to open-source under the AGPL license. Here is the full story, the license breakdown, and why every Bambu owner should care.
What Actually Happened,
From the Beginning
This is not just a story about one developer and one cease-and-desist letter. It is about a company that built its slicer on open-source code it did not write, benefited enormously from a community it is now restricting, and has responded to good-faith community work with legal threats.
To understand the dispute, you need to understand what OrcaSlicer actually is. OrcaSlicer is a fork of Bambu Studio, created by developer SoftFever in 2022. Bambu Studio is itself a fork of PrusaSlicer. All three slicers share the same AGPL-3.0 open-source code lineage. OrcaSlicer quickly became the gold standard for many Bambu Lab users — community-driven, rapidly innovating, introducing features like scarf seams, crosshatch infill, mouse ears, and a built-in calibration suite long before Bambu Lab's official releases caught up.
Then, in January 2025, Bambu Lab changed the rules. The company removed OrcaSlicer's ability to send print jobs directly to its printers over the cloud. Instead, Bambu Lab required all third-party slicers to route connections through a new standalone middleware application called Bambu Connect. The stated reason: security. Bambu Lab claimed the restrictions were necessary to protect its cloud infrastructure from roughly 30 million "unauthorized" daily cloud requests.
The problem: Bambu Connect was not a like-for-like replacement. Though Bambu Lab offered up "Bambu Connect" to allow OrcaSlicer to send files, it severely limited users' access to their own machines. OrcaSlicer could "see" your printer's and AMS's settings, but could not change anything. Changing the speed, temperature, or colors in the AMS required users to manually input data directly into the printer.
OrcaSlicer's developers declined to adopt the two-app workflow. Users were left with an ugly choice: update firmware and lose OrcaSlicer's cloud printing entirely, or freeze on old firmware and never receive updates.
Enter Paweł Jarczak
Independent software developer Paweł Jarczak spent weeks on the problem. He eventually created a fork of OrcaSlicer called OrcaSlicer-bambulab that restored direct cloud printing functionality to Bambu Lab printers. The fork received several public releases on GitHub and attracted significant community attention.
Jarczak's technical argument was specific: he argued that his fork used only publicly available source code and exploited a pathway that Bambu Lab itself admitted it had simply not yet disabled on the Linux side of its workflow. He was not cracking encryption or reverse-engineering proprietary binaries. He was using publicly available AGPL-licensed code that Bambu Lab was legally required to publish.
Bambu Lab's response was a cease-and-desist letter — not a conversation, not a technical objection, not a pull request asking him to fix an issue. A legal threat, directed at a single developer maintaining a community project in his spare time.
What Bambu Lab
Accused Him Of
Jarczak published a detailed account on GitHub before removing the project. According to his statement, Bambu Lab's legal team accused him of the following:
Reverse engineering Bambu Studio's software — impersonating the official Bambu Studio application to gain unauthorized access to Bambu Lab's cloud infrastructure.
Bypassing authorization controls — the authentication and authorization mechanisms Bambu Lab introduced to restrict which software can send commands to its printers.
Violating Bambu Lab's Terms of Use — using Bambu's cloud infrastructure through a non-approved application pathway.
Enabling arbitrary commands — creating a modified fork capable of sending unapproved commands to printers, framed as a security and safety risk.
Jarczak's counter to each accusation was detailed and specific. Jarczak claims they asked Bambu Lab for more information, but instead "received further broad accusations, including repeated references to 'reverse engineering'."
"Bambu Studio is released under the AGPL-3.0 license, and the plugin required for cloud printing is 'an optional component based on non-free libraries.' My work doesn't redistribute proprietary Bambu Lab code — it builds upon the available Bambu Studio source code."
The critical distinction Jarczak drew: he did not redistribute Bambu Lab's closed-source networking plugin binaries. He built on the open-source AGPL code that Bambu Studio publicly releases. In his reading of the situation, the pathway he used was not hidden or encrypted — it was simply a code path that Bambu Lab had not yet disabled on the Linux side of its system. Using publicly available open-source code to access a pathway the code owner had not yet closed is not reverse engineering. It is software development.
Bambu Lab has not issued any public statement responding to Jarczak's characterization of events.
What AGPL-3.0 Actually
Requires
The Bambu Lab / OrcaSlicer dispute cannot be understood without understanding the AGPL license — what it is, what it requires, and why it matters specifically in this situation.
The chain of inheritance is straightforward: Slic3r → PrusaSlicer → Bambu Studio → OrcaSlicer. All share AGPL-3.0 code at their core. That means Bambu Lab, by building Bambu Studio on top of PrusaSlicer's AGPL codebase, inherited the license obligations that PrusaSlicer carried — including the obligation to keep the core software open source.
Anyone who distributes or provides network access to modified AGPL software must make the full corresponding source code available. Modifications must be released under the same AGPL license. You cannot take AGPL code, make changes, and close those changes off to the public — whether distributed or run over a network.
Bambu Lab's networking plugin — the critical component enabling cloud communication with Bambu printers — is closed-source. Bambu Lab argues this plugin is a separate, independent component not derived from AGPL code. This interpretation is disputed in the community, and was the subject of a separate GitHub issue in February 2025 questioning whether Bambu Studio version 1.10.02.76 published its full source as required.
Bambu Lab has previously stated on its blog: "Enhancing AGPL software with a third-party library, service, or software that is independent and distributed separately is a common approach within the IT industry." The company says its lawyers confirmed AGPL compliance. The open-source community is not universally persuaded.
Jarczak did not touch the networking plugin. He built on the publicly available AGPL source code that Bambu Lab is obligated to publish. If you are allowed to publish code under AGPL, others are allowed to build upon it under the same license. That is the entire point of copyleft licensing.
AGPL-3.0: What You Can and Cannot Do
You can use AGPL code commercially. The license imposes no conditions on commercial use of AGPL-licensed software.
You can modify AGPL code. Changes are permitted — but if you distribute or provide network access to those changes, you must release the source under AGPL.
You can fork AGPL code. Forking is not just permitted — it is the entire mechanism that makes open-source development work. OrcaSlicer is a fork. Bambu Studio is a fork. Forks of forks are legal and expected.
You cannot sublicense AGPL code. You cannot take AGPL code, modify it, and close those modifications off — whether distributed as a binary or run over a network.
The "separate plugin" argument is contested. Bambu Lab's claim that its networking plugin is sufficiently independent from the AGPL core to avoid copyleft obligations is a legal interpretation that the open-source community has challenged. It has not been tested in court.
The deeper irony: If Jarczak's fork was really just using publicly available AGPL-licensed source code — code that Bambu Lab is legally required to publish — then Bambu Lab was effectively using copyright law to restrict the use of code it was obligated to make freely available. That is not how AGPL is supposed to work.
What Bambu Lab Actually
Took Away
The community's frustration is not abstract. Bambu Lab's January 2025 policy change had concrete, specific impacts on how real people use their printers. Understanding what was lost makes the intensity of the reaction comprehensible.
Slice in OrcaSlicer, hit print, job goes directly to your Bambu printer over the cloud. One app, one step, full feature access.
Must have Bambu Connect running as middleware. OrcaSlicer routes through Bambu Connect. Many cloud features unavailable or read-only.
OrcaSlicer could read and set AMS filament data, trigger color changes, monitor and adjust multi-material profiles remotely.
Bambu Connect limits OrcaSlicer to reading AMS data. To change anything — speed, temperature, filament color — users must manually input settings at the printer.
Cloud-based file sending over WiFi. No physical media required for most users' standard workflows.
Until March 2025, Bambu Lab printers had no USB drive support. Users were limited to inconvenient microSD cards not designed for frequent access — for three months.
The loss of these capabilities hit Bambu Lab's most engaged, sophisticated users hardest — exactly the community that had helped popularize Bambu printers by creating guides, reviews, community mods, and calibration resources. This is not an accident: power users who want granular control are precisely the users who rely on third-party software like OrcaSlicer. They are also precisely the users most likely to notice and respond loudly to capability regressions.
Community response: Some users went further and described Bambu Lab as the "Nintendo of 3D printing." The comparison reflected a view that the company tightly controls both its hardware and software ecosystem. The phrase spread rapidly across Reddit, Bambu Lab's own forums, and 3D printing communities on YouTube and Discord.
Security Justification or
Ecosystem Lock-in?
Bambu Lab's stated reason for the Bambu Connect requirement — protecting cloud infrastructure from 30 million unauthorized daily requests — deserves to be taken seriously. It also deserves scrutiny.
Cloud infrastructure abuse is a real problem. Unauthorized API traffic can cause genuine performance and security issues for the services legitimate users depend on. If OrcaSlicer users were generating 30 million requests per day that Bambu Lab's infrastructure had not been designed to handle, that is a legitimate operational concern.
But the solution Bambu Lab chose — removing capabilities from third-party software, replacing them with a middleware application that deliberately restricts what that software can do, and then using legal threats to block a community developer who restored those capabilities — raises questions that go beyond infrastructure management.
The Open-Source Debt Problem
Bambu Lab entered the 3D printing market in 2021 with printers that were fast, polished, and significantly cheaper than the competition. They achieved that speed of development in part by building on a stack of open-source software they did not create: PrusaSlicer's codebase, Klipper firmware concepts, and the decade of open-source development that preceded them. The community's investment in that open-source ecosystem was, in part, an investment in Bambu Lab's product.
Bambu Studio has to be AGPL licensed because so is what it's built on, but in many ways that's just the enabler for a proprietary system that they have in place. They have reaped years of benefits from this, benefiting from the work of others. That observation — from developer Armin Ronacher — points at the fundamental tension: a company can take from an open-source ecosystem, fulfill the minimum license obligations, and still behave in ways that the spirit of that ecosystem never anticipated.
The Real Cost to Jarczak
Paweł Jarczak is not a corporation. He is a single developer who maintains, in addition to the OrcaSlicer fork, the Bambu Multi-Color Unit (BMCU) — a DIY alternative to Bambu Lab's official AMS multi-material system. He said there is a growing risk that the BMCU will also be locked out of Bambu Lab's ecosystem and is pivoting to Klipper-based printers. He is currently crowdfunding that project through Ko-Fi and Revolut.
The threat of legal action from a well-funded manufacturer is not symmetric with a solo open-source developer's ability to respond. Even if Jarczak were entirely legally in the right — even if his use of AGPL code was fully justified by the license — the cost of defending that position against Bambu Lab's legal team would be personally ruinous. This is the mechanism by which legal threats work against community developers: not by winning in court, but by making the cost of fighting prohibitive.
Jarczak chose not to fight. He voluntarily removed the project, stated his case publicly, and moved on to platforms where similar restrictions are less likely. The community lost the fork. Bambu Lab faced no consequences. That asymmetry is worth sitting with.
Where Does Legitimate Security End?
The incident underscores a broader industry debate: where does legitimate security end and anti-competitive behavior begin?
A manufacturer can reasonably argue that unverified third-party software sending arbitrary commands to a machine capable of heating elements to 300°C+ and driving motors at high speed poses genuine safety risks. Firmware authentication and command signing are legitimate engineering choices. Documenting an API for third-party software — which would allow community developers to interact with printers through approved, safe channels — is the alternative that critics have been asking for since January 2025. Bambu Lab has not provided one.
The gap between "we need to control unsafe commands for security reasons" and "here is a documented, approved API for third-party slicers" is the space where Bambu Lab's credibility on this issue lives or dies. The longer they stay in that gap — restricting community access without providing an approved alternative — the harder it becomes to argue that security is the primary motivation.
What This Means If You
Own a Bambu Printer
If you own a Bambu Lab printer and you are reading this, here is what the Jarczak situation actually tells you about the ecosystem you have invested in:
Your printer's functionality is not entirely under your control. Bambu Lab has demonstrated that it can and will modify what third-party software can do with your printer via firmware and cloud-side changes — without advance notice, without community input, and without providing equivalent alternative tools on a reasonable timeline.
The open-source ecosystem that made Bambu popular is under pressure. OrcaSlicer exists because of open-source culture. The calibration tools, the advanced features, the rapid iteration that helped Bambu Lab's printers earn enthusiast credibility — these came from a community that expected the open-source relationship to be reciprocal. Jarczak's case is a signal that Bambu Lab's appetite for that reciprocity has limits.
Future ecosystem restrictions are possible. Jarczak noted publicly that his BMCU project — a DIY alternative to Bambu Lab's AMS — faces growing risk of being locked out of the Bambu ecosystem. If Bambu Lab's authentication and authorization mechanisms can restrict slicer access, they can also restrict third-party hardware integrations. That includes community-built AMS alternatives, third-party enclosures with monitoring integrations, and any other ecosystem add-on that relies on Bambu's cloud or firmware.
The pivot to Klipper is gaining momentum. Jarczak is not alone in treating Klipper-based platforms as a safer long-term bet for community development. The event has reinforced the case, loudly, for printers built on fully open firmware stacks — where no manufacturer can modify what your software can do without your consent.
The practical upshot: If you use OrcaSlicer with a Bambu printer and cloud printing matters to you — check the current state of Bambu Connect compatibility before updating firmware. The official OrcaSlicer project continues development and maintains some compatibility, but the situation remains fluid. Consider whether cloud dependency for advanced features is something you want in a printer for the long term.
Frequently Asked Questions
AGPL (Affero General Public License v3) is a strong copyleft open-source license that requires anyone who distributes or provides network access to modified versions of AGPL software to make their full source code available. Bambu Studio is AGPL-licensed because it is built on PrusaSlicer, which is AGPL. This means Bambu Lab must keep Bambu Studio's core code open source — which is precisely why Jarczak could build a fork using that code. The dispute is about whether his use of that publicly available AGPL code was lawful — and his argument is that it obviously was.
No court has ruled on this, and Bambu Lab chose not to pursue formal legal action after Jarczak removed the project. Jarczak's stated position is that he used only publicly available AGPL-licensed source code and did not redistribute any proprietary Bambu Lab binaries. Open-source lawyers and community members who have reviewed the situation tend to be sympathetic to his reading. Bambu Lab has not publicly provided the legal reasoning behind its allegations in any detail.
Yes — the official OrcaSlicer project is ongoing and maintains some compatibility with Bambu printers through Bambu Connect. What you lose is the direct cloud printing path and full AMS control that existed before January 2025. Many users are operating this way. The Jarczak fork specifically was about restoring that lost functionality — and that fork is now gone.
OrcaSlicer's developers declined to build a two-application workflow because it degrades the user experience — requiring a separate running application to broker connections introduces complexity, reduces reliability, and limits what OrcaSlicer can do. The argument is principled: third-party software should be able to interact with a printer you own without requiring the manufacturer's middleware. Whether that principle is achievable in practice with Bambu Lab's current hardware is another question.
Bambu Lab has not issued a public statement specifically about the Jarczak situation or the cease-and-desist letter. The company's stated rationale for the Bambu Connect requirement was protecting cloud infrastructure from approximately 30 million unauthorized daily requests and preventing third-party software from sending arbitrary commands to printers. Bambu Lab has previously published a blog post defending its AGPL compliance regarding the closed networking plugin.
Bambu Lab printers remain technically excellent — fast, capable, and well-engineered. The dispute does not change that. What it should change is your expectations about long-term ecosystem openness. If you value full software control, community-modifiable firmware, and guaranteed third-party interoperability, Klipper-based printers (Voron, Bambu-alternative builds, various CoreXY machines) are more aligned with that philosophy. If you want the best out-of-box experience and are comfortable with Bambu Studio as your slicer, the hardware is still compelling.
Community Matters in 3D Printing
We stay on top of everything happening in the 3D printing world — the good, the frustrating, and the contentious. Whether you need prints made or a printer diagnosed, Dreaming3D is San Diego's local resource.