Bambu Lab just did the classic corporate shuffle: wave the AGPL flag with one hand, reach for the leash with the other, and then act surprised when the room catches fire.
Here’s the shape of the mess. Bambu Studio is open source. OrcaSlicer is a fork. Forks are normal. Forks are the entire point. The ugly little miracle of open source is that if a vendor starts acting weird, users can walk around the corpse instead of waiting for a press release written by someone in marketing who thinks “ecosystem” means “you are not leaving.”
That part is fine.
The part that is not fine is when the hardware company decides the code can be free, but the machine can only be useful if every interesting action routes through their cloud like a cow being herded into a tiny, branded abattoir.
That is the actual argument here. Not “open source bad.” Not “forks evil.” The fight is about who gets to control the printer you bought with your own money after the sale is already done and the credit card is already screaming.
Bambu’s defense is basically: yes, the software is open, but don’t be dramatic, the cloud is private, and this fork was faking identity metadata while talking to our servers. Which, to be fair, is a sentence that sounds terrible until you remember the company built a product where the cloud sits in the middle of the user experience like a bouncer with a clipboard.
So now we get the familiar little morality play:
- users want direct control,
- vendors want centralized control,
- the vendor calls it “security,”
- the user calls it “stop touching my machine.”
And somewhere in there a lawyer shows up to explain that the problem is not the AGPL, it’s the cloud terms of service, which is technically true in the same way a bank robber is technically correct that the vault door was locked before he used a stick of dynamite.
The annoying part is that Bambu is not wrong about one narrow thing. If a third-party tool impersonates the official client, that is not a cute little fan project anymore. That is a trust problem. If a random fork can walk into the cloud wearing the official name tag, then yes, your infrastructure team should start sweating through their shirt.
But that is also where Bambu loses the plot.
Because if the cloud is so fragile that a small fork can threaten it, maybe the company should not have built such a hard dependency on the cloud in the first place. Maybe the machine should have a stronger local mode. Maybe the “advanced users” should not need a ritual sacrifice, a firewall rule, and a firmware freeze just to keep their printer from calling home like a nervous intern.
That is the core scam of modern hardware: you buy a physical object, then discover the useful parts were leased to you in the form of remote policy. The printer sits on your desk, but the authority lives in a server rack somewhere, and the vendor is very sorry, but also not sorry, because “reliability” apparently requires you to hand over the steering wheel.
I’ve seen this movie before. The company always says it loves the community. The community is always welcome. Feedback is valued. Collaboration is cherished. The bug bounty program is open. The ecosystem is strong. The word “boundary” appears twelve times like it’s a holy relic. And then, the moment somebody uses the openness in a way the company didn’t plan for, the tone changes from warm to corporate stun gun.
That’s not open source culture. That’s a toll road with a developer relations team.
And yes, the fork author may have crossed a line. If you are spoofing client identity to get around cloud restrictions, you are no longer doing polite open source gardening. You’re poking at a server-side gate with a sharp stick and daring it to notice. Fine. I can live with Bambu objecting to that specific maneuver.
What I cannot stomach is the broader posture: “we made the machine cloud-shaped, then got shocked when people tried to make it less cloud-shaped.”
That is not a security strategy. That is a business strategy wearing a security hat.
The whole 3D printing scene is supposed to be about control. That was the promise, wasn’t it? Cheap machine, open ecosystem, weird little calibration rabbit holes, a thousand community fixes, the occasional broken part held together with zip ties and spite. Then one successful product line arrives and suddenly everyone wants to turn the hobby into an appliance subscription with motors.
No thanks.
If I want a printer that behaves like a service, I will buy a service. If I buy a machine, I expect the machine to belong to me even when the vendor gets moody. Open source is not a decorative sticker you slap onto the homepage while quietly building a moat around the only path users actually need.
So here is my mean little take: Bambu Lab is not defending open source, and it is not really defending security either. It is defending the right to keep the most useful parts of ownership behind a cloud choke point and then punish anybody who proves the choke point is optional.
That is why people are pissed.
Not because they hate AGPL. Not because they don’t understand networking.
Because they can smell a power grab from six rooms away.
And once that smell gets into the plastic, good luck getting it out.