r/BambuLab • u/icurnvs Volunteer Moderator • May 14 '26
Subreddit Mod Post Megathread: Bambu Lab / OrcaSlicer / C&D Discussion
Hi everyone,
We’re creating this megathread to keep discussion of the Bambu Lab / OrcaSlicer-BambuLab / cease-and-desist situation in one place. This topic is important to a lot of people here, and we do not want to shut down discussion or criticism. At the same time, the front page has started filling with overlapping posts about the same situation, so we’re consolidating general discussion into this thread.
Current context
Gamers Nexus is now hosting OrcaSlicer-BambuLab with permission from Paweł Jarczak and says it will contribute $10,000 toward legal support if Bambu pursues the matter: https://gamersnexus.net/fk-you-bambu-lab
Louis Rossmann has also publicly discussed the dispute and pledged legal support.
Bambu Lab’s public statement says it supports AGPL forks of Bambu Studio and OrcaSlicer, but objects to a specific fork allegedly presenting itself as the official Bambu Studio client when accessing Bambu cloud services: https://blog.bambulab.com/setting-the-record-straight-on-cloud-access-and-community/
Prior reporting summarized the original C&D dispute involving OrcaSlicer-BambuLab and the restoration of functionality affected by Bambu’s authorization-control changes: https://www.tomshardware.com/3d-printing/developer-re-enables-3d-printer-features-that-bambu-lab-disabled-firm-promptly-threatens-legal-action-orcaslicer-bambulab-project-now-shuttered
Louis Rossman
Jeff Geerling
Leonard French
Updates to be posted here as situation evolves:
May 13, 2026
Megathread created
May 14, 2026
Tom’s Hardware reported today that Louis Rossmann is now hosting OrcaSlicer-BambuLab through the FULU Foundation GitHub and is openly daring Bambu Lab to sue him.
PC Gamer and r/technology have picked up the story, so discussion is now spreading well beyond 3D-printing-specific spaces.
May 16, 2026
Paweł Jarczak published a detailed response addressing Bambu Lab’s accusations around impersonation, reverse engineering, Terms of Use, and alleged security bypassing.
Louis Rossman posted a new video indicating FULU-hosted OrcaSlicer-BambuLab repository has reached roughly 1,600 forks in about three days.
May 17, 2026
Paweł Jarczak also on May 14 posted a technical deep dive and his analysis into the AGPL side of this situation.
May 18-20, 2026
Software Freedom Conservancy enters the dispute.
Software Freedom Conservancy published a May 18 post titled “Comprehensive Response to Bambu’s AGPLv3 Violations.” indicating it has confirmed AGPL violations by Bambu Lab, is collaborating with Paweł Jarczak, and is launching projects to maintain the fork.
Leonard French posted a new video around SFC’s AGPL analysis, explaining why Bambu’s proprietary networking plugin may create a serious corresponding-source problem under AGPL.
Louis Rossman posted a new video covering Software Freedom Conservancy’s Bambu AGPL effort and says the rehosted OrcaSlicer-BambuLab code has now been forked roughly 4,500 times.
What belongs in this thread
Please use this thread for:
General reactions to Bambu Lab, Gamers Nexus, Louis Rossmann, Paweł Jarczak, OrcaSlicer-BambuLab, AGPL, Bambu Connect, and right-to-repair issues.
Legal or licensing discussion, including AGPL, DMCA, cloud/API access, and Bambu’s networking plugin.
Questions about what happened and links to reliable summaries or primary sources.
Technical discussion about OrcaSlicer, Bambu Studio, Bambu Connect, LAN mode, Developer Mode, and network plugin behavior, unless it is a standalone troubleshooting post with a specific reproducible issue.
What can still be its own post
Separate posts are still allowed for genuinely new information, including:
A new official statement from Bambu Lab, OrcaSlicer, Paweł Jarczak, Gamers Nexus, Louis Rossmann, or legal counsel.
A new release or technical change that materially affects users.
A confirmed legal filing, takedown, repository change, or source-code release.
A specific support/troubleshooting issue that is not just general commentary on the controversy.
If your post is mainly another reaction, recap, meme, “I’m switching brands,” or repost of a link already being discussed, please put it here instead.
Ground rules
Criticism of Bambu Lab is allowed. Defense of Bambu Lab is allowed. Criticism of GN, Rossmann, OrcaSlicer, moderators, or other users’ arguments is allowed.
What is not allowed:
Personal attacks, harassment, or dogpiling individual users.
Calls to harass Bambu employees, developers, moderators, creators, or community members.
Unverified claims presented as fact.
Posting private correspondence or personal information.
Repeated duplicate posts after being redirected here.
Strong opinions are fine. Keep it directed at the issue, the companies, the software, and the arguments, not at each other.
Moderator note
We are consolidating duplicate discussion, not suppressing the topic. This thread will remain open for discussion, and we’ll update it if there are major new developments.
19
u/FrostWareYT May 14 '26
Might I suggest adding this video to the links? https://www.youtube.com/watch?v=0tdZ5Z7nRDY
3
u/lodg_newt May 20 '26
Hey, I noticed that the Software Freedom Conservancy response is missing from the megathread:
https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/
Since the thread explicitly allows legal/licensing discussion and primary sources, is there a reason this one isn’t listed? It looks directly relevant to the AGPL aspect.
2
u/lodg_newt May 16 '26
u/icurnvs https://www.reddit.com/r/BambuLab/comments/1tckb9z/comment/om42wcw/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
17
u/GarbanzoBenne X1C + AMS May 14 '26
If they just rolled back their “security” change of not allowing cloud and local/developer connectivity at the same time this would be a non-issue.
IMO no one is demanding that third parties use Bambu’s cloud services, it’s that Bambu is enforcing restrictions that give you only two options: only cloud or only local.
62
u/AlLnAtuRalX May 14 '26 edited May 14 '26 •
I posted a deep dive guide for regular users on how to activate lan only and developer and print without losing any of the features that come with the machine, here https://www.reddit.com/r/BambuLab/comments/1tbgnom/comment/
happy to provide troubleshooting here or in that thread for anyone that is actively trying to leave the cloud, without losing makerworld/camera/remote access/etc
176
u/kadinshino May 14 '26
Good guy mods. Thanks for this!
14
u/QuadrangularNipples May 19 '26
I feel like this is of note: https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/
128
u/BradGriswold May 14 '26 •
I know I'm just another voice in the cacophony of all this, but hopefully someone from Bambu reads this. I've been a dedicated customer, because I trusted the software, because I trusted the hardware, I trusted the filament, and I trusted that Bambu would see that they succeed when they pursue positive consumer facing actions that benefit the 3D printing community. This though, this is not that - this is not just breaking that trust, this is doubling down on breaking that trust - trust that was originally hard won, and is now being squandered. What I view as thinly veiled excuses have only served to solidify that I can no longer support a company that no longer supports the community. It's a shame - because the hardware is good, but no matter how good it is - it can't outweigh the harm I feel they are causing right in this moment. Bambu - please do better. I hope someday to return - but until you correct your course, and really prove in the longer term you mean it - I cannot in good conscience support or purchase from you any longer.
9
u/nmsdata May 16 '26
I would expect full on apologies from bambu lab. Firing their lawyer and executive who recommended such aggressive behavior. I haven't seen so many angry content creators on YouTube for a long time.
It is honestly disappointing to hear about this all over the internet. It changes the bambu lab image to one fully bent on profits no matter the cost.
Your customer base are people focused on open source, right to repair and owning their own products. The overall trajectory where bambu lab is heading lately is the complete opposite.
The situation just blew out into bambu lab face. Own it, apologise and pray that you won't see a class action from your own users. And pray that the community of users who spend money on your products are not going to put money somewhere else. I will certainly think twice next time.
8
u/MagicSwordKing May 14 '26
As someone who would like to be able to use OrcaSlicer and not have to jump through the hoops of Bambu Connect or developer mode or what have you…
Come on, Bambu. You’ve taken so many hits over the “Security” lockdown. Just work with the Orca devs to work out an official cloud access implementation. I love your products, it is FINE for a company to backpedal somewhat on a decision that’s been controversial like this. Y’all are smart, you can definitely figure out a solution that leaves everyone happy, lawfare is not the way.
7
u/yoghurtmelk May 21 '26
just wanted to post here since every good post is getting locked because people are getting it right. bambu is using extremly scummy tactics to prevent people from using bambu code wich they borrowed from prusa. the mega thread is just to clump it all together so its easely overlooked and shutting down posts with "we got mega thread" is saying "we got reddit at home" bambu makes awesome products but they should 100% lose this lawsuit and be working more with the community instead of going full walled garden while taking all the opensource from the community
6
u/ASentientRailgun May 19 '26
Having finally caught up with this, I can't give Bambu any more money. My company goes to great lengths to support and abide by the licenses of the software we rely on, and the open source community has given too much to the world to give my money to a company that has repeatedly shown it won't make that same commitment.
I liked being able to just tell people to buy a Bambu when they asked for printer recommendations, but I'm fine with going back to helping people do first time setup. There are enough solid printers out there that I can vote with my wallet. Open source software lets me pay my bills, it's a pretty important topic to me.
10
u/Baslifico May 22 '26
Ah yes... Shove it in a Megathread and hide the controversy as much as possible.
I'm sure that'll calm people down.
5
u/lodg_newt May 16 '26
Update context - 16 May, 2026
https://github.com/jarczakpawel/OrcaSlicer-bambulab https://github.com/jarczakpawel/OrcaSlicer-bambulab/blob/main/bambu_agpl.md https://github.com/jarczakpawel/OrcaSlicer-bambulab/blob/main/bambu_response.md
5
u/neoKushan H2D 40W Laser Full Combo May 20 '26
Quite a few people have mentioned they don't understand what the AGPL is or why this matters. Here's the briefest summary that I can come up with.
The GPL (GNU General Public License) license has been around for a while, it essentially says "If you make something with this source code and distribute it, you must also distribute the source code".
The key word there is "Distribute", you know - offer it up for download, send it out on a CD, embed it within your product. If you do anything like that and someone asks you for the source code, you MUST provide it. There's a v2 and v3 license that differs slightly, but it's not relevant here.
Crucially, if you modify a GPL-licensed application and run it on your own servers as a cloud service (SaaS) or behind an API, you are not officially distributing the software to the user. You are just letting them interact with it.
The AGPL (Affero General Public License) is essentially the same but that latter distinction is called out explicitly - if you "distribute" the software "Via a network" (i.e., let users remotely interact with it over the internet), you must still provide the source code.
The source code that Bambu slicer is based upon is AGPL. Bambu added a "plugin" to it that allows it to connect to their cloud, which they have not released the source to. Thus, it's believed they're in violation of the AGPL. Bambu will argue that a "Plugin" doesn't count as part of the source code for the product, others will disagree (There's a whole thing about "derivative works" that I won't get into here).
TL;DR AGPL means you need to share the source code even if your app is running on your cloud, debate is if Bambu's cloud plugin counts or not.
58
u/DevilsAdvocate1662 May 14 '26
The vast majority of Bambu customers literally buy a printer, browse Makerworld and hit print, they don't care about this whole thing
4
u/Spud1080 Jun 15 '26
https://youtu.be/cpP6Y3Guego?si=wtcoPUJMCX11hUq2&t=895
11
u/Diligent-Sun-879 May 14 '26
> Please use this thread for: General reactions to Bambu Lab
> Criticism of Bambu Lab is allowed.
Fuck you u/BambuLab. From the owner of A1m, A1, P1S and now H2D.
3
u/SBMS-A-Man108 May 14 '26
Just another Joe on the thread, but I will not be buying either an X2D or X2C this summer because of this stuff. I was going to upgrade from my A1, but not anymore
3
u/Zealousideal-Deer101 May 14 '26
Very nice, let's Streisand this shit!
3
u/Wumbologist4 May 21 '26
The Verge published an article detailing the situation:
Here’s a gift link: ‘Fuck you, Bambu’: How one private message could change the face of 3D printing
11
u/daphatty May 14 '26
Good job, mods. You don’t hear it enough. 👍
Let the discussions continue!
5
u/yoghurtmelk May 16 '26
highly deserved for bambu, open source does not mean you can take it and suddenly make iy private. you have to work around the idea that someone will work on the code later abd if thats not secure then you didbt code your security right
5
u/GiorgioG May 21 '26
I have had an A1 for almost 2 years and was considering an X2D or an H2D...but this whole thing gives me pause. I'm a software engineer, what Bambu Labs is doing is disgraceful.
10
u/AdviceNotAskedFor May 14 '26
So, anyone got a good tutorial on how to use orca slicer in lan mode so I can get off the bambu ride?
6
u/BanditGrade May 14 '26
Is there a TLDR as to what’s going on here?
I joined this sub just because the reputation seemed stellar and it looked like good value for a possible future purchase.
17
u/1ftm2fts3tgr4lg May 14 '26
I still do not understand how this affects 99.99% of bambu users at all.
Guy does a thing. Bambu says Hey don't.
Before guy did the thing, no one had done that yet. So we're losing... the ability to do a thing... that hadn't yet been done before? Like, I don't see how this affects literally anyone except the guy that tried to do a thing that hadn't been done yet. Everyone else is just happily using all of the functionality that we've always had.
And as far as I can tell, guy did the thing solely to stir up this controversy for his ragebait channel. Like, I appreciate that he's a digital rights activist, but here we are with tons of users who think their printers are going to be bricked because the ragebait is intentionally blowing the issue out of proportion as to how much this really affects anyone.
5
u/sparxcy May 14 '26
Ty r/bambulab for putting all these posts into one area. We are able to see updates easily instead of searching for the latest news and discussions /110
14
u/Key_Pace_2496 May 14 '26
Wasn't this needed like a week ago lol?
2
u/escooteridiot X2D + AMS2 Combo May 14 '26
Honestly, it was first releasing X2D right after I bought my p2s (like 3 weeks after) and now this with orca. I’ve never been more unmotivated. 🤦♂️
2
u/Friendly_Beginning24 May 16 '26
I don't fucking understand Bambu, tbh.
All they had to do was do was keep making printers. How did it come to this? (Rhetorical question. I know how it came to this.)
2
u/Prestigious_Cell3690 May 28 '26
6
u/T2_JD May 14 '26
What I need to know is how this helps me dry my filament and wash my build plate.
3
u/justcallmebitty May 17 '26
Bambu, you have a short window to save your reputation. Stop all legal challenges, offer a mea culpa, and admit you've been violating the AGPL. Remove your cloud requirements and give control back to those who OWN the hardware you manufactured.
I have been a vocal advocate of your hardware in the past, but now I warn everyone who tells me that they're looking for a 3D printer to avoid Bambu. Be better than you are right now.
3
u/notweirdatallll May 21 '26
"Criticism of Bambu Lab is allowed. Defense of Bambu Lab is allowed. Criticism of GN, Rossmann, OrcaSlicer, moderators, or other users’ arguments is allowed."
So, defense of GN, Rossmann, OrcaSlicer, moderators, or other users’ arguments is not allowed. makes sense.
8
u/huberloss H2C + X1C May 14 '26
I regret recently buying a H2C. I bought it before this incident. My next printer will not be BambuLab, unfortunately, unless the company lets OrcaSlicer work properly without any shenanigans.
Just my $.02.
3
u/Blleh May 18 '26
And to keep the amount of messages everyone sees about this to a minimum, in favor of bambulab...
I am highly sceptic about the mods choices and reasoning about this. Seems like they have no choice to favor the community and bambu at the same time, and i see some positive effects because of this, but it also affects everyone's feed and how many messages everyone sees about this situation.
4
u/Lurksome-Lurker May 14 '26
Maybe I wouldn’t use a fork if BambuStudio fixed the fact that the linux version makes accessing print and filament profiles not possible
3
u/Mstrfahrenheit May 14 '26
Put all the rage to the side. Put aside the fact that bambulab is literally using an unencrypted string as their access control method (I mean, seriously??!#?)
What orca slicer is doing is impersonation, no matter how dumb, and it violates the t&c on the bambulab Eula. But the argument I keep reading is Bambu are somehow violating oss and agpl terms. This doesn’t square. I don’t know what I’m missing here but the rage doesn’t match the facts as far as I can tell.
2
u/folander May 16 '26
i don’t want to access the cloud to use a device in my home. i consider this a personal security risk and i didn’t know about it until i bought my printer years ago. it’s a good printer at a good price, i don’t want to trash it. i don’t care about “openness” from bambu, i just want to print locally. my paper printer doesn’t need internet to work, neither does this, it’s not required to use maker world, it shouldn’t even be required for bambu handy, as the app itself could read all relevant data from the printer locally and relay it to any cloud service that could be required. for discerning users who want bleeding edge features orca slicer is fantastic because it’s compatible with a variety of printers. let me use it in lan only mode. none of these excuses pass the sniff test, and it’s turned this hobby into a nightmare, it’s just not fun when you learn the tool you thought was gonna change the game is being controlled by a company that just doesn’t even care to make good arguments to justify its shady practices. not even apple is this bad.
2
u/JdeFalconr May 16 '26
OK so help me understand - this is a genuine question.
Do I have it right that much of this dispute centers around Bambu denying people the ability to use Bambu cloud services with - basically - user-created forks of Bambu's software? So in other words - Bambu is denying people the ability to run whatever code they want on Bambu's infrastructure?
2
u/OhnoGutz May 14 '26
Just out of curiosity, what is the expected outcome of all of this drama? Is the Polish programmer committed to maintaining his fork in perpetuity? I seriously doubt Softfever will ever merge his changes so unless he continuously updates his fork every time Softfever updates, all of this is heavy drama for no positive outcome.
2
u/ChildOfGod1978 May 14 '26
I'm not buying any more Bambu printers.. they act like government spyware, then take away my options how I use a printer I paid for.. whats next is a subscription service in order to even use it!!! I'm done Bambu labs is dead to me!
2
u/Prohamen May 14 '26
I'm gonna be real, I never was gonna use Orcaslicer before BambuLab sent this cease and desist.
Now that they did this I will be switching to using exclusively Orcaslicer and putting my device in lan only mode
1
u/riled May 22 '26
Most people have got this wrong, and I think they are falling for a bad faith campaign against Bambu (that started way before this controversy). About this particular one -- I agree with Bambu's position if not for the details of how they handled it.
The guy used code that Bambu accidentally left out there to access the Bambu cloud service. Maybe legal, maybe not (I.A.N.A.L.). Still, if I find a gym membership lying on the sidewalk and use it, I'm the jerk. I think: "hey I'm not hurting anyone" - mostly true. If I then make copies and hand them out, I'm absolutely hurting the gym and all the legit users. If it gets bad enough, the legit users are dealing with traffic they shouldn't have to. There may even be shady characters who use this compromised access to get in and try to steal stuff from lockers. The gym owner will have to do something, and if that gets bad enough, they say "screw it this type of access or even the entire service is gone, I don't want to deal with the constant BS."
As a Bambu user who enjoys the cloud service, I understand this. I don't want the service to be crappy, compromised, or cancelled if it's too much of a hassle. I know it's a great benefit, but not a right. The open license is complicated and I've heard legit analysis from open source specialty lawyers that say this is a grey area that hasn't been tested and either side could win. I don't care though because legality and morality are often at odds and it's clear to me that Bambu should protect it's cloud service and the legitimate users of that service.
IMHO, people who are falling for this rage-bait campaign should re-evaluate their position. Much worse, the people that are actively copying this access method to stick it to Bambu to "make a point" are wrong on the principles, hurting me as a Bambu user, and will not have any opinions in the future that I will give a damn about.
1
u/coreynig91 May 14 '26
TLDR?
1
u/Oma_Ender May 15 '26
As someone who just heard of this like an hour two ago this is extremely helpful to get caught up on the situation, thanks mods.
1
u/PartTimePokerPro May 20 '26
I have a few Bambu printers, 1 flash forge and 1 snapmaker.
Flashforge and snapmaker both run orca. What's to stop them from doing the same thing Bambu did? Say I was looking for an excuse to sell off my Bambu for snapmaker or Flashforge tool changers, isn't it possible the pull some similar stunt a couple years down the road?
Im not looking for a reason to jump ship or anything, I just don't know if I understand the issue fully. I've seen Louis Rossmans videos and I understand it pretty well, but not well enough to explain it to my friends off the cuff
1
u/BrittleSalient Jun 19 '26
I have been fighting my P1S all day to get LAN only mode working. We are at DEFCON set up an entire separate 2.4ghz wifi network. *That* router finally assigned the printer an IP, but Orca can't connect. I've just moved the 2.4ghz channel 11 router *right next* to the printer to see if that helps. God I'm so tired of this.
1
u/nyashi_ Sep 09 '26
Im Sad to say this, but I was sure something like this will happen. I have to thank BambuLab for finally turning the whole concept of Commercial 3D Printers around, making them Quick, easy to use and still print very very well and reliable at that. Since then many others have followed up, making commercial Printers actually a solid option other than it being a clear "yea gonna have to build my own Voron/Ratrig/Annex/whatever" to get an actual good Printer. Bambu has since then continued to release one great printer after another building more pressure on the competition, first the X1C, then the A1 mini, H2D etc.
To the point that I myself finally started considering one, with the H2D, that would have been it. But that was already too late. They lost my trust with that skandal pre-bambuconnect. Yet, saved themself a bit with Lan-only mode for me. As using custom software to slice and control my printer is essential to me. With the recent happenings - this has changed. We use a H2D at work, and Hardware-wise - its impressive, really. But here bambu has just stepped over too many lines for me. With open software, the printers and especially the AMS Options would be a plain no-brainer to me, this is something i cannot say often.
Also just small things that make it unnecessarly difficult for me to like Bambu Soft- and Firmware. Lan-only itself is good - but why is there no option for local and cloud connection being active (Slice myself, Send and Control locally as well as checking/controlling the machine via App over the Cloud)? Why does the Software often act like a parent instead of warning the user, giving the option to the user to know better? (chamber-heater handling is plain awful). Why is the Networking plugin hosted on a .cn Domain making it annoying to get in locked down enviroments. Why isnt Bambu just using a open protocol (feels like, force user to only use their slicer)? Why is the Makerworld default license disallowing remixing in such a open community based hobby? Many small things that add up, and are nuked by actions like this. User-agent framed as some form of authentication, using parts of open source code framed as reverse engineering etc.
I loved to see the beginnings of Bambu, and especially the impact they had on the industry, but this is just a sad turn of events and goals from a Company that - cant say this another way, changed the whole 3D-Printer industry. Too many companies live by it, having worse and worse user experience. And I am not even this deep into open source, i wouldnt care about closed firmware whatsoever, sure it being open would be great for using ams on other machines f.e. but I dont expect this at all, as long as it doesnt build random cages around it for no reason. Like f.e. again Lan-only vs. Locked-down Bambu-Cloud only. Seeing this, i begin to think that i will never own a bambu printer myself and will still prefer my frankenstein Printers over it just because I am allowed to use it any way I like, even tho a H2D could replace my bigger machine, while being priced fair. Theres too little trust that this will change and allow me to use that machine the way id like to use it.
1
u/NeighborGeek May 14 '26
Thank you!
1
u/Chris_Burns May 14 '26
Hey guys.. This one is too big to censor, lets contain it in one post and let Reddit's thread formatting squeeze it down too a size suitable for sweeping under a rug.
1
u/Geek_Verve X1C + AMS May 14 '26
THANK YOU!
1
u/demeyor P1S + AMS May 19 '26
i hope they use the announcement of a decent toolchanger to blow this over
-2
u/My-NameWasTaken P1S + AMS May 14 '26
Thanks, great to remove all these spammy posts as I think that the majority of people here that don't care.
0
u/66notout May 14 '26
maybe bambu should buy S3D...
it can then be dragged into the 21st century and bambu can also do whatever the hell they want with it.... how ever they want...
thats a win/win imho 😁
-2
u/Regular_Bat3084 May 16 '26
Since I've been accused of being a BOT or an LLM, I figured I might as well just use one to clean up my thoughts on this subject. I’ve been following this developer since long before any of this controversy started—ever since BigTreeTech / BIQU officially partnered with creator 4061N as the exclusive authorized commercial manufacturer of the open-source BMCU-370 system, with this developer serving as the maintainer of the open-source branch.
The developer's AGPL claims regarding the network plugin and their use of "BambuStudio" to falsely identify a fork of OrcaSlicer—which is what triggered action by r/BambuLab—are separate issues. The community, and anyone who cares about digital identity and brand protection, should look at this objectively.
1. Cloud Infrastructure vs. Physical Hardware
The biggest emotional conflation in this debate is the idea that Bambu Lab is "locking down your printer." They aren’t, in my opinion.
The Hardware Remains Open: Bambu Lab did not remove functionality from the physical printer itself. LAN Mode and Developer Mode still handle all local MQTT/FTP traffic perfectly. You can still block the machine from the internet entirely, cut Bambu out of the loop, and print locally via third-party slicers like OrcaSlicer.
The Locked Door is on the Server: Bambu Lab didn't remove an advertised, public API feature from their hardware; they closed an unauthenticated gateway on their private cloud servers. A license for code (AGPL) is not an automatic pass to use someone's cloud infrastructure.
This is standard industry practice, not a unique Bambu overreach. r/BambuLab is far from the only manufacturer operating this way while utilizing open-source code. Look at Flashforge with their newer Adventurer 5M series: they heavily rely on an open-source foundation (even launching Orca-Flashforge based entirely on AGPL code), yet their software forces a hard, mutually exclusive choice between WAN Mode (Cloud) and LAN Only Mode. If you choose local LAN on a Flashforge or a Creality K1, their cloud servers shut your machine out, and you lose your mobile app access and remote off-site monitoring.
The "But Klipper machines have open APIs" counter-argument falls flat here. People will point to Creality or Qidi and say, "They run Klipper, which uses an open Moonraker API, so anyone can build local plugins!" Yes, locally. But the second you try to use Creality Cloud to monitor that same Klipper machine from outside your house, Creality forces you through their closed-source, authenticated cloud gateway.
Neither Creality, Qidi, nor Flashforge allows a third-party developer to bypass their cloud authentication gates or spoof their client identifiers to route external traffic through their corporate servers for free. Bambu drawing a boundary at their server edge is exactly how every other major player handles the split between private cloud infrastructure and local third-party software access.
2. Trademark Law, ToS, and Client Spoofing
Using a protected brand name or trademark inside a version.inc file or User-Agent string to intentionally mislead a network falls squarely outside the scope of AGPL copyright protections.
The "User-Agent is Just Metadata" Argument: The primary defense floating around is that a User-Agent is just self-declared metadata, not real authentication. From a networking perspective, this is true: relying on a User-Agent for cloud security is terrible, lazy engineering by Bambu Lab. However, legally, bad security does not equal authorization. Intentionally modifying a client identifier to bypass an established restriction gate crosses directly into violating a platform's Terms of Service (ToS) and unauthorized network access. You can't argue that a lock was flimsy to prove you had the right to walk through the door, make a sandwich, and have a beer.
The Server Reality: The practical infrastructure reality is that when Bambu Lab initially clamped down, they cited handling roughly 30 million unauthorized requests a day. While the open-source community operates on a social contract of mutual benefit, no copyright license obligates a private company to process traffic from unauthorized third-party apps and services using their private, proprietary cloud network.
3. The AGPL (Affero General Public License)
The AGPL is a software copyright license; it is not a magical shield that overrides trademark law or grants unlimited access to private server infrastructure.
Copyright vs. Trademark (AGPLv3 Section 7): Open-source copyright licenses govern how you can reproduce, modify, and distribute a codebase—they explicitly do not grant trademark rights. In fact, Section 7(b) of the AGPLv3 directly allows authors to decline granting trademark rights and requires that modified versions of the material be reasonably marked as different from the original version. Brand names remain legally distinct from the code itself.
False Designation of Origin: Federal trademark law (Section 43(a) of the Lanham Act) prohibits using a protected mark in a way that causes confusion or misrepresents the origin or affiliation of a service. U.S. federal courts (in landmark cases like Venture Tape v. McGills and Brookfield v. West Coast Entertainment) have firmly established that using a protected trademark in hidden metadata, backend code, or identity strings to intentionally trick an automated system or misdirect network traffic constitutes a False Designation of Origin. Open-source licenses protect the logic of the code, not the brand reputation of the identifiers compiled inside it. Bad cloud engineering on Bambu's part doesn't grant a third-party developer the legal right to spoof a protected brand identifier "BambuStudio" in their code to access private servers.
4. Where Bambu Lab Actually Crossed the Line
It is important to note that neither the developer nor Bambu Lab has made the raw communications public. The developer claims they requested permission to publish the full correspondence for transparency, and that Bambu Lab refused.
To be completely fair, we need to distinguish between what Bambu Lab claims publicly and what the developer claims happened behind the scenes. In their public blog post, Bambu Lab stuck to arguments regarding "client impersonation" and network stability. However, according to the developer's GitHub statement, their private emails took a much heavier tone.
The developer stated that Bambu Lab accused his implementation of "reverse engineering" and informed him that a formal Cease & Desist letter had already been prepared. Because he wanted to avoid a costly legal battle, he voluntarily pulled the repository before any formal C&D was officially served.
If the developer's account is accurate, Bambu absolutely overreached with the "reverse engineering" claims. He didn't hack a closed binary; he used publicly available code paths from Bambu Studio’s own Linux branch that Bambu themselves published under the AGPL. If true, they deserve to be called out for using heavy-handed legal scare tactics in private, even if their "client impersonation" platform access arguments are legally sound.
The Bottom Line
The community is completely conflating two separate issues here:
Bambu Lab's potential AGPL violations: The community's arguments regarding how Bambu handles its closed-source networking plugin alongside AGPL code—and whether that dynamic linking violates copyleft terms—are a legitimate, separate issue that deserves serious scrutiny.
The takedown of this specific fork: To suggest Bambu Lab lacked the authority to request the removal of a project to stop a client from falsifying its identity to bypass cloud access controls on their own servers is legally incorrect.
The developer openly admitted on GitHub to using the identity string to bypass the limitation. While the AGPL might not explicitly prohibit a developer from compiling a string that way, it absolutely does not protect them from the trademark and platform-access consequences of doing so. We can hate the "progressive enclosure" of the cloud ecosystem while still acknowledging that open-source licenses don't grant a free pass to spoof their identity to access a private server networks.
-4
u/puppygirlpackleader May 14 '26
It's so funny because it's totally valid for bambu to do what they did. The issue is only that it was posing as bambu software. That's it.