Does that answer your questions?

Use the integrated tailscale.

Need more infos. Please open an issue and attach a support package.

For what purpose? Don't see any reason for it.

For everyone sponsoring Bambuddy on GitHub Sponsors — or thinking about it — the new sponsors portal is live:

https://sponsors.bambuddy.cool

What it does:

• Sign in with the GitHub account you sponsor with — your tier shows up automatically
• Monthly sponsors newsletter (the same one that used to land as a pinned Issue in the private sponsors repo)
• Quarterly roadmap vote for Patron tier and above
• Email notifications when a new newsletter publishes or a vote opens

What changes for existing sponsors:

• The Discord "Backer / Supporter / Patron / ..." roles are gone. Discord stays exactly as it is for community use, just without the sponsor-tier channels.
• The private bambuddy-sponsors repo will be archived once the migration settles — newsletter + voting now live on the portal.
• BACKERS.md on the main repo still lists everyone (Backer and above).

Backer tier is intentionally off-portal — the perk stays the BACKERS.md listing, no portal sign-in needed.

What didn't change:

• All the actual tier perks. Supporter still gets newsletter, Patron still gets voting, Sustaining still gets the README listing and direct email line, Corporate still gets priority response and logo placement. Just delivered through a more reliable channel.
• Discord remains the general community hangout.

If you sponsor and your name isn't showing on the portal within an hour, email martin@bambuddy.cool or open an Issue on the main repo.

— Martin

Need to look at it more detailed. Please open an issue on Github. Thanks.

Please open an issue on Github and attach a support-package.

https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

Just in.....

Hey everyone,

The Bambuddy Sponsors program is now fully live with five recurring tiers. If you've been waiting for a way to back the project that's more than a one-off tip, here it is.

The tiers — what you get:

Backer — $5/mo

Your name in BACKERS.md. The warm feeling of keeping a local-first project alive.

Supporter — $15/mo

Everything in Backer, plus:

• Access to a private sponsors space
• Monthly sponsor newsletter
• Early release notes before public announcement

️ Patron — $35/mo

Everything in Supporter, plus:

• A vote on the quarterly roadmap
• First Patron vote opens June 2026 on Q3 features

Sustaining Sponsor — $150/mo

Everything in Patron, plus:

• Direct async email line to me for technical questions - ~2-3 business day response

Corporate — $500/mo

Everything in Sustaining Sponsor, plus:

• Priority email response (next business day)
• Your logo in the README header
• Your logo in the sitewide footer on bambuddy.cool
• Placement on the Press page

Sign up: https://github.com/sponsors/maziggy
One-time tip instead: https://ko-fi.com/maziggy

Why this exists

Bambuddy is principled local-first software. No cloud, no telemetry, no upsells, no enterprise SKU hiding behind the OSS edition. Igor's Lab framed it as "a principled alternative to Bambu Cloud" and I want to keep that promise. Sponsors are how that stays true — every dollar goes into shipping the next release, not into building a paywall around the current one.

If you're running Bambuddy in production (especially with multiple printers, an LDAP setup, or in a workshop / makerspace) and it's saving you time, the Sustaining Sponsor or Corporate tier is what underwrites the support response time and roadmap influence you'd otherwise have to negotiate as a contract.

What I won't do

• No hosted SaaS tier. The project stays self-hostable forever.
• No feature gated behind a sponsor tier. Everything that's in OSS Bambuddy today stays in OSS Bambuddy.
• No vendor lock-in. AGPL-3.0, your data on your hardware.

Questions, feedback, or "I'd sponsor if X were a perk"? Reply in this thread.

Thanks to everyone who's already on board.

— Martin

Your docker-compose.yml is truncated!

rm slicer-api/docker-compose.yml
wget -O slicer-api/docker-compose.yml https://raw.githubusercontent.com/maziggy/bambuddy/main/slicer-api/docker-compose.yml
docker compose up -d

Hey — fair question, happy to share.

Quick organizational note up front: maziggy and martinnyhc-1 are the same person. That's me, Martin. So there's no team behind Bambuddy in any traditional sense — just one person who got annoyed enough to keep going.

Background: I'm not a 3D-printing veteran by any stretch. My background is 30+ years service-provider networking. I came at Bambuddy purely as a user who wanted his printers to work without depending on a vendor cloud.

Why I started it — two reasons that kept compounding:

The first is the obvious one. I didn't want a cloud. Not a workaround, not "Bambuddy is fine alongside the Bambu app" — I wanted a complete replacement that covers everything the cloud does, so the printer can sit purely on the LAN and nothing is missing from the user's perspective. Most LAN-only tools handle one slice (just sending prints, or just monitoring); I wanted the whole stack: queue, dispatch, FTP, MQTT, camera passthrough, AMS, Spoolman, slicer integration, MakerWorld. If a feature only half-works in LAN mode, the project isn't done.

The second is more frustration than vision. Bambu Lab is noticeably slow to act on what users actually ask for. A lot of what's in Bambuddy started as a request that sat somewhere — in a forum, on GitHub, on Bambu's own feedback channels — for months or longer. At some point I figured if I wanted these things to exist, I'd have to build them. Turns out a lot of other people wanted the same things.

Print farm: nope. Three printers total — one H2D and two X1Cs. The funniest part of the whole thing: since I started working on Bambuddy, I basically don't print anymore. No time. The dev tree runs more cycles than my actual production prints do.

How it fits into daily life: right now Bambuddy is my main focus, full-time. I have the runway to do that for the moment, and the project needs that kind of attention to stay where it is and keep moving. To make it sustainable beyond just my own bandwidth, there are sponsor tiers on GitHub Sponsors and at https://bambuddy.cool/sponsors.html — five tiers from $5 to $500/mo. The headline perk on the Patron tier is a quarterly roadmap vote, with the first one opening this June. None of it monetizes Bambuddy itself — it stays AGPL, self-hosted, free for everyone. The funding just pays for the dev time.

Thanks for the kind words — honestly the best part of this is the response from people running it. Bambuddy gets better every week mostly because the user community actually digs in and reports things in detail. Couldn't do it without that.

Martin

Just open a feature request.

Just do

sudo systemctl enable --now docker.service && sudo systemctl status docker.service

You are checking the wrong service.

systemctl status docker.s
docker.service docker.socket

doocker.service is the right one.

Mhhh...never saw that before. Restart Docker and check your logs for errors.

@Schumbi Just open a feature request.

Use Bambu Studio ^^

Yes, sure.