SFC Closes $250,007 Baltobu Fundraiser; Bambu Compliance Dispute Continues
Software Freedom Conservancy says its software right-to-repair fundraiser closed at $250,007. The money will support its continuing AGPL compliance work involving Bambu Studio and an OrcaSlicer fork.
Software Freedom Conservancy says the baltobu campaign closed at $250,007. Its May 18 statement describes two unresolved allegations: incomplete corresponding source involving Bambu Studio and networking libraries, and a separate AGPL section 10 restriction involving an OrcaSlicer fork. The campaign is complete; the compliance dispute is not.
ReportSoftware Freedom Conservancy
SFC closes its fundraiser, with two attributed Bambu software claims still open
Software Freedom Conservancy announced on July 16 that the baltobu software right-to-repair campaign had reached $250,007, just above its $250,000 target, and the campaign is now marked complete. SFC says the funds will support legal and technical work on two unresolved AGPL matters involving Bambu Lab software. In its May 18 account, SFC described one matter as incomplete corresponding source for Bambu Studio and networking libraries. It described the other as a separate AGPL section 10 restriction tied to Bambu's demand that an OrcaSlicer fork be removed. Those are SFC's allegations and interpretations of the license; this brief does not present them as a court or regulator's finding. The fundraiser result establishes that the campaign met its funding goal, not that either dispute has been resolved.
For owners and developers, the useful next signal is documentary: source releases, policy changes, or a dated resolution from the organizations involved. The funding total does not establish a hardware defect, safety issue, or outcome in the software-license dispute.
What the fundraiser result establishes
Confirmed by SFC: the campaign reached $250,007 and is complete. SFC's May 18 statement describes incomplete corresponding source involving Bambu Studio and networking libraries, plus a separate allegation that a demand to remove an OrcaSlicer fork imposed a further restriction barred by AGPL section 10. The statements are SFC's account of an ongoing license-compliance dispute, not an adjudicated ruling.
What it changes: The development is about software licensing and source access rather than printer specifications. It matters most to readers who weigh repairability, open-source compliance, and long-term software access alongside hardware performance.
- What legal or technical work will SFC publish after deploying the fundraiser proceeds?
- Will new source releases or policy changes narrow either disputed issue?
- Will the parties publish a dated resolution or a more specific compliance roadmap?
What to monitor:Look for primary-source changes to the released source, licensing terms, or an announced resolution rather than treating the fundraiser total as the outcome
Keep in perspective:This dispute concerns software-license compliance and source access; it does not by itself establish that a particular printer is unsafe or unusable
Primary pages and records used for this report.
Frequently Asked Questions
Did the SFC baltobu fundraiser reach its goal?▼
Yes. Software Freedom Conservancy reported that the campaign reached $250,007, above its $250,000 target, and is complete. SFC says the money will support continuing legal and technical work.
What Bambu software issues does SFC describe?▼
SFC's May 18 statement describes incomplete corresponding source involving Bambu Studio and networking libraries, plus a separate AGPL section 10 restriction involving a demand to remove an OrcaSlicer fork. These are SFC's allegations in an ongoing compliance dispute, not an adjudicated finding.
Have a launch, correction, or test opportunity?
Brands, product teams, and knowledgeable sources can send relevant details, approved media, or corrections. Coverage is selected independently.
Choose the useful next step.
Know what changed before it changes your workshop.
When a source-backed change affects what to buy, update, test, or ignore, we send a short decision brief with the evidence, the workshop consequence, and what remains unknown.
Know what changed. Know what it means at the bench. Decide whether to act, wait, update, test, or ignore.
Scanned daily. Sent only when the signal changes a workshop decision, with a rare alert when waiting would matter.
See how The Workshop Signal works