More about the devs
-
For a multitude of reasons, I'm interested in learning more about the devs, especially @maziggy and @martinnyhc-1 . It seems like you work on this project 24/7, which of course is so much appreciated. I don't know how you do it, but I know this is one of the best run open-source projects I have ever participated in.
Do you all run print farms and Bambuddy is a necessary component or how does it fit into your daily life? If you don't mind sharing some of your backstory. If it's posted somewhere else, I haven't found it yet. Thanks again for all you do! -
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
-
Does that answer your questions?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login