BambuStudio has been violating PrusaSlicer AGPL license since their fork

A popular Chinese 3D printer maker is accused of violating the AGPL license of an open source slicer it forked, reigniting worries about how easily copyleft licenses can be ignored when enforcement across borders is costly or impractical. Commenters debate whether the company’s cloud‑centric, partially closed ecosystem and DMCA threats reflect simple cultural and legal mismatch around open source, or a deliberate strategy that exploits weak IP enforcement while harvesting valuable user and industrial design data. The thread also touches on how much pressure should come from courts versus public shaming and boycotts, and whether users should favor more open, locally controlled printer platforms instead.

Alleged AGPL Violation & Technical Dispute

  • Thread centers on claims that Bambu Studio, a fork of PrusaSlicer (AGPL), violates the license by using a closed-source network/cloud plugin.
  • Key disagreement: is the plugin a “separate work” (permissible) or part of a single combined program (copyleft should apply)?
  • Some argue the slicer is usable over LAN/dev mode without the plugin, so it’s not essential; others say primary functionality depends on it, making separation artificial.
  • Boundary between “combined work” and “aggregate” under GPL/AGPL is widely acknowledged as fuzzy and legally untested here.

Enforceability of AGPL & Legal Strategy

  • Many see copyleft licenses as vulnerable: enforcement is expensive, violations are hard to prove, and there’s little case law, especially on AGPL.
  • Specific concern: no precedent for enforcing AGPL against Chinese companies; jurisdiction would likely be Chinese courts applying Chinese law.
  • Software Freedom Conservancy is mentioned as active (e.g., Vizio GPL case), but bandwidth and cost are limiting; some want more aggressive lawsuits and import bans.
  • Others note that licenses don’t “force” publication; they condition the right to use. Remedies would more likely be termination/damages than compelled disclosure.

China, IP, and Cultural/Political Context

  • Several comments frame this as part of a broader pattern of weak IP enforcement in China and state-backed industrial strategy.
  • Counter-views say it’s less nefarious and more about different norms: what’s available is assumed usable, and open-source expectations are poorly understood.
  • Others reject the “cultural misunderstanding” framing, arguing Chinese companies demonstrably understand Western IP when it benefits them (e.g., DMCA threats).

Cloud Connectivity, Privacy, and Industrial Espionage

  • Strong concern over Bambu’s cloud-centric model and potential exfiltration of sensitive 3D models: product prototypes, commercial parts, even defense components.
  • Some see this as “free” industrial espionage vs. firms that avoided building their own printer farms.
  • Skeptics argue: high‑sensitivity users already avoid cloud (LAN/SD only), prototypes may be low-value shells, and defense manufacturers wouldn’t use these printers.
  • Additional worries include possible future requirements for model metadata, capture of Wi‑Fi credentials, and proposed US state laws that could restrict fully offline use.

Open Source Ethics & Social Enforcement

  • Many see Bambu’s behavior (if the claims hold) as an unethical “free ride” on AGPL code to cut development costs.
  • Legal tools are perceived as weak or impractical, so people advocate social pressure and boycotts as the primary enforcement mechanism.
  • Others dislike public shaming as “performative,” preferring clear legal actions and precedents; they doubt social campaigns will significantly affect sales.

Impact on Buying Decisions & Alternatives

  • Some prospective buyers say this controversy pushed them away from Bambu toward alternatives (Prusa, Voron, Qidi, Creality, Elegoo, etc.), especially for business or IP‑sensitive use.
  • Others prioritize reliability and “it just works” experience, viewing Bambu as the “Apple of 3D printing” and arguing most hobbyists won’t care about licensing or cloud issues.
  • There’s active interest in fully or mostly open, offline-capable printers (Voron builds, Klipper/Marlin-based machines) as a way to retain control and avoid vendor lock‑in.