Consumer Rights Wiki

Bambu Lab: Difference between revisions

← Older edit
VisualWikitext
No edit summary
forgot to add an edit note to the prev edit: added consumer impact summary and updated the page to reflect recent developments and all issues covered on the wiki
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{StubNotice}}
{{CompanyCargo
{{CompanyCargo
|Description=
|Description=
Line 11: Line 10:
[[wikipedia:Bambu_Lab|'''Bambu Lab''']] is a Chinese technology company that designs and manufactures 3D printers. The company is based in Shenzhen, China, with locations in Shanghai and Austin, Texas. It was founded in 2020 by a group of ex-[[DJI]] engineers.
[[wikipedia:Bambu_Lab|'''Bambu Lab''']] is a Chinese technology company that designs and manufactures 3D printers. The company is based in Shenzhen, China, with locations in Shanghai and Austin, Texas. It was founded in 2020 by a group of ex-[[DJI]] engineers.


Alongside 3D printers, Bambu Lab also sells its own brand of 3D printer filament on spools with embedded NFC tags that describe the filament material, type, model. The NFC tags are meant to interact with a corresponding NFC tag reader inside their proprietary AMS (Automatic Material System).<ref>{{Cite web |date=2026-03-18 |title=PLA Basic |url=https://ca.store.bambulab.com/products/pla-basic-filament |url-status=live |access-date=2026-03-18 |website=Bambulab Store}}</ref> A group of researchers by the name [https://github.com/Bambu-Research-Group/RFID-Tag-Guide Bambu Research Group] has since managed to reverse-engineer these tags, although not managing to make their own custom tags. Their project's documentation also mentions their efforts may be slowed down due to fear of repercussions from Bambu Lab.
Alongside 3D printers, Bambu Lab also sells its own brand of 3D printer filament on spools with embedded NFC tags that describe the filament material, type, model. The NFC tags are meant to interact with a corresponding NFC tag reader inside their proprietary AMS (Automatic Material System).<ref>{{Cite web |author= |title=PLA Basic |url=https://ca.store.bambulab.com/products/pla-basic-filament |website=Bambu Lab |date=18 Mar 2026 |access-date=10 May 2026 |url-status=live|archive-url=|archive-date=}}</ref> A group of researchers by the name [https://github.com/Bambu-Research-Group/RFID-Tag-Guide Bambu Research Group] has since managed to reverse-engineer these tags, although not managing to make their own custom tags. Their project's documentation also mentions their efforts may be slowed down due to fear of repercussions from Bambu Lab.


Bambu Lab's official accompanying software package is [https://github.com/bambulab/BambuStudio Bambu Studio], which handles the converting ([https://wikipedia.org/wiki/Slicer_(3D_printing) slicing]) of digital model files into compatible [https://wikipedia.org/wiki/G-code G-code] that the 3D printer can read and process. It is based on the open-source software [https://github.com/prusa3d/PrusaSlicer PrusaSlicer], and draws the majority of its inner workings from it.<ref>{{Cite web |last=@bambulab |title=PC Software for BambuLab and other 3D printers |url=https://github.com/bambulab/BambuStudio#bambustudio |url-status=live |access-date=1 May 2025 |website=GitHub |archive-url=https://web.archive.org/web/20250510135316/https://github.com/bambulab/BambuStudio#bambustudio |archive-date= 10 May 2025}}</ref>
Bambu Lab's official accompanying software package is [https://github.com/bambulab/BambuStudio Bambu Studio], which handles the converting ([[Wikipedia:Slicer_(3D_printing)|slicing]]) of digital model files into compatible [[Wikipedia:/G-code|G-code]] that the 3D printer can read and process. It is based on the open-source software [https://github.com/prusa3d/PrusaSlicer PrusaSlicer], and draws the majority of its inner workings from it.<ref>{{Cite web |last=@bambulab |title=PC Software for BambuLab and other 3D printers |url=https://github.com/bambulab/BambuStudio#bambustudio |url-status=live |access-date=1 May 2025 |website=GitHub |archive-url=https://web.archive.org/web/20250510135316/https://github.com/bambulab/BambuStudio#bambustudio |archive-date=10 May 2025}}</ref> Bambu Studio is released under the [[Wikipedia:GNU Affero General Public License|AGPL-3.0]] license,<ref name="bambustudio-license">{{Cite web |title=BambuStudio LICENSE (AGPL-3.0 verbatim) |url=https://github.com/bambulab/BambuStudio/blob/master/LICENSE |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref> which grants anyone the right to use, modify, and redistribute the source code. However, Bambu Lab's [[Terms of Service|Terms of Use]] contain clauses that appear to contradict this grant, forbidding users from modifying, copying, reverse engineering, or creating derivatives of "the Product."<ref name=":2">{{Cite web |date=2024-04-24 |title=Terms of Use |url=https://bambulab.com/en-us/policies/terms |url-status=live |archive-url=https://ghostarchive.org/archive/vPu9I |archive-date=2026-03-09 |access-date=2025-05-01 |website=[[Bambu Lab]]}}</ref>


==Consumer impact summary==
==Consumer impact summary==
<nowiki>*</nowiki> User Freedom:


<nowiki>*</nowiki> User Privacy:
===Post-purchase restriction of functionality===
Bambu Lab has implemented firmware changes that gate previously available printer features behind mandatory cloud authentication, effectively altering the terms under which customers purchased their printers. Owners who update to the new firmware lose the ability to use third-party slicers and accessories without routing through Bambu's proprietary middleware, Bambu Connect.<ref name="firmware-update-introducing-new-authorization-control-system-2">{{Cite web |last=Bambu Kidd |date=2025-01-16 |title=Firmware Update Introducing New Authorization Control System |url=https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/ |url-status=live |archive-url=https://ghostarchive.org/archive/qwL63 |archive-date=2026-03-07 |website=[[Bambu Lab]] Blog}}</ref> Features restricted behind the new authentication path include:


<nowiki>*</nowiki> Business Model:
*Initializing prints via LAN or cloud mode
*Remote video access to monitor prints
*Controlling motion system, temperature, and fans
*AMS settings and calibrations
*Home automation integration beyond basic status monitoring<ref name="bambu-connect">{{Cite web |[email protected] |title=Bambu Connect (beta) |url=https://wiki.bambulab.com/en/software/bambu-connect |url-status=live |archive-url=https://ghostarchive.org/archive/CVCtK |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Wiki}}</ref>


<nowiki>*</nowiki> Market Control:
===Third-party product incompatibility===
The authorization system rendered numerous third-party products incompatible with Bambu printers, including the popular Panda Touch accessory from Big Tree Tech (BTT) and the widely used OrcaSlicer software. BTT urged its customers not to update their firmware, as doing so would permanently break compatibility with the Panda Touch.<ref name=":0">{{Cite web |last=@BIGTREETECH |date=2025-01-17 |title=BIGTREETECH's post |url=https://www.facebook.com/BIGTREETECH/posts/pfbid0SNZGxvf7NRdmyVgHf6y9yNedNbU2RrCfdT8gugTSD4AYfr5BHneNF9H1EbwyYiJEl |url-status=live |archive-url=http://web.archive.org/web/20251004104021/https://www.facebook.com/BIGTREETECH/posts/pfbid0SNZGxvf7NRdmyVgHf6y9yNedNbU2RrCfdT8gugTSD4AYfr5BHneNF9H1EbwyYiJEl |archive-date=2025-10-04 |website=[[Facebook]]}}</ref> OrcaSlicer's lead developer, SoftFever, was not provided API keys for Bambu Connect and stated publicly that direct print sending from OrcaSlicer would no longer be supported.<ref name=":1">{{Cite web |last=@fever_soft |date=2025-01-18 |title=This is definitely a bummer. I was negotiating for an authorization key to allow OrcaSlicer to communicate with their device like BambuStudio does, but today I was told they won't support this. Only their slicer can send prints directly; others must use their Bambu Connect application |url=https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q |url-status=live |access-date=2025-05-01 |website=[[X]] |archive-url=http://web.archive.org/web/20251004104021/https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q |archive-date=2025-10-04}}</ref>
 
===Privacy and data collection===
Bambu Lab's privacy policy describes that when a user submits a print job through Bambu cloud, the company may forward configuration information, printing settings, model pictures, plate thumbnails, and G-code files. When the print history reprinting feature is enabled, Bambu may also store start times, finish times, and filament consumption data.<ref name=":6">{{Cite web |date=2025-03-25 |title=Privacy Policy |url=https://bambulab.com/en-us/policies/privacy |url-status=live |archive-url=https://ghostarchive.org/archive/0XOv5 |archive-date=2026-03-10 |access-date=2025-05-01 |website=[[Bambu Lab]]}}</ref>
 
===Open-source licensing conflict===
Bambu Lab publishes Bambu Studio under the AGPL-3.0 license, which explicitly grants users the right to modify, copy, and redistribute the software. At the same time, the company's Terms of Use § 3.4 forbid users from modifying, copying, reverse engineering, or creating derivatives of "the Product."<ref name=":2" /> These two positions are in direct contradiction: AGPL § 10 prohibits the licensor from imposing further restrictions on the rights the license grants, and AGPL § 7 allows downstream recipients to strip any additional terms that exceed the license's permitted list.<ref name="agpl3-section10">{{Cite web |title=GNU Affero General Public License Version 3, Section 10 (Automatic Licensing of Downstream Recipients) |url=https://www.gnu.org/licenses/agpl-3.0.html#section10 |website=GNU Project |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-05-10 |url-status=live}}</ref>
 
===Restrictions on third-party development===
Bambu Lab's Terms of Use § 3.1 prohibits the use of Bambu Lab technology or intellectual property to develop software or third-party devices and accessories without the company's prior consent,<ref name=":2" /> a clause that has been present since at least January 2024.


==Incidents==
==Incidents==
Line 33: Line 46:
Bambu Lab later responded to public outrage and controversy over these changes, stating that feedback has been provided and they would amend the firmware's new security measures with developer options that would unlock the use of the 3D printer without connecting to Bambu Lab's services.<ref>{{Cite web |last=Rossmann |first=Louis |date=19 Jan 2025 |title=Bambu Lab Firmware Update Forces Cloud Dependency & User Lock-In - AVOID THEIR 3D PRINTERS! |url=https://www.youtube.com/watch?v=aIyaDD8onIE |url-status=live |access-date=1 May 2025 |website=[[YouTube]] |archive-url=https://preservetube.com/watch?v=aIyaDD8onIE |archive-date=19 Jan 2025}}</ref> However, the wording of these updates has been widely criticised by consumer rights conscious people as implying these were good-will gestures or extra granted rights, or that restriction of functionality was never on the roadmap.   
Bambu Lab later responded to public outrage and controversy over these changes, stating that feedback has been provided and they would amend the firmware's new security measures with developer options that would unlock the use of the 3D printer without connecting to Bambu Lab's services.<ref>{{Cite web |last=Rossmann |first=Louis |date=19 Jan 2025 |title=Bambu Lab Firmware Update Forces Cloud Dependency & User Lock-In - AVOID THEIR 3D PRINTERS! |url=https://www.youtube.com/watch?v=aIyaDD8onIE |url-status=live |access-date=1 May 2025 |website=[[YouTube]] |archive-url=https://preservetube.com/watch?v=aIyaDD8onIE |archive-date=19 Jan 2025}}</ref> However, the wording of these updates has been widely criticised by consumer rights conscious people as implying these were good-will gestures or extra granted rights, or that restriction of functionality was never on the roadmap.   


Bambu Lab vocally spoke out against the public's reaction, calling many of the valid concerns "unfortunate misinformation", "false accusations" and "baseless allegations".<ref>{{Cite web |last=@SpaghettiMonster |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/20260222212906/https://blog.bambulab.com/updates-and-third-party-integration-with-bambu-connect/ |archive-date=22 Feb 2026|access-date=1 May 2025 |website=Bambu Lab Blog}}</ref> It is notable that Bambu's recall of these accusations seems to fall on the creatively victimized interpretation side of the matter.
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)===
{{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>
 
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>
 
===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===
===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==
Bambu Lab's practices have drawn comparisons to other manufacturers who have faced backlash and litigation over post-purchase restrictions on consumer products.
[[HP]]'s printer firmware updates have rendered third-party ink cartridges unusable, leading to class-action settlements in both the United States and the European Union.<ref>{{Cite web |last=Harding |first=Scharon |date=2025-03-19 |title=HP avoids monetary damages over bricked printers in class-action settlement |url=https://arstechnica.com/gadgets/2025/03/hp-avoids-monetary-damages-over-bricked-printers-in-class-action-settlement/ |url-status=live |archive-url=http://web.archive.org/web/20250319231817/https://arstechnica.com/gadgets/2025/03/hp-avoids-monetary-damages-over-bricked-printers-in-class-action-settlement/ |archive-date=2025-03-19 |website=Ars Technica}}</ref> The Federal Trade Commission's May 2021 report ''Nixing the Fix'' described firmware-mediated cartridge restrictions as a recurring repair-policy issue.<ref>{{Cite web |title=Nixing the Fix: An FTC Report to Congress on Repair Restrictions |author=Federal Trade Commission |url=https://www.ftc.gov/system/files/documents/reports/nixing-fix-ftc-report-congress-repair-restrictions/nixing_the_fix_report_final_5521_630pm-508_002.pdf |website=Federal Trade Commission |date=2021-05-06 |access-date=2026-05-10 |url-status=live}}</ref>
Within the 3D-printing industry, the now-defunct manufacturer [[MakerBot]] followed a similar trajectory, shifting from open-source, DIY-focused machines to closed-source, proprietary ones, which ultimately drove customers to less-expensive open-source competitors and contributed to MakerBot losing its position as an industry leader.<ref>{{Cite web |last=Benchoff |first=Brian |date=2016-04-28 |title=The MakerBot Obituary |url=https://hackaday.com/2016/04/28/the-makerbot-obituary/ |url-status=live |archive-url=http://web.archive.org/web/20251208222057/https://hackaday.com/2016/04/28/the-makerbot-obituary/ |archive-date=2025-12-08 |access-date=2025-05-01 |website=[[Hackaday]]}}</ref>


==See also==
==See also==
Line 42: Line 75:
*[[Creality]]
*[[Creality]]
*[[MakerBot]]
*[[MakerBot]]
*[[Bambu Lab Authorization Control System]]
*[[Bambu Farm Manager]]
*[[Forced account]]
*[[Right to repair]]
*[[Terms of Service]]
*[[GNU Affero General Public License]]


==References==
==References==
<references />
<references />
[[Category:Bambu Lab]]
[[Category:Bambu Lab]]
[[Category:Feature Ransom]]
[[Category:3D printers]]
[[Category:Open source]]
Retrieved from "https://consumerrights.wiki/w/Bambu_Lab"