GitHub Analysis Alleges AGPL Violation in Bambu Studio’s Closed-Source Networking Component
A detailed examination of Bambu Studio’s source code suggests the software’s closed-source bambu_networking component is dynamically linked in a manner that requires disclosure under the AGPL v3 license, challenging the company’s distribution model.
A technical analysis published on GitHub argues that Bambu Studio, the popular 3D printing slicer developed by Bambu Lab, is in breach of the GNU Affero General Public License (AGPL) v3. The review contends that the software’s integration of the closed-source bambu_networking component constitutes a violation of licensing terms because the module is not an independent plugin but a dynamically linked runtime component that shares intimate data communication and control flow with the main application.
The analysis, authored by a GitHub user, asserts that under AGPL v3, the source code for such dynamically linked subprograms must be disclosed as "Corresponding Source." The author points to specific code structures, including bambu_networking.hpp and NetworkAgent.cpp, to demonstrate that the component is downloaded, installed, and dynamically loaded as an integral part of the program’s operation. This architecture, the argument goes, prevents the component from being classified as a separate aggregate or an optional user-installed add-on.
Key technical evidence cited in the report includes the use of callbacks, such as QueueOnMainFn, which allow the plugin to execute functions on the main user interface thread of Bambu Studio. The code also reveals shared data structures, including PrintParams, which contain printer details, project information, and connection settings. These elements indicate a tight coupling between the open-source slicer and the proprietary networking module, satisfying the AGPL’s definition of intimate data communication.
The review further highlights that Bambu Studio contains built-in mechanisms to download and update bambu_networking, including version checks and certificate validation. This suggests the component is a managed runtime element rather than a neutral interface for arbitrary implementations. The analysis notes that network printing paths, including local area network workflows, are routed through the bambu_networking layer, making it essential for core network functions despite the fact that SD card workflows remain functional without it.
The author distinguishes this licensing dispute from broader issues regarding cloud access terms, framing it strictly as a distribution compliance problem under copyright law. The argument concludes that because Bambu Studio is derived from AGPL-licensed code, it cannot unilaterally move key runtime parts into a closed binary boundary without providing the corresponding source code, unless explicit permissions are obtained from all copyright holders of the underlying AGPL code.
