HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bambulab
BambuStudio
C++2023–2026
bambulab / BambuStudio

BambuStudio

PC Software for BambuLab and other 3D printers

12Distinct people
15Mentions
0Explicit recommenders
5.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

PC Software for BambuLab and other 3D printers

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year15 dated mentions

Observed mentions: 2023-09-23 09:47:22 UTC to 2026-08-27 04:50:03 UTC.

02462023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC413
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC321
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC707

What Hacker News says

15 sources
* 2022-05-23: KickStarter launch, distributing Bambu Studio binaries to every backer, reviewer and influencer *without source code*. They also sanitized the About dialog and removed any open-source attributions, AGPL disclosures, or links to the underlying PrusaSlicer/Slic3r code. [https://www.reddit.com/r/BambuLab/comments/vnzpie/comment/ie...](https://www.reddit.com/r/BambuLab/comments/vnzpie/comment/ie...) * 2022-05-29: Admitted it's based on PrusaSlicer [https://blog.bambulab.com/to-open-or-not-to-open-that-is-the...](https://blog.bambulab.com/to-open-or-not-to-open-that-is-the...) * "We would like to ask for the understanding of the community to give us some time *before we open-source* Parts 1 and 2, which is scheduled for the second half of this year." - admitted it's currently an AGPL violation * 2022-06-29: Evidence. "GPL requ
Read the rest
ires release of source the moment binaries are out. Many people have had the binaries for weeks. They are 100% in violation". [https://x.com/DreadMakerAdam/status/1542216014984876036](https://x.com/DreadMakerAdam/status/1542216014984876036) * ??? * 2022-07-15: They only dumped it (with prior git history squashed) onto GitHub months after the initial release, after immense community pressure. [https://www.reddit.com/r/OpenBambu/comments/1thfslw/comment/...](https://www.reddit.com/r/OpenBambu/comments/1thfslw/comment/...) [https://github.com/bambulab/BambuStudio/issues/1](https://github.com/bambulab/BambuStudio/issues/1)
In An ongoing 3D-printer AGPL violation
> Kühn said; they often rely on mechanisms that an actual judge is not going to care about. In this case, Bambu Studio would pop up a request to download "a little more stuff" with the classic choices of "Yes" or "Ask me later"; users eventually figure out that some functionality in the slicer does not work until they click "Yes". The extras that are downloaded are two .so files built from C++ source. Those shared-library files are dynamically loaded into the slicer—as can plainly be seen from the dlopen() calls in the source code that was released. This seems to be the main complaint: They ship a separate .so as a plugin. Saying that an actual judge is not going to care about it is confusing. Is this or is it not consistent with the license? Why wouldn't a judge care about something that is a license violation? I don't get it. > violatin
Read the rest
g GPLv2 by not providing the source for a Buildroot-based Linux (and other copyleft components) used in the firmware of some 3D-printer models. He downloaded the 300MB firmware image from the Bambu Lab web site, but was unable to find the source or an offer to provide it. This was the first hit when I googled it: https://wiki.bambulab.com/en/knowledge-sharing/open-source-s.... Includes the e-mail address opensource@bambulab.com for requests Is there some other technicality that I'm missing? > Bambu Lab needed a slicer, of course, so it started shipping a modified PrusaSlicer (as Bambu Studio), which it was able to get via the AGPLv3, but without shipping any source code or an offer to provide it. That continued up through 2022 or 2023, Kühn said, until the pressure from the 3D-printing community effectively forced Bambu Lab to make a source release, which was, as is almost always the case for a first release, not the actual corresponding source code. I googled Bambu's first Kickstarter. It shows July 2022 as the estimated ship date. The BambuStudio repo has public issues from July 2022 with public user comments - https://github.com/bambulab/BambuStudio/issues/12 So the repo was public and available around the time that the Kickstarter ended. Seems fair? He acts like they were refusing until the community forced them to do it a year later, but the repo was live and open when the printers shipped. I get that Bambu is supposed to be the enemy and we're not supposed to defend the enemy unless we want a lot of downvotes, but the reporting on this issue seems lacking any fact checking. I didn't try very hard but found contradictory evidence in the first Google link for several of the claims. The article is quoting someone speaking from memory to an audience so mistakes are understandable, but I would at minimum expect some cursory fact checking for someone reporting on it.
In An ongoing 3D-printer AGPL violation
This is false. After the authorization-related firmware changes last year LAN mode doesn't allow 3rd party slicers to connect. LAN mode is also abandonware with numerous issues and missing features that they've had no interest in fixing. Orca slicer has had to rely on hacky workarounds in Bambu's buggy networking plugin just to be able to connect to printers in a different subnet. https://github.com/bambulab/BambuStudio/issues/4512
In Bambu Lab is abusing the open source social contract
Something I just thought of under the shower: A user can build the slicer from scratch and the UA is public on their repo [0]. If one is determined to do so, using the same deps, pinning the date, etc., they could create a deterministic build identical to what Bambu offers for download on their website. Will using such a build be an issue for Bambu? If not, what degree of modification would be needed for them to view building with their publicly available UA as bypassing a security measure/improperly accessing their services? Where exactly is the line here? Does their EULA define what percentage of the source code may be modified to view using their UA as acceptable? If not, is this something that one could enforce if they wanted to? Also, what about 10NES [1]? The courts found that reverse engineering such a measure would be lawful, the
Read the rest
basis of much that came later with Phoenix, Compaq, etc. If reverse engineering is acceptable, why wouldn't using AGPL licensed code? In both cases, the required information was acquired 100% legally. [0] https://github.com/bambulab/BambuStudio/blob/3e96c7e073fdc14... [1] https://en.wikipedia.org/wiki/Atari_Games_Corp._v._Nintendo_....
In Hey Bambu Lab: come sue us [video]
We've strayed so far off topic. Try to get a handle on your fanboyism and you might be able to see this discussion more rationally. Why do you feel the need to justify your purchase in public and talk about how great the printer is? Bambu make good printers and nobody is disputing that. And for the record, my own experience hasn't been terrible at all, it's been predominantly positive. However that doesn't change the fact that their overall dishonest corporate behavior, pushing unjustified user-hostile changes after the sale, violating the AGPL license of Prusa slicer, and legally bullying independent developers is immoral, illegal, and generally indefensible. Nobody wants to live in a world where this sort of behavior is normalized. Furthermore "LAN only mode" has been neglected and generally half-broken for years. It was a hobbled alter
Read the rest
native before they broke it even further. https://github.com/bambulab/BambuStudio/issues/4512 > I prefer security at the network level You do you, but the world has moved on since the 90s. Communication is expected to be end to end encrypted, credentials should be revocable, and you generally don't want to grant every process on your device unrestricted ability to set your house on fire. Disgracefully, this is being done in the name of "security".
In Bambu Lab is abusing the open source social contract
An extra point that it is too late to edit in, on openness wrt software: unlike some companies we could all mention, they are playing right with the slicer software. It is heavily based on earlier AGPL3 licensed software and their work is correctly licensed also: https://github.com/bambulab/BambuStudio/blob/master/LICENSE There might be some question as to whether anything like the connectivity layer that sits between BS and the printer that currently isn't open, should also be AGPL. I'll leave discussion of how AGPL and losly linked components do/n't work together to people with more experience in the area…
In Reverse Engineering Bambu Connect
botolo·Dec 19, 2023Submission

How to Decrypt Log Files?

There is currently huge debate in the 3D printing world related to information logged by Bambu Lab printers. Those printers encrypt their logged files and I’m curious to see if there is a way to decrypt them to finally seen what kind of information is stored and tracked. Here are some sample files. What would be the first step to attempt to decrypt them? Is there a way to see which encryption method they are using and then throw hashpower to these files using tools like hashcat? https://github.com/bambulab/BambuStudio/issues/1261#issuecomment-1423022959
1 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.