Bambu Lab: Difference between revisions

Line 39:

==Incidents==

===Authorization Control System (2025)===

===Authorization Control System (''2025'')===

In early 2025, Bambu Lab announced changes to future firmwares that would implement a centralised authentication mechanism that regulated connections and control over the customer's 3D printer. This new firmware would be mandatory to install and could have prevented the customer's printer from functioning until it had been. This effectively forced customers to agree to new Terms and Conditions surrounding the use of their printer, which they did not agree with upon purchase of the product.<ref>{{Cite web |last=Tyrer-Jones |first=Alex |date=20 Jan 2025 |title=Bambu Lab Responds to Backlash Over New Firmware Update |url=https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |url-status=live |archive-url=https://web.archive.org/web/20250214090029/https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |archive-date=14 Feb 2025 |access-date=1 May 2025 |website=3D Printing Industry}} </ref>

In early 2025, Bambu Lab announced changes to future firmwares that would implement a centralised authentication mechanism that regulated connections and control over the customer's 3D printer. This new firmware would be mandatory to install and could have prevented the customer's printer from functioning until it had been. This effectively forced customers to agree to new Terms and Conditions surrounding the use of their printer, which they did not agree with upon purchase of the product.<ref>{{Cite web |last=Tyrer-Jones |first=Alex |date=20 Jan 2025 |title=Bambu Lab Responds to Backlash Over New Firmware Update |url=https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |url-status=live |archive-url=https://web.archive.org/web/20250214090029/https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |archive-date=14 Feb 2025 |access-date=1 May 2025 |website=3D Printing Industry}}</ref>

This new authentication mechanism resulted in numerous designed-for and compatible third-party products, both software and hardware, being made incompatible with the printers going forward. The chief products affected were (including but not limited to): Panda Touch, OrcaSlicer, any third-party product making use of the MQTT protocol. Soon after the updated software was released, users managed to [[Bambu private keys leaked less than 24 hours after announcement|extract necessary security keys]] from it to continue using their third-party products. Amendments have presently been made that would allow some or all of these products to work with workarounds or extra software or tools from Bambu embedded into these products.

Line 49:

Line 50:

Bambu Lab vocally spoke out against the public's reaction, calling many of the valid concerns "unfortunate misinformation", "false accusations" and "baseless allegations".<ref name="bambu-connect-response">{{Cite web |date=20 Jan 2025 |title=Updates and Third-Party Integration with Bambu Connect |url=https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/ |url-status=live |archive-url=https://web.archive.org/web/20260216001409/https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/ |archive-date=16 Feb 2026 |access-date=19 Mar 2025 |website=[[Bambu Lab]] Blog}}</ref> The company's initial blog post announcing the firmware changes was also edited after publication to include an FAQ section addressing whether users could remain on old firmware, a section that was not present on the day of the announcement when community members first raised their concerns.<ref name="firmware-update-introducing-new-authorization-control-system-2" />

===Cease and desist against OrcaSlicer fork maintainer (2026)===

===Cease and desist against OrcaSlicer fork maintainer (''2026'')===

{{Main|Bambu Lab Authorization Control System#Cease_and_desist_against_the_OrcaSlicer-bambulab_re-enablement_project}}

In April 2026, Bambu Lab sent a private cease-and-desist demand to Pawel Jarczak, a Polish developer who had published an OrcaSlicer fork restoring direct printer control on top of Bambu Lab's own AGPL-licensed source code. Bambu Lab alleged the fork constituted impersonation of Bambu Studio, bypassed authorization controls, violated their Terms of Use, and involved reverse engineering.<ref name="jarczak-readme">{{Cite web |last=Jarczak |first=Pawel |title=OrcaSlicer-bambulab — This is the end…. |url=https://github.com/jarczakpawel/OrcaSlicer-bambulab |url-status=live |archive-url=https://web.archive.org/web/20260430001537/https://github.com/jarczakpawel/OrcaSlicer-bambulab |archive-date=2026-04-30 |access-date=2026-05-04 |website=[[GitHub]]}}</ref> Jarczak rejected these characterizations, stating his work was based on publicly available AGPL source code, and asked for specifics about which files or commits were at issue. He reports receiving further broad accusations rather than specificity.<ref name="jarczak-readme" />

Jarczak removed the repository voluntarily but stated the removal should not be interpreted as an admission that the legal or technical allegations were correct.<ref name="jarczak-readme" /> On May 7, 2026, Bambu Lab published a blog post ~~recharacterizing~~ the dispute as being about "impersonation" through a "falsified" HTTP User-Agent string, rather than about open-source rights.<ref name="bambu-blog-record-straight">{{Cite web |title=Setting the record straight on Cloud Access and Community |url=https://blog.bambulab.com/setting-the-record-straight-on-cloud-access-and-community/ |website=Bambu Lab Blog |publisher=Bambu Lab |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref> The User-Agent string in question is generated by Bambu Lab's own AGPL-licensed source code in <code>src/slic3r/Utils/Http.cpp</code>.<ref>{{Cite web |title=Http.cpp source file (User-Agent setter at line 175) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/Http.cpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref>

Jarczak removed the repository voluntarily but stated the removal should not be interpreted as an admission that the legal or technical allegations were correct.<ref name="jarczak-readme" /> On May 7, 2026, Bambu Lab published a blog post re-characterizing the dispute as being about "impersonation" through a "falsified" HTTP User-Agent string, rather than about open-source rights.<ref name="bambu-blog-record-straight">{{Cite web |title=Setting the record straight on Cloud Access and Community |url=https://blog.bambulab.com/setting-the-record-straight-on-cloud-access-and-community/ |website=Bambu Lab Blog |publisher=Bambu Lab |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref> The User-Agent string in question is generated by Bambu Lab's own AGPL-licensed source code in <code>src/slic3r/Utils/Http.cpp</code>.<ref>{{Cite web |title=Http.cpp source file (User-Agent setter at line 175) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/Http.cpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref>

The incident was covered by XDA Developers, Tom's Hardware, 3Druck, and Manufactur3D, and became a flashpoint in the wider 3D-printing community over open-source licensing and consumer rights.<ref>{{Cite web |last=Batt |first=Simon |date=2026-04-23 |title=A developer restored OrcaSlicer's features that Bambu Lab killed — then the legal threats arrived |url=https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |url-status=live |archive-url=https://web.archive.org/web/20260427233833/https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |archive-date=2026-04-27 |access-date=2026-05-04 |website=XDA Developers}}</ref><ref>{{Cite web |title=Developer re-enables 3D printer features that Bambu Lab disabled, firm promptly threatens legal action — OrcaSlicer-BambuLab project now shuttered |url=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 |website=Tom's Hardware |date=2026-04-29 |access-date=2026-05-10 |url-status=live}}</ref>

Line 59:

Line 61:

===Farm Manager subscription potential===

Bambu Lab's Farm Manager EULA contains language reserving the right to introduce fees for the software and connected services, including for commercial uses. The EULA states in capitalised text that the company "MAY CHARGE A FEE TO CERTAIN USERS OR FOR CERTAIN USES (E.G. COMMERCIAL USES)" and "RESERVES THE RIGHT TO AND MAY CHANGE THE LICENSE AND FEE STRUCTURE."<ref>{{Cite web |date=2025-05-27 |title=BAMBU FARM MANAGER EULA AND SERVICE AGREEMENT |url=https://bambulab.com/en/policies/bambu-farm-manager-service-agreement |url-status=live |archive-url=https://ghostarchive.org/archive/3ZHOP |archive-date=2026-03-07 |access-date=19 Mar 2025 |website=[[Bambu Lab]]}}</ref> Despite publicly denying any subscription model,<ref name="bambu-connect-response" /> the EULA language establishes the contractual groundwork for one.

===Helio Additive===

In mid 2025, Bambu Lab added a new functionality in a form of a third party cloud service where you can send your design to get a thermal analysis, which can be used later to optimize the print adjusting the temperature (for [https://www.helioadditive.com/pricing paid membership]). Besides privacy concerns of sharing the designs with a Chinese startup, the functionality is restricted to an online-only model, with no offline simulation alternative, limiting potential open-source or community-driven innovation.

In mid-2025, Bambu Lab added a new functionality in a form of a third party cloud service where you can send your design to get a thermal analysis, which can be used later to optimize the print adjusting the temperature (for [https://www.helioadditive.com/pricing paid membership]). Besides privacy concerns of sharing the designs with a Chinese startup, the functionality is restricted to an online-only model, with no offline simulation alternative, limiting potential open-source or community-driven innovation.

==Comparisons to similar practices==

@@ Line 39: / Line 39: @@
 ==Incidents==
-===Authorization Control System (2025)===
+===Authorization Control System (''2025'')===
 {{Main|Bambu Lab Authorization Control System}}
-In early 2025, Bambu Lab announced changes to future firmwares that would implement a centralised authentication mechanism that regulated connections and control over the customer's 3D printer. This new firmware would be mandatory to install and could have prevented the customer's printer from functioning until it had been. This effectively forced customers to agree to new Terms and Conditions surrounding the use of their printer, which they did not agree with upon purchase of the product.<ref>{{Cite web |last=Tyrer-Jones |first=Alex |date=20 Jan 2025 |title=Bambu Lab Responds to Backlash Over New Firmware Update |url=https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |url-status=live |archive-url=https://web.archive.org/web/20250214090029/https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |archive-date=14 Feb 2025 |access-date=1 May 2025 |website=3D Printing Industry}} </ref>
+In early 2025, Bambu Lab announced changes to future firmwares that would implement a centralised authentication mechanism that regulated connections and control over the customer's 3D printer. This new firmware would be mandatory to install and could have prevented the customer's printer from functioning until it had been. This effectively forced customers to agree to new Terms and Conditions surrounding the use of their printer, which they did not agree with upon purchase of the product.<ref>{{Cite web |last=Tyrer-Jones |first=Alex |date=20 Jan 2025 |title=Bambu Lab Responds to Backlash Over New Firmware Update |url=https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |url-status=live |archive-url=https://web.archive.org/web/20250214090029/https://3dprintingindustry.com/news/bambu-lab-responds-to-backlash-over-new-firmware-update-235771/ |archive-date=14 Feb 2025 |access-date=1 May 2025 |website=3D Printing Industry}}</ref>
 This new authentication mechanism resulted in numerous designed-for and compatible third-party products, both software and hardware, being made incompatible with the printers going forward. The chief products affected were (including but not limited to): Panda Touch, OrcaSlicer, any third-party product making use of the MQTT protocol. Soon after the updated software was released, users managed to [[Bambu private keys leaked less than 24 hours after announcement|extract necessary security keys]] from it to continue using their third-party products. Amendments have presently been made that would allow some or all of these products to work with workarounds or extra software or tools from Bambu embedded into these products.
@@ Line 49: / Line 50: @@
 Bambu Lab vocally spoke out against the public's reaction, calling many of the valid concerns "unfortunate misinformation", "false accusations" and "baseless allegations".<ref name="bambu-connect-response">{{Cite web |date=20 Jan 2025 |title=Updates and Third-Party Integration with Bambu Connect |url=https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/ |url-status=live |archive-url=https://web.archive.org/web/20260216001409/https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/ |archive-date=16 Feb 2026 |access-date=19 Mar 2025 |website=[[Bambu Lab]] Blog}}</ref> The company's initial blog post announcing the firmware changes was also edited after publication to include an FAQ section addressing whether users could remain on old firmware, a section that was not present on the day of the announcement when community members first raised their concerns.<ref name="firmware-update-introducing-new-authorization-control-system-2" />
-===Cease and desist against OrcaSlicer fork maintainer (2026)===
+===Cease and desist against OrcaSlicer fork maintainer (''2026'')===
 {{Main|Bambu Lab Authorization Control System#Cease_and_desist_against_the_OrcaSlicer-bambulab_re-enablement_project}}
 In April 2026, Bambu Lab sent a private cease-and-desist demand to Pawel Jarczak, a Polish developer who had published an OrcaSlicer fork restoring direct printer control on top of Bambu Lab's own AGPL-licensed source code. Bambu Lab alleged the fork constituted impersonation of Bambu Studio, bypassed authorization controls, violated their Terms of Use, and involved reverse engineering.<ref name="jarczak-readme">{{Cite web |last=Jarczak |first=Pawel |title=OrcaSlicer-bambulab — This is the end…. |url=https://github.com/jarczakpawel/OrcaSlicer-bambulab |url-status=live |archive-url=https://web.archive.org/web/20260430001537/https://github.com/jarczakpawel/OrcaSlicer-bambulab |archive-date=2026-04-30 |access-date=2026-05-04 |website=[[GitHub]]}}</ref> Jarczak rejected these characterizations, stating his work was based on publicly available AGPL source code, and asked for specifics about which files or commits were at issue. He reports receiving further broad accusations rather than specificity.<ref name="jarczak-readme" />
-Jarczak removed the repository voluntarily but stated the removal should not be interpreted as an admission that the legal or technical allegations were correct.<ref name="jarczak-readme" /> On May 7, 2026, Bambu Lab published a blog post recharacterizing the dispute as being about "impersonation" through a "falsified" HTTP User-Agent string, rather than about open-source rights.<ref name="bambu-blog-record-straight">{{Cite web |title=Setting the record straight on Cloud Access and Community |url=https://blog.bambulab.com/setting-the-record-straight-on-cloud-access-and-community/ |website=Bambu Lab Blog |publisher=Bambu Lab |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref> The User-Agent string in question is generated by Bambu Lab's own AGPL-licensed source code in <code>src/slic3r/Utils/Http.cpp</code>.<ref>{{Cite web |title=Http.cpp source file (User-Agent setter at line 175) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/Http.cpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref>
+Jarczak removed the repository voluntarily but stated the removal should not be interpreted as an admission that the legal or technical allegations were correct.<ref name="jarczak-readme" /> On May 7, 2026, Bambu Lab published a blog post re-characterizing the dispute as being about "impersonation" through a "falsified" HTTP User-Agent string, rather than about open-source rights.<ref name="bambu-blog-record-straight">{{Cite web |title=Setting the record straight on Cloud Access and Community |url=https://blog.bambulab.com/setting-the-record-straight-on-cloud-access-and-community/ |website=Bambu Lab Blog |publisher=Bambu Lab |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref> The User-Agent string in question is generated by Bambu Lab's own AGPL-licensed source code in <code>src/slic3r/Utils/Http.cpp</code>.<ref>{{Cite web |title=Http.cpp source file (User-Agent setter at line 175) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/Http.cpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref>
 The incident was covered by XDA Developers, Tom's Hardware, 3Druck, and Manufactur3D, and became a flashpoint in the wider 3D-printing community over open-source licensing and consumer rights.<ref>{{Cite web |last=Batt |first=Simon |date=2026-04-23 |title=A developer restored OrcaSlicer's features that Bambu Lab killed — then the legal threats arrived |url=https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |url-status=live |archive-url=https://web.archive.org/web/20260427233833/https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |archive-date=2026-04-27 |access-date=2026-05-04 |website=XDA Developers}}</ref><ref>{{Cite web |title=Developer re-enables 3D printer features that Bambu Lab disabled, firm promptly threatens legal action — OrcaSlicer-BambuLab project now shuttered |url=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 |website=Tom's Hardware |date=2026-04-29 |access-date=2026-05-10 |url-status=live}}</ref>
@@ Line 59: / Line 61: @@
 ===Farm Manager subscription potential===
 {{Main|Bambu Farm Manager}}
 Bambu Lab's Farm Manager EULA contains language reserving the right to introduce fees for the software and connected services, including for commercial uses. The EULA states in capitalised text that the company "MAY CHARGE A FEE TO CERTAIN USERS OR FOR CERTAIN USES (E.G. COMMERCIAL USES)" and "RESERVES THE RIGHT TO AND MAY CHANGE THE LICENSE AND FEE STRUCTURE."<ref>{{Cite web |date=2025-05-27 |title=BAMBU FARM MANAGER EULA AND SERVICE AGREEMENT |url=https://bambulab.com/en/policies/bambu-farm-manager-service-agreement |url-status=live |archive-url=https://ghostarchive.org/archive/3ZHOP |archive-date=2026-03-07 |access-date=19 Mar 2025 |website=[[Bambu Lab]]}}</ref> Despite publicly denying any subscription model,<ref name="bambu-connect-response" /> the EULA language establishes the contractual groundwork for one.
 ===Helio Additive===
-In mid 2025, Bambu Lab added a new functionality in a form of a third party cloud service where you can send your design to get a thermal analysis, which can be used later to optimize the print adjusting the temperature (for [https://www.helioadditive.com/pricing paid membership]). Besides privacy concerns of sharing the designs with a Chinese startup, the functionality is restricted to an online-only model, with no offline simulation alternative, limiting potential open-source or community-driven innovation.
+In mid-2025, Bambu Lab added a new functionality in a form of a third party cloud service where you can send your design to get a thermal analysis, which can be used later to optimize the print adjusting the temperature (for [https://www.helioadditive.com/pricing paid membership]). Besides privacy concerns of sharing the designs with a Chinese startup, the functionality is restricted to an online-only model, with no offline simulation alternative, limiting potential open-source or community-driven innovation.
 ==Comparisons to similar practices==