Loading...
Loading...
A thawing battle between Bambu Lab and the open‑source community spotlights copyleft enforcement and user control of connected 3D printers. The Software Freedom Conservancy says Bambu distributed an AGPLv3‑derived PrusaSlicer (Bambu Studio) tied to a proprietary networking library without providing required Corresponding Source or installation info, prompting formal action and fundraising for enforcement and right‑to‑repair work. Separately, Bambu’s public threats toward a community fork (OrcaSlicer‑bambulab), which enables local printing to avoid cloud routing, have drawn criticism for chilling contributors and dodging design choices that push cloud dependency. The saga underscores how vendor practices shape software freedom, privacy, and ecosystem trust.
The dispute affects how vendors can combine copyleft code with proprietary components for connected devices, with implications for developer rights, user control, and trust in device ecosystems. Tech professionals building or integrating firmware, cloud services, or community forks must understand compliance obligations and potential risks to contributor engagement.
Dossier last updated: 2026-05-22 13:11:16
Software Freedom Conservancy (SFC) says it has confirmed at least two AGPLv3 violations by 3D‑printer maker Bambu Lab after a compliance investigation. The main confirmed violation: Bambu distributed a modified AGPLv3 PrusaSlicer (Bambu Studio) tied to a proprietary networking library (libbambu_networking) without providing the complete Corresponding Source or installation information for the library across platforms (.so/.dll/.dylib), which SFC says breaches AGPLv3 §6 and related clauses. SFC also reports aggressive actions by Bambu that create a chilling effect on developers; the organization is pursuing multi‑pronged remediation to restore users’ software right to repair and is fundraising to support sustained enforcement. The outcome could affect copyleft enforcement, OEM open‑source obligations, and 3D‑printer user freedoms.
Software Freedom Conservancy (SFC) announced a targeted action over confirmed AGPLv3 license violations by 3D-printer maker Bambu Lab. SFC's investigation found Bambu failed to provide Corresponding Source and installation information for a proprietary networking library (libbambu_networking.*) used with Bambu Studio, which Bambu publicly admits derives from AGPLv3-licensed PrusaSlicer. SFC says this withholding and distribution method violates AGPLv3’s requirements for source, shared libraries, and installation scripts. The Conservancy is pursuing a multi-pronged response to quickly help users and seek a long-term remedy, while fundraising to support right-to-repair work and further compliance enforcement. The case underscores license enforcement’s role in open-source software interoperability and user repair rights.
Bambu Lab publicly accused a small open-source fork of OrcaSlicer (OrcaSlicer-bambulab) of impersonating its official Bambu Studio client and threatening infrastructure, sparking backlash from community users and the fork’s developer. The fork exists because Bambu Studio’s default cloud-centric workflow routes print jobs through Bambu’s servers, which some users reject for privacy and control reasons; forks enable local-only use. Bambu’s public statement and reported legal threats have been criticized as heavy-handed, harming trust with power users and open-source contributors. The dispute raises questions about vendor control over AGPL-licensed ecosystems, responsible security practices, and how companies should engage with community forks rather than litigate or publicly shame developers.
Bambu Lab publicly accused a forked OrcaSlicer developer of impersonation and security risks after the fork allowed users to run Bambu 3D printers without routing jobs through Bambu's cloud. The fork, OrcaSlicer-bambulab, uses AGPLv3-licensed upstream Bambu Studio code to enable local control; Bambu responded with a blog post threatening legal action and claiming falsified identity metadata in client-server communication. The author argues Bambu’s response abuses the open-source social contract, chills community contributions, and sidesteps addressing design choices that make the cloud the default. This matters because vendor actions against open-source forks can reshape hardware control, user privacy, and ecosystem security norms for connected consumer devices.