I don't have my notes in front of me, but I managed to do all of that with hardly any trouble at all. IIRC, you only had to change one setting on the printer itself, and optionally block the printer from Internet access via the firewall to prevent automatic firmware updates and telemetry. I have only used OrcaSlicer to tweak my models, mess with parameters, and send the prints to the printers.
So other than Bambu getting all heavy-handed with a legitimate open-source fork of their slicer software (which is definitely not okay), I'm not sure I'm clear on what the kerfuffle is about. Are their printers now MORE locked down than before? Or maybe only certain models?
I think it's an odd hill for them to die on, but it's not a totally unreasonable position - the cloud is other people's computers, other people can have rules about what you can do with their computers. Just because a client is open-source, doesn't mean you're allowed to use the server.
If you're using developer mode running everything locally (or remotely over your own VPN, like the author here) then I think this makes zero difference.
I have a P1S myself, and I find Bambu to be a strange company. They're one that has benefited tremendously from OSS while sometimes violating both the ethos and licenses.
They specifically engineer it such that your prints need to go through an intermediary even when it could send it right to your device on a simple network. That'd be like a laserjet routing through the cloud instead of going to your device. With nothing much in the way of encrypting your designs and protecting your data, it feels like this was done on purpose. Given the shameless track record of many (most?) Chinese companies on IP, my assumption is that they're mainly doing this to steal designs. The juxtaposition of their poor track record on OSS, what seems like a shady approach to privacy and IP protection, and the aggressive legal posturing - all sum up to what I think is a very untrustworthy organization.
Luckily my designs are in the "look at this trash" territory, so I don't have anything to worry about, but I certainly wouldn't use this for important work.
Why do you have to do that on a product you own that is running in your home?
I’m not saying we shouldn’t shame those companies for not abiding to their words, but there is more to it than outrage. Suing them (or the threat of) might also work here if they really went against the license.
My biggest annoyance is that I can no longer use OrcaSlicer to interact with my printers (e.g. sync filaments) and start prints remotely. I am still very annoyed at Bambu Labs for this stupid move, as it directly impacts my usage.
What most people seem to be missing in these discussions is that some of us have printers in remote workshops, not next to us. So all the "LAN" or "Developer" options aren't great, especially if you have to pick between those OR the cloud.
> We have documented incidents of service outages caused precisely by spikes in unauthorized traffic - overwhelming the servers, causing service disruptions affecting everyone. The cost was instability felt by all users.
So it's a problem that their printers are popular, and they can't be bothered to scale their infra, so let's gate everything based on USER AGENT STRING! This is so crazy of an excuse that I don't believe it.
That’s not impersonation. That’s Bambu discovering that user agents are not authentication.
But, though there are some explicit laws where that’s how it works, that’s not generally how the legal system works. If I have a private server, and I don’t give you permission to access it - or, even better, tell you not to, it doesn’t really matter how I secure it. If you access it, you’re in the wrong.
To give a physical analogy, it doesn’t matter how I’ve secured my house. Even if the door is open, you’re not allowed to just waltz in (or, to take it a bit further, come in and start using my stuff).
The legal risk comes from why you are doing it and what protections you are bypassing.
If you are doing it specifically to bypass Bambu's authorized access, then it is very likely to fall afoul of the Computer Fraud and Abuse Act. The mechanism (spoofing the UA) is entirely incidental to the motivation (bypass authorized access), which is what the law cares about.
The funny part here is it seems Bambu is more exposed to a libel suit than the developer is for... checks notes clicking 'Fork' on Bambu's github. Since the moment he did that, his software was supposedly in breach of Bambu's...expectations.
At least in the US, the law against unauthorized access to a computer system has no requirements for how good the security has to be. If you should reasonably know you're not supposed to be using it, that's potentially enough to make it illegal.
Am currently somewhat into the topic of UAs for a personal project (not connected to Bambu printers), so am honestly interested for any tangible information, I just dislike us assuming something illegal because a corporate entity views it in a negative light.
[0] https://www2.ca3.uscourts.gov/opinarch/131816p.pdf ("We also note that in order to be guilty of accessing “without authorization, or in excess of authorization” under New Jersey law, the Government needed to prove that Auernheimer or Spitler circumvented a code- or password-based barrier to access. See State v. Riley, 988 A.2d 1252, 1267 (N.J. Super. Ct. Law Div. 2009). Although we need not resolve whether Auernheimer’s conduct involved such a breach, no evidence was advanced at trial that the account slurper ever breached any password gate or other code-based barrier. The account slurper simply accessed the publicly facing portion of the login screen and scraped information that AT&T unintentionally published.")
You're correct of course that this is an entirely distinct argument from what Bambu's legally allowed to do under existing law.
I don't know if that is what is happening here because the article is talking about a fork that is bypassing Bambu's servers entirely (which is permitted under the AGPL) and Bambu is not happy.
Edit: On re-reading, it seems to me the fork is still calling Bambu's servers. It's just bypassing some things.
This is just Bambu alienating their customer base, again.
Still I suspect it is about spying in wartime, Bambu printers are at the core of the Ukrainian war effort, the main reason even Ukraine is winning since januari 2026.
First China prevented Ukraine from using any of the drones that they sold in millions to Russia while exercising the built in kill switches in Chinese drones used in by Ukrainians.
Suddenly Bambu, another Chinese company started listening in on the 3D printing on a massive scale in secret factories all over Ukraine that make the drones to replace the Chinese drones. Very suspicious.
Whatever is the reason Bambu locks down software or firmware on their 3D printers, now is the time for programmers to change the situation. We need to put up money like Louis Rossmann did [1], not to fight legal battles but for a assembly language programmer to reverse engineer the Bambu firmware and make a free and open source version.
This firmware replacement will cost a couple of months to write so we all should send that programmer a little money so he/she can release it for free.
A free Bambu firmware will allow the Ukranians to continue producing another few million drones and save over a hundred thousands lives by ending the war.
Now is the chance for us outsiders to help Ukraine, by freeing Bambu firmware.
[1] https://www.youtube.com/watch?v=qLLVn6XT7v0
P.S. I would be willing to do the reverse engineering but I would need at least 35 euro per day (to eat) to build a new firmware for all Bambu models from scratch. I would need a few different models of printers on loan for a few weeks to test the new firmware. I estimate it would take 5-9 months to rebuild firmware for all models from zero and release it. Maybe Rossmann and Geerling could use their influence and coördinate this freeing of the firmware?
I just emailed Rosmann and Geering to see if we together can free the Bambu firmware. Anyone who wants to help, please contact me trough my HN profile.
the Ukraine war started in 2014 technically. But even if we go to the "current" wave start, that was 24 February 2022[0].
Bambu Labs released their first printer (X1C, on kickstarter) on 31 May 2022, let alone their "must go through cloud service" restriction starting in early 2025[1].
[0]: https://en.wikipedia.org/wiki/Russo-Ukrainian_war
[1]: https://blog.bambulab.com/firmware-update-introducing-new-au...
https://www.newsweek.com/china-ukraine-russia-war-drone-uav-...
I'm not up to date with their latest printers, but the Bambu printers used during this timeframe have easy ways to enable LAN only mode. You can leave it disconnected from the network entirely and use an SD card, too.
The app lets you enable root access and install firmware mods. There are multiple efforts to reverse engineer the firmware.
> A free Bambu firmware will allow the Ukranians to continue producing another few million drones and save over a hundred thousands lives by ending the war.
If that were true, it seems to me, that Ukraine would have already done it if it was somehow standing in their way.
Bambu has every right to restrict or limit how their cloud service is used, even if they do it in a completely insecure and trivially reproducible way (a user agent).
I'm curious from a legal perspective - the user agent in the Bambu slicer is AGPLed, so copyright wise it seems anyone could put it in their own slicer too. Nonetheless, something feels wrong to me about saying you're a Bambu slicer when you're actually not. Bambu is going after it because of the user agreement, but is there any other legal standing for complaint?
Bambu Studio is literally a PrusaSlicer fork. You don't get to build on the community and then threaten it.
They are offering a cloud infrastructure that allows users to remote control the printer via their software. If they don't want users to use a non-approved software to access their cloud, they should just build auth around it and explicitly tell people that. The accessibility for users to utilize the printer without going through official software and cloud is a whole other can of worms of course.
This whole fiasco could have been avoided by not being so confrontational, giving their user base ideological ammo.
Like when you think of the App/Play store lockdowns, the new ReCaptcha attestation stuff, and other things that have a more authoritarian angle to it as of late, you can at least see how it happens: most of their consumers aren't technical and don't even know how to argue against it or why they should care.
With Bambu on the other hand, I'd think a good portion of its customers do actively care about this kind of thing. 3D printing just doesn't have the same market reach as computers and smartphones.
Also, it seems to me like there's eventually going to be a turning of the tide on all of these pushes (app stores included) and companies that are making these kinds of moves aren't seeing that writing on the wall.
Anyways, yeah, my next purchase will be a Prusa.
I'm fairly certain user agreements have been used for suing makers of game cheats and other similar things. Certainly in the industry I work in, there was a company making third party software and integrating it with the industry standard tool without going through the official channels, which caused people to violate the user agreement when used. They got sued and settled.
Bamboo not understanding the OS licencing when they themselves took from Prusa if I remember correct is pretty rich.
I don't really see why everyone is up in arms about this. You are able to print in LAN mode or directly through USB drives without going through bambus servers.
Their slicer is open source but it downloads a plugin once you launch it if you choose to which is closed sourced that interacts with their APIs.
Someone reverse engineered the plug-in and put it into orca slicer and then claimed that the plugin should have been GPLed to begin with which I find dubious. I don't really see it being much different than downloading closed drivers on Ubuntu but I'm also not a open source lawyer.
To me, the problem with all of this is that it seems strange to want the plugin when bambu will just shut off their resources to unsigned versions of the network plugin if the orca slicer dev got their way.
I'm open to being convinced but I just don't think the cross-section of people who want this would actually want prints going through bambus cloud so this effort really feels vain.
It also feels like bad framing as well because every post I see about this thing really tries to blur the line and claim this plugin and orca slicer are one and the same.
> Someone reverse engineered the plug-in and put it into orca slicer and then claimed that the plugin should have been GPLed to begin with which I find dubious. I don't really see it being much different than downloading closed drivers on Ubuntu but I'm also not a open source lawyer.
The GPLv3 specifically was written to address a problem called "TiVo-ization", which is when a hardware vendor uses some trick (DRM, proprietary blobs, whatever) to prevent users from actually running modified versions of the software.
The AGPL, the license of this particular software, extends the GPLv3 with protections for users of network services:
> Simply put, the AGPLv3 is effectively the GPLv3, but with an additional licensing term that ensures that users who interact over a network with modified versions of the program can receive the source code for that program. In both licenses, sections four through six provide the terms that give users the right to receive the source code of a program.
https://www.fsf.org/bulletin/2021/fall/the-fundamentals-of-t...
And on TiVo-ization: https://en.wikipedia.org/wiki/Tivoization
The Linux and proprietary drivers situation is more complicated, but proprietary drivers on Linux are generally restricted to interfaces that Linux chooses to expose to them for that purpose. But the Linux kernel seems to take a narrower view of what constitutes a derivative work than was likely intended by the FSF in writing the GPL. Under a "traditional" reading of the GPL, those proprietary drivers are meant to be illegal. Whether some or all of the linking done by proprietary drivers in the Linux kernel is really allowed by the GPL or not is somewhat untested, I think.
Correction is much harder than starting off on the right side.
Sure, a manufacturer that didn’t need to course correct yet doesn’t mean they won’t change their stance in the future, but the same is true for one that already course-corrected.
We see this with privacy eroding laws continually - legislators will “listen” and course correct if there’s pushback, only to reintroduce the bill in the next legislative session, repeatedly, until it gets passed.
I’d prefer the one that hasn’t yet signaled a desire to do something negative in the past to one that has, even if they walked it back later.
Someone who isn’t racist because they grew up in a progressive family just means they were lucky. They often have never been tested under pressure.
On the other hand, someone who grew up in a racist family and ends up not racist means their beliefs are battle tested. This is a real test of character — it also tells me how they process information.
What you’re describing is a third case where someone pretends to correct but has no intention to, which I do not think Bambu’s original act of opening of LAN access qualifies.
Now I think the other dimension here is that people are expecting Bambu to believe in open source. They might not actually, which is their own opinion to have, but that’s a different problem altogether. I believe in local access but not necessarily open sourcing of everything so from my PoV, Bambu’s stance is perfectly consistent.
Doesn't it sounds weird to you? I mean, what the reason they have to blur the line? Are they just clueless? Or maybe they fight for some political reason, like an anti-corporate stance, and Bambu is just a convenient target for them?
I'm asking, what you think of them, because I can't understand you. Your take on the conflict is incompatible with behavior of the people opposing Bambu. Or rather it leaves no good explanations for their behavior. When I notice it, I start digging, because if the situation doesn't have a good explanation, it means I do not understand the situation. But you just accept your understanding, so you have some good explanation for people's behavior?
This is in no way equivalent. You can't sync filaments, you can't monitor printers in your slicer, you can't monitor prints from your phone. This is like going backwards at least 5 years.
I find this shallow take really annoying, as it tends to derail most discussions ("you have LAN mode, so what are you complaining about").
Plenty of situations would make me feel differently, but I'm fine with their restrictions in this case.
1. OrcaSlicer: so it's a fork of Bambu's official client, Bambu Studio - but it apparently still goes through Bambu's servers for printing? How exactly does that work? Does it also "impersonate" the User-Agent, and Bambu was okay with that?
2. OrcaSlicer-bambulab: if the goal of this fork-of-a-fork is to bypass Bambu's cloud servers, why would it still need to "impersonate" the UA and communicate with Bambu's servers (as Bambu claimed)? Wouldn't the whole point be to avoid doing that in the first place?
Orca Slicer was forked to improve usability and features, not to get around any cloud printing requirements, Bamboo added those later and removed the ability to print locally.
It has to impersonate to transfer a gcode file locally, which is another open standard.
Bamboo restricted LAN printing, that is the issue.
I finally got to the bottom of this; there is a cloud-based RPC method called `bambu_network_start_local_print` where Bambu's Cloud would authorize a print using (ostensibly) only locally transferred data. The goal of this project was basically to pretend to be the Bambu plugin in order to authorize this method, which is otherwise locked behind Bambu's auth system.
The alternative is to run the printer in LAN mode (which OrcaSlicer has always supported) where the client connects natively over MQTT, but after Bambu added their cloud authentication, this requires putting the printer in Developer mode and severing the Cloud features.
What printers are similarly priced and have similar specs, for someone relatively new to 3D printing?
None, really. Prusa printers are good enough though. If you value freedom and privacy, its worth a few extra dollars.
I've got an a1 mini myself, and I'm not aware of anything comparable on the market, but there's a clear need for some competition now.
It's a much more interesting and dynamic place than before Bambu's market entry
But you raise a good issue: are they selling these at a loss in order to leverage some sort of lock-in? If that's the reason they're so cheap, that's important to know.
I honestly wouldn't mind paying twice as much for something that's more open. But it's also an issue I haven't looked very deeply into. For my first 3d printer I just wanted something cheap and foolproof.
The Mk3 is also easy, and can be had for cheap now, but it doesn't have auto Z-adjust which is really nice. It's also noticeably slower compared to the latest models.
[1] https://store.creality.com/products/k2-k2-combo-3d-printer-l...
same for breach National Defense Authorization Act (NDAA)
point: they enfrocing network access for their products (including USA), which are sensitive. so, maybe export control problems?
Having said all that, the hardware is very good. Software, not so much.
That said none of this is surprising. Bambu Labs have been very candid about their playbook which is following Apple's lead. They want to be the Apple of printers, a very walled garden with high integration good UX and not a lot of freedom because they want to tightly control the full experience.
And that is going to alienate a lot of people and endear a lot of others. The only reason they've even paid lip-service to open source or open hardware is simply to get a foothold in an industry that had strong roots in that area. Now that they're a more established brand we should expect them to start bricking in the garden and adding controls.
Fortunately I think they've been a net-good for the printer landscape, they shook things up pretty hard and I think there's now more competitive models from other brands.
They rubbed people the wrong way launching the CC2 with multi-color support before they developed the multi-color add-on that was promised for the original CC. I didn’t plan on multi-color with the CC, so that didn’t personally bother me too much.
I recently got a Snapmaker U1 for multi-toolhead prints and love it so far - much less waste than a filament changer and I’m using it for more exotic prints like a mix of conductive and regular PLA in a single part that wouldn’t work well in a filament changer single toolhead printer.
And I still use my CC for occasional single color prints (recently it’s been dedicated to TPU but I’m probably going to move that over to the U1 so I can do “over molded” TPU+PLA prints).
In short, if you’re willing to spend more I’d highly recommend the U1 if you know you’d benefit from the toolchanger. CC is probably a fine budget machine but there are a lot of other similar budget corexy machines to consider these days as well (I got CC when it was groundbreaking for features at its price but competition has caught up by now).
My understanding is that right now, you can run your printer in LAN or USB mode without Bambu's cloud, and this is supported natively by OrcaSlicer (or any slicer using USB), but you lose some of the Cloud monitoring features.
You can also use Bambu's cloud with their Cloud Connect app and gain those monitoring features while using a third-party slicer, but at the expense that you send your prints through their cloud.
Or, you can use Bambu Studio and get the "fully integrated" experience.
My understanding is that this plugin just replicated their Bambu Studio communication with the Cloud, and that it _enabled_ you to send your prints to their cloud, not _disabled_ it. Is there something I'm missing that made this valuable? (ie - did it do some hybrid where it could hack in the Cloud monitoring without sending the prints through the Cloud?) Otherwise, I think what Bambu are doing are distasteful but I don't understand all of the Chinese espionage hand-wringing or "stealing our files" commentary around this.
EDIT: I finally got to the bottom of this; there is a cloud-based RPC method called `bambu_network_start_local_print` where Bambu's Cloud would authorize a print using (ostensibly) only locally transferred data. The goal of this project was basically to pretend to be the Bambu plugin in order to authorize this method, which is otherwise locked behind Bambu's auth system. This makes more sense. I wish the commentary on this subject would actually explain this.
The Bambu printers work. Imagine the difference between windows XP and OSX. Do you guys remember the insane breath of fresh air it was to get a computer which just worked?
That's Bambu. Yeah they aren't open source there's all sorts of telemetry, etc. Nobody cares because they really just want to print things.
Bambus p2s and their ams2 pro have had more hardware reliability issues in 1 month than is normal
Wayyyy more than my p1s and ams combo
I think there’s also some issue in their firmware that needs to be rolled back or perhaps properly tested
Gonna sound harsh :
This isn’t a printer anymore … it’s AI slop
Do such people really exist? Are there actually people who are comfortable blindly starting a robot in their home, with a part that heats to 150 C, and then hope that everything will work out and when they get home the part will be waiting for them, instead of the firefighters?
Maybe if it knocks itself down to the ground? But I worry much more about faulty wiring or stuff like that. And that's more a function of the brand and model
Not saying fires don't happen that way but let's say it's a failure mode that is a challenge to achieve intentionally much less accidentally.
Failed FET for instance. They tend to fail "on". Unless you have a highside FET shutting off the power (and that may fail too).
On my printer I have software watchdogs but I also have an entire "dumb" (no MCU) circuit that will shut off a large relay that goes to my heaters if any of it's failsafes are triggered. I have a smoke detector, secondary thermistors, etc.
There are a bit more things in the way of thermal fuses and heaters that are less likely to runaway on the newer commercial printers but I still think people need to take the risk more serious.
I have been building printers and printing since 2011 and I still prefer to not have my printer in my house where the family sleeps, even with the failsafes. It lives out in the shop with plenty of room around/above it in case of a fire.
Prints regularly take ten+ hours to complete. No one is vigilantly guarding their printer during this time. Fire spreads so quickly in a house that a smoke alarm is often just a signal to get out, you don’t necessarily have the time to grab a fire extinguisher and put it out.
And how big is the risk, really? The materials that you use do not ignite so close to their melting point.
The main potential problem these days (in my view) is whether a print finishes without crashing or delaminating from the print plate, which also has workarounds... but that's only potential printer damage, not a fire.
At worst the sprinklers above it will wash it but that’s in a catastrophic instance.
It is closer to a toaster or an oven than a water heater or HVAC.
Also...my last lease specifically said that I was not allowed to use the washer/dryer or oven when I was not home. So it is not a stretch to believe that the property owners will use those types of agreements to go against you when the insurance company denies your claim (this does and has happened with 3d printer fires).
All that being said...I have run 135hr prints unattended on my printers (not bambu). The risk may be low but it is not zero and it certainly higher than a water heater or HVAC.
Perhaps one or two.
This mentality is baffling to me. No, insurance isn't there so you can knowingly do risky things, it's there in case something accidentally happens.
Would you say the same about juggling chainsaws? "That's what health insurance is for"?
Absolutely crazy to me
There are people who are simply careless
There are people who think of the 3d printer as a toy, not as a piece of industrial (or semi industrial) equipment
There are people who are arrogant, who think they have figured out and solved anything that could possibly go wrong so they have made it safe to do
There are people who kind of think they are invincible and are just convinced that bad stuff won't happen to them
Idk. It's not a stretch at all for me to imagine this sort of person, based on the people I've met in the past. I mean people remove safety guards from power saws that are designed to protect you from losing fingers, so...
Their cloud infrastructure obviously has real costs associate with running it, and I don't understand why any software other than their own should be entitled to use those resources.
If you buy something and then significantly modify it, you generally tend to void the warranty - and that's not because companies are just greedy; there are real limitations when it comes to a company's ability to support the endless ways a product could be modified.
Publishing something as open-source does not imply that you must operate an optional-but-complementary service at a loss for charity.
That's not a genuine argument, nobody "feels entitled" to anything. Bambu made a deliberate choice to architect the product this way, deliberately placed themselves in this gatekeeping position, and they're deliberately working towards removing any other form of access to our hardware.
Maybe I'm mistaken, but I don't think that's what is happening. They aren't doing anything to block OrcaSlicer or any fork from working with the printer using LAN-only mode. It's only if you want to use Bambu Lab's servers for essentially a remote-access solution (which, by the way, kind of defeats the privacy-oriented purpose of running some of these forks) that they're saying you should use their own software.
Thought experiment: if a VPN provider offers an open-source client, and their reference implementation also includes some kind of promotional free tier of their service with limitations, are they then obligated to offer free service to every fork of the client? What if some of those forks abuse the free tier by removing limitations that their reference implementation imposes?
All this outrage essentially sounds like "since Bambu Lab's slicer is open-source, the open-source community should be able to point any slicer at Bambu Lab's servers to get free remote monitoring services". And I don't think that's right.
What phone and laptop does Jeff use?
Don't let perfect be the enemy of good.
Pine sucked all the oxygen out of the environment, with a shit dead-on-arrival product. Pinephone doent even work as a bloody phone.
Other Linux phones are 2-3 generations old, and priced at $700 or so.
So, we're stuck with Apple or Google. Not great choices either way.
Internet influencers - nothing against this one, I like his videos, I think I got JetKVM because of one video - are a persona which is different from their person. They sell something in their videos and do things in videos that are different from their true self. Videos are primarily done to drive more subscribers. I don't dispute that he might be an exception but he has >1M subscribers which makes being authentic and not driven by audience difficult.
Take LTT as an extreme example.
[Edit] I'm not judging Jeff or saying this is good or bad.
Not sure what that exchange was for, but I like it!
PS: Not a native speaker, don't know what "HN peanut gallery" means. But I like peanuts, though I think Peanuts are overrated. Though sometimes our dog looks like Snoopy, when her ears are flying.
2. A google pixel isn’t meaningfully more open than an iPhone (I depend on functionality that would be unavailable if rooted). This wasn’t meant to be an iPhone vs android debate. For the purposes of this discussion they are equivalent.
"reverse engineering or writing drivers"
When I encountered Linux I was already too old to be interested in that kind of things. But I did disassemble C/PM code. I was interested in blue boxing, cracking of games, infinite life reverse engineering and hacking in the 80s though.
"For the purposes of this discussion they are equivalent."
Again it feels like you made some assumptions about me and what I wanted to say which are just that, assumptions.
“Inauthentic” was I still think a close enough reference paraphrase of your statement. Not a value judgement. You even used the word authentic. And in general I wouldn’t necessarily disagree but I don’t see how it is necessarily related to their choice of personal devices. An internet celeb probably doesn’t use GrapheneOS because the limitations sucks for most people, not because of some calculated subscriber count play.
"So, this wasn’t a dick sizing contest"
You can say "I didn't intend this a dick sizing contest" but you can't say "This wasn't a dick sizing contest". Again this is based on your judgement.
For anyone considering alternatives: You should know that almost all other 3D printers expect you to know a little more about how they actually work than Bambus. Bambus are as close as you can get to a "just works" type experience, but modern alternatives from others are nowhere near as hard as they used to be.
The closest "easy" alternative is probably Prusa, but you'll pay significantly more for a Prusa machine than you would a Bambu. They're an excellent company, and the complete opposite of Bambu when it comes to Openness. If money is no object, Prusa is highly recommended.
Beyond Prusa, there's a lot of other options. https://auroratechchannel.com/#section2 This list is a good one.
I personally run an old Elegoo Neptune 4 pro - but my needs are quite low. If I were buying today, a Snapmaker U1 or the Creality K2 Plus is probably where I'd end up going.
You're right that they're expensive but you get free human support 24x7, you get an open platform, lots of contributions to open source (even Bambu Studio is a fork of Prusa Slicer), and they pretty much go on forever.
My Core One+ started its life as an original MK3 and went through each iteration of upgrades, and it works like new. I'm now waiting for an INDX upgrade for it.
IMO the main drawback of consumer Prusa offerings is the lack of good chamber heating for more advanced materials. I can print PC on my Core One+ in the summer with the chamber at 45℃ (good enough for most uses, but 60 would be better), but in the winter it becomes a lot harder.
The Core One L is supposedly better in that regard but I've seen reports that it's still not ideal.
Other than that, I feel the extra cash pays itself back in the long run.
Could too much thermal insulation cause the bed temperature to lower (to avoid overheating chamber temp) to the point the print no longer adheres? etc.
If you could recommend some articles on the subject I would highly appreciate it.
The main issue is how close the walls are to the bed, which makes a lot of insulation projects dead in the water. If a radiator reflector foil [0] can be made to fit, it might help quite a bit as well.
Other than that, proper active chamber heating is really where we should be heading. When I have the time I might attempt to replace the left panel with one.
[0] https://www.amazon.co.uk/Radiator-Reflective-Thermal-Heating...
Then in 2025 they changed their 'open community license' to say users may not:
“Sell complete machines or remixes based on these files, unless you have a separate agreement…” and “The Restriction: You cannot commercially exploit the design files…”
https://blog.prusa3d.com/core-one-cad-files-release-under-th...
Maybe this is more a comment on how open source has had to change in the face of commercial exploitation of the vulnerabilities traditional open source licenses create for the businesses doing the R&D.
They're doing what it takes to be a business. I was glad when they moved to more injection molded parts instead of trying to 3D print their own parts. It was a cool idea at the start but the time for that was long past.
My only slight objection is that you can tell they're trying to have it both ways: They want all of the good will and reputation of being open source, but they're also trying hard to put as many limits on this as they can. Like all projects trying to walk the line between open and closed source, I think they're at their best when they're honest about what they're doing. The moves they made with their open license are completely reasonable and I support them, but that blog post was a bit of a letdown when they tried to make it about fighting patent trolls for the community or something. When you reach Prusa scale you have to be honest that you're no longer one and the same with the community. You are the medium-ish size business that people rely on. Taking away the right for others to sell the products is a reasonable business move, but please be honest about it rather than trying to tell us it's for our own good.
You can be entirely in favor of the open source ethos, even as a commercial entity, but then certain actors can take advantage of that ethos and just directly commercialize your R&D investment and take all the proceeds of your investment, whether or not they comply with attribution or share-alike requirements.
It’s tough seeing an open source project you’ve poured tons of care and effort into (and WANT people to share and remix and build cool things) get more or less “extracted” for profit without contributing back (code or money).
At the end of the day, none of it really matters unless you’ve got money and time to actually try to enforce your licenses, or have enough customer mindshare to effectively change the behavior of bad actors without needing legal action.
I’ll probably use licenses like Prusas in the future for similar reasons, even though I generally prefer to use less restrictive ones. Bad actors, or even just non-benevolent actors, can really sour the open source ethos, and it sucks but there’s no way to legally enforce “don’t be a jerk” without restricting a legal document in slightly unpalatable ways.
It only stops the honest people from doing that (and possibly much more, like manufacturing and selling replacement parts or mods).
Creating 3D models from existing products is relatively fast and easy. The hard parts have always been the actual design process, materials selection, and setting up the supply and manufacturing chain.
Prusa took what was practically a non-issue (cloning of their modern printers which have multiple custom parts and are overall not easy to clone cheaply anyway) and used it to restrict the freedoms of end users and small businesses while crying about how they are the victims.
I lost a lot of respect for Prusa when they came out with the OCL.
A damn patent would have been both more effective and less restrictive for reasonable commercial purposes.
They ARE however deterrents to bad actions from less-than-scrupulous entities, and enforcement mechanisms against fully-unscrupulous entities.
I suspect (but will admit I am just guessing here) that Prusa would prefer not to get to the enforcement stage because it is both costly and annoying, but having that in your back pocket is, sadly, necessary in a litigious society with some number of unscrupulous actors, and the deterrent effect alone is likely enough to achieve most of their goals.
If I make an open source car, I don’t want someone else taking my design work, and then selling a cheaper version of my product, I want my consumers to build their own parts.
Maybe you should make a source-available car, or a car with select portions of CAD available, or something else that fits your intended business model better than open-source.
Different licenses are build around different philosophies, and the common open source definitions allow commercialization as long as the source & modifications you make are freely available to others. Prusa is breaking from that tradition.
Then I installed the app (open source in github) and started using the “cloud” services. I consider myself pretty stupid with such things, and it was absolutely the easiest thing I’ve done in 10 years.
The price is very high though. But at least you OWN the damn thing.
I have no first-hand idea of they’re ’morally’ better than Bambu - I haven’t looked into it - but I think the folks in charge of buying them considered that.
- they benefit from open source software work
- we benefit from their dirt cheap top performing machines
As long as they remain the lowest priced and the best, they can do whatever they want if you ask me. They provide insane social value through accessibility. Before them, it was Creality with the Ender 3.
My problem with Pruša as an European is that it turns us into the equivalent of being a Chinese citizen who can't afford the Temu product they make at work. Their machines are priced more or less only for US export, and not really something most people here can reasonably buy. They even refuse to use injection moulding out of some self righteous principle, which drives the price per unit up further all the while selling less durable machines cause they're half RepRap. I take it sort of as a personal insult and I will never buy one even though I can afford it, I see it as bad value. Like buying a gold plated watch or something.