I want to be clear about my position before getting into the detail. I use Bambu Lab printers. I like Bambu Lab printers. The A1 is an excellent machine and the ecosystem around it — Bambu Handy, MakerWorld, Bambu Studio — is genuinely well executed. None of what follows is written from a place of hostility toward the company or the products. It is written from a place of concern, because what has happened here in the last few weeks matters to anyone who owns a Bambu machine and cares about what they can and cannot do with it in the future.
The short version: Bambu Lab issued legal threats against an independent developer who restored direct cloud printing functionality to OrcaSlicer — functionality that Bambu themselves removed in a January 2025 firmware update. The developer shut down his project. The community is angry. And the incident has pulled into sharp focus a question that every Bambu owner should be thinking about: how much control over a machine you bought are you actually prepared to hand back to the manufacturer?
The background: what OrcaSlicer is and why it matters
OrcaSlicer is a free, open-source slicer maintained by developer SoftFever. Originally forked from Bambu Studio in 2022, OrcaSlicer grew into the community’s preferred slicer by shipping features — such as scarf seams, crosshatch infill, and built-in calibration suites — well ahead of commercial alternatives. For a significant portion of Bambu’s user base, OrcaSlicer is not a niche alternative to Bambu Studio — it is the primary slicer, preferred precisely because it moves faster than the official software and gives users more granular control over print settings.
The important genealogy detail: Bambu Studio is itself a fork of PrusaSlicer, released by Bambu Lab under the AGPL-3.0 open-source licence — a copyleft licence that requires any derivative work to also be open source. OrcaSlicer forked from Bambu Studio. The open-source chain runs directly from Prusa Research through Bambu Lab to OrcaSlicer. This licence context matters considerably for what follows.
January 2025: Bambu removes direct OrcaSlicer access
In January 2025, Bambu Lab pushed a firmware update that broke OrcaSlicer’s ability to send print jobs directly to Bambu printers over the cloud. Before that shift, OrcaSlicer users could send their slices directly to their Bambu Lab printers. However, Bambu Lab wanted users to route connections through its standalone app, Bambu Connect, which acts as a bridge to its printers.
Bambu Connect is a middleware application — a separate piece of software that sits between OrcaSlicer and the printer. Even after introducing Bambu Connect as a compromise, Bambu Lab severely limited user control. The middleware allowed OrcaSlicer to send print files but stripped it of the ability to modify printer or AMS settings. Users were forced to manually adjust speed, temperature, or filament colours directly on the printer’s touchscreen — a step backward for a community accustomed to full remote control.
OrcaSlicer’s developer SoftFever stated publicly that direct print sending from OrcaSlicer would not be supported going forward because they were not given API keys for Bambu Connect. Users were left with an unpleasant choice: update firmware and lose OrcaSlicer’s direct printing functionality, or stay on old firmware and never receive updates again.
Bambu’s stated justification for the change was infrastructure protection. Bambu Lab claimed the restrictions were necessary to protect its cloud infrastructure from roughly 30 million “unauthorised” requests per day, which it attributed largely to OrcaSlicer users. Security and infrastructure concerns are legitimate grounds for policy changes. The question the community began asking — loudly — was whether the solution Bambu chose was proportionate to that concern, or whether it served other interests.
April 2026: one developer fixes the problem
Independent developer Paweł Jarczak created a fork of OrcaSlicer called OrcaSlicer-bambulab. Jarczak’s fork of OrcaSlicer would have allowed users to bypass Bambu Connect, a middleware application that severely limits OrcaSlicer’s access to remote printer functions in the name of security. The fork released several versions, restored the direct cloud printing path, and gained traction quickly within the community.
Jarczak’s position was straightforward: he had used publicly available source code, had not redistributed Bambu’s proprietary networking plugin binaries, and had built upon Bambu Studio’s own AGPL-3.0 licenced codebase. The pathway his fork used to restore direct printing was, by Bambu’s own admission, simply one they had not yet disabled. “I explicitly pointed out that, according to Bambu Lab’s own explanation, the reason the method still worked was simply that they had not disabled that path yet,” Jarczak stated.
The legal threats arrive
Bambu Lab contacted Jarczak directly. The list of accusations included claims that the project impersonated Bambu Studio, bypassed authorisation controls, violated the Terms of Use, performed reverse engineering, and enabled a modified fork to send arbitrary commands to the printer.
Jarczak asked for specific technical or legal clarification — which code paths, which commits, which specific provisions. He said he asked Bambu Lab for more information, but instead received further broad accusations, including repeated references to “reverse engineering.” No precise technical response was provided. Rather than face a prolonged legal battle he could not afford, Jarczak voluntarily removed the project from GitHub. He insists he did nothing wrong as his fork of OrcaSlicer only used publicly available source code.
The accusations deserve scrutiny. Impersonation of Bambu Studio is a serious charge — it implies Jarczak’s fork was presenting itself as official Bambu software in a way that could deceive users. A fork clearly labelled “OrcaSlicer-bambulab” on GitHub by an independent developer does not obviously meet that description. Reverse engineering is equally charged — but building on open-source code released under AGPL-3.0 is, by definition, explicitly permitted by the licence Bambu chose to release Bambu Studio under. The AGPL-3.0 licence exists specifically to enable derivative works. Bambu Lab’s legal team called it “unauthorised modification of proprietary firmware.” The developer called it “enabling functionality the hardware is physically capable of.” Both are technically correct, which is why this fight is so interesting.
The broader pattern: this is not an isolated incident
The OrcaSlicer controversy did not begin with Jarczak’s fork. It began in January 2025 and has been building since. The Authorization Control System announced on January 16, 2025 gated print initiation, motion control, fan and hotend temperature control, and AMS configuration — a substantial list of controls that users had previously exercised freely through third-party software.
Jarczak’s situation is also not limited to OrcaSlicer. He also maintains firmware for the Bambu Multi-Color Unit (BMCU), a DIY alternative to Bambu Lab’s official AMS. He warned that the BMCU project faces a growing risk of being locked out of the Bambu ecosystem and is now pivoting to develop Klipper-based printer firmware. The same ecosystem closure that affected OrcaSlicer threatens community hardware alternatives too.
The community reaction has been sharp. People took to the Bambu Lab subreddit to air their grievances with the company, with one commenter calling it the “Nintendo of 3D printing.” The Nintendo comparison is pointed — Nintendo is known for aggressively defending its intellectual property and closed ecosystem even against uses that the broader creative community would consider legitimate. Being compared to Nintendo in a community built around open-source values and the spirit of maker culture is not a compliment.
The timing adds a layer of context too. The legal action against the fork arrives as Bambu Lab faces mounting pressure on multiple fronts, including a patent infringement case brought by Stratasys and a recently settled copyright dispute with Pop Mart. A company facing legal pressure from multiple directions and simultaneously deploying legal threats against an individual open-source developer is a pattern that does not read well regardless of the merits of any individual case.
The legitimate security argument and its limits
It is worth giving Bambu’s security argument a fair hearing before dismissing it entirely. Thirty million unauthorised requests per day from OrcaSlicer users is a real infrastructure concern. A manufacturer has legitimate interest in controlling what software can issue commands to their printers — a malicious fork that sends arbitrary commands to a printer’s motion system could cause physical damage, and Bambu cannot audit every third-party implementation for safety.
These are reasonable positions. The problem is not the existence of the security concern. The problem is the response chosen and the way it was applied. The dispute has become sensitive because it sits between two legitimate concerns. One side involves a company’s interest in security, authorisation, and system integrity, while the other involves users’ and developers’ expectation that software remain flexible and interoperable.
A security-focused response that served users as well as the company would look different. It would involve publishing a clear API for authorised third-party access. It would involve working with OrcaSlicer’s developer rather than shutting off access unilaterally. It would involve Bambu Connect being a transparent bridge that maintained full user control rather than a middleware layer that reduced it. None of those things happened. What happened instead was a firmware update that broke third-party access, a middleware replacement that reduced functionality, and a legal threat against an individual developer who fixed the problem for free.
What this means for Bambu owners today
My honest assessment: this does not affect my current workflow right now. I use Bambu Studio as my primary slicer and Bambu Handy for remote monitoring. The OrcaSlicer direct printing change does not directly impact how I use my A1 today. I want to be transparent about that.
But I find it disappointing. Not because of what has been taken away from me specifically, but because of what the decision signals about Bambu’s direction. A company that builds on open-source foundations, benefits from the ecosystem those foundations enabled, and then uses legal threats to prevent the open-source community from maintaining the interoperability that made the product attractive in the first place — that company is making a bet that its products are valuable enough to survive the goodwill cost of that position. That may be true today. It may not be true in three years.
The practical concern for any Bambu owner is the precedent. Bambu Lab pushed a firmware update that disabled certain advanced features on their 3D printers — features that were available when customers purchased the hardware. If a feature existed when you bought your machine and was subsequently removed by a firmware update, the question of whether you “own” that feature or merely had temporary access to it is not a comfortable one. The answer, in a world where manufacturers control firmware updates and can issue legal threats against anyone who restores removed functionality, leans toward the latter.
The alternative ecosystem options become more appealing in this context. The Snapmaker U1’s Klipper-based firmware is open-sourced. The Anycubic Kobra X runs Anycubic Slicer Next but is also OrcaSlicer compatible with no middleware requirement. Prusa’s ecosystem has an established history of openness. These are not automatically better machines than Bambu’s — the A1 is still excellent at what it does. But ecosystem openness is now a legitimate factor in a purchasing decision in a way that it perhaps was not eighteen months ago.
I suspect this will be off-putting to potential buyers who were weighing Bambu against alternatives. The community around a printer matters as much as the machine itself for many hobbyists — the ecosystem of shared profiles, third-party tools, custom firmware, and community development is part of what makes a platform worth investing in. Bambu Lab is eroding trust in that community dimension, and once that trust is gone it is difficult to rebuild.
What has not changed
It is worth being clear about what this controversy does not change. The A1 remains a fast, reliable, excellent machine for PLA and PETG printing with AMS multi-colour capability. Bambu Studio is a capable slicer that receives regular updates. MakerWorld is a well-stocked model library with good Bambu printer integration. Remote printing via Bambu Handy works well. The hardware quality has not changed and the core user experience for anyone using the official Bambu toolchain is not materially affected by the OrcaSlicer situation.
The concern is not about what Bambu is today. It is about the direction the company appears to be heading, and what that direction means for the longevity and value of the hardware investment. Printers last years. Ecosystems change. The trust relationship between a hardware manufacturer and its community, once damaged, is slow and difficult to repair.
What Bambu Lab should do
This is straightforward. Publish a documented, stable API for third-party slicer access that provides the same level of printer control that Bambu Studio has. Allow authorised third-party slicers — OrcaSlicer at minimum — to communicate directly with Bambu printers without middleware limitations. Engage with the open-source community as a partner rather than a threat. If security is the genuine concern, a published and authenticated API addresses it more effectively than middleware that reduces functionality for legitimate users while determined bad actors find workarounds anyway.
The community that made Bambu Lab’s machines popular — that contributed profiles, wrote guides, made YouTube tutorials, recommended the machines to friends, and built the word-of-mouth reputation that drove the growth — is the same community currently expressing serious concerns about the direction of the company. That is worth paying attention to.
Where do you stand on this? Are you a Bambu user who has already switched from OrcaSlicer to Bambu Studio as a result of the access changes? Or are you on old firmware, holding out? Does this change how you think about future purchases? Drop a comment below — this is a conversation the community needs to keep having.
