If you own a Bambu Lab printer and you've seen phrases like "cease and desist," "AGPLv3," and "Software Freedom Conservancy" flooding your Reddit feed over the last few weeks — you're not alone in feeling lost.
This isn't a legal article, and we're not going to pretend it is. What we are going to do is explain exactly what happened, what it means for your printer right now, and whether you should be worried going forward. No legal jargon. No corporate PR spin. Just the facts, written for makers who want to keep printing.
Background: Bambu Connect and the January 2025 Firmware Update
To understand this fight, you need to go back to January 16, 2025 — when Bambu Lab pushed a firmware update introducing something called the Authorization Control System, or ACS.
Before that update, you could send print jobs directly from third-party slicers like OrcaSlicer to your printer over your local network. No middleman. No cloud required. Just your computer talking to your printer.
After the update, that changed. Bambu introduced Bambu Connect — a closed-source middleware application — and required users to route print jobs through it. The result: OrcaSlicer's direct-connect functionality was effectively broken for Bambu printers. The official OrcaSlicer project (SoftFever) publicly stated they would not be supporting direct print-sending going forward, because Bambu hadn't given them API keys for Bambu Connect.
For most casual users, this was a minor inconvenience at worst. For power users, Linux users, and anyone who'd built workflows around direct LAN printing, it was a significant step backward. The community grumbled. Bambu said it was for security. Life moved on — until April 2026.
What Paweł Jarczak Built — and Why It Mattered
On April 23, 2026, a Polish developer named Paweł Jarczak published a fork on GitHub called OrcaSlicer-bambulab. His fork did one thing: it restored the ability to send print jobs directly to Bambu printers without going through Bambu Connect.
Importantly, Jarczak built this using publicly available source code. Bambu Studio — Bambu's own slicer — is released under the AGPLv3 open source license, which means anyone can use it, modify it, and redistribute it, as long as they follow the license rules. OrcaSlicer itself is also AGPLv3. Jarczak wasn't hacking anything. He was working within a legal open-source framework that Bambu itself chose.
The fork wasn't huge. It was a niche tool for technically-minded users. But it worked, and people appreciated it.
The Cease-and-Desist
In April 2026, Bambu Lab sent Jarczak a private cease-and-desist letter. The accusations were serious:
- That his fork was reverse engineering Bambu's software
- That it was impersonating Bambu Studio
- That it bypassed their authorization controls
- That it violated their Terms of Use
Jarczak rejected all of these characterisations publicly — pointing out that he'd used only publicly available code and hadn't modified anything that wasn't already open. He asked Bambu to specify exactly which files or commits were at issue. They didn't.
Faced with the financial reality of a legal fight against a well-funded company, Jarczak did what most solo developers would do: he took the project down. He made clear he was doing so reluctantly, and that he believed he had done nothing wrong.
On May 7, Bambu published a blog post attempting to clarify their position. They acknowledged that AGPL forks of Bambu Studio are technically permitted — but argued this particular case was about "cloud access" and "impersonation," not the open-source license itself. The community wasn't buying it.
GamersNexus, Louis Rossmann, and the Community Backlash
At this point, the story stopped being about one developer and became something much larger.
GamersNexus — one of the most respected hardware publications in the world — rehosted OrcaSlicer-bambulab with Jarczak's permission, openly daring Bambu Lab to sue them. They offered $10,000 USD in legal support to Jarczak if Bambu pursued action. Louis Rossmann, the right-to-repair advocate, did the same — contributing another $10,000 and uploading the fork to his own GitHub.
Rossmann's legal analysis was pointed: Bambu's software uses the AGPL license, which explicitly permits anyone to use and fork it. Jarczak hadn't modified any code — he'd used Bambu's own source, as the license allows. The cease-and-desist, in Rossmann's view, couldn't win in court.
Jarczak himself declined the offer — he didn't want the extended legal stress — but the code was already out. The message from the community was clear.
The Software Freedom Conservancy Steps In
On May 18, 2026, the Software Freedom Conservancy (SFC) — a nonprofit dedicated to protecting open-source software — announced a formal investigation into Bambu Lab. Their findings were significant: two confirmed AGPLv3 violations.
libbambu_networking alongside Bambu Studio for years — without releasing its source code. The AGPLv3 license requires all corresponding source code be made available. Bambu wasn't doing that.The SFC didn't stop at publishing findings. They launched a funded project called "baltobu" with three active arms:
- Reverse engineering Bambu's proprietary networking library to produce an open-source replacement
- Maintaining Jarczak's OrcaSlicer fork as the canonical community version — with Jarczak involved as a collaborator
- Developing "viscose" — an entirely independent fork of Bambu Studio
They also announced a standing committee, launching in June 2026, to bring together manufacturers, users, and open-source experts to address software freedom issues in 3D printing long-term.
Bambu Lab Backed Down
Under the mounting pressure — from the community, from GamersNexus and Rossmann, and now from a formal open-source nonprofit investigation — Bambu Lab backtracked.
The company issued a statement expressing regret over how the situation was handled, acknowledging that their reference to Terms of Service overriding AGPLv3 was incorrect. It was the kind of corporate partial-apology that stops short of admitting full fault, but the practical outcome was clear: the pressure worked.
What This Means for You and Your Printer
Let's be direct about the practical questions most Bambu owners actually have.
The Bigger Picture
What makes this story worth paying attention to — even if you never use OrcaSlicer and don't know what AGPLv3 means — is what it reveals about the direction of consumer 3D printing.
Bambu Lab makes genuinely excellent printers. The A1 Mini, the P1S, and the H2D are some of the best consumer machines ever built. They've done more to bring 3D printing to mainstream households than arguably any other company in the last decade.
But excellent hardware and community-friendly software policies aren't the same thing. The Authorization Control System, Bambu Connect, and now this legal episode all point toward a company that is increasingly treating its ecosystem as something to control rather than something to empower. Every printer that requires cloud authentication to print is a printer that depends on the manufacturer staying solvent, staying honest, and keeping the servers on.
That's not unique to Bambu. Apple, Tesla, John Deere — this is a familiar pattern in hardware. What's different in 3D printing is that the community is particularly technical, particularly vocal, and — thanks to open-source licensing — has real legal tools to fight back. The SFC stepping in changes the calculus permanently.
Where Things Stand Right Now
Your printer still works. The community is organised and fighting. And the era of assuming your hardware company is also your friend is, quietly, coming to an end. We'll keep tracking this as it develops — subscribe to the weekly newsletter below for updates as they break.
This article reflects publicly available information as of May 31, 2026. We welcome corrections — contact us here.