maziggy/bambuddy
Your Bambu Lab. No Cloud. Your Rules. Self-hosted command center for Bambu Lab — from one A1 to an entire print farm. observed · 2026-08-28
Health v2 · maintenance only
78/100
- Activity 99
- Release rhythm 86
- Longevity 19
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 3
- age_days: 278
- days_rel: 18
- days_push: 7
- n_releases_24m: 66
Adoption not part of the score
2856 stars · 381 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Bambuddy is a self-hosted web application that acts as a command center for Bambu Lab 3D printers, from a single printer to an entire print farm. It provides real-time fleet monitoring, automatic print archiving, job queueing, server-side slicing via a headless OrcaSlicer/Bambu Studio sidecar, filament inventory tracking, and cloud-free remote printing through a virtual printer proxy.
Use cases
- manage a Bambu Lab print farm without the vendor cloud
- monitor multiple 3D printers in real time from a self-hosted dashboard
- queue print jobs across a fleet of printers
- archive every print with 3MF files, previews, and cost tracking
- slice STL and 3MF files server-side without a desktop slicer
- track filament spool inventory and remaining weight
- print remotely without Bambu Cloud, port forwarding, or a VPN
- analyze print costs, energy usage, and failure rates
When to choose
- you own one or more Bambu Lab printers and want to avoid Bambu Cloud entirely
- you run a print farm and need queueing, archiving, and cost analytics in one place
- you want everything local on your own hardware (Docker, Pi, NAS, mini-PC, or Windows)
- you need remote printing without port forwarding, optionally via Tailscale
- you want integrated slicing and filament/AMS management
When to avoid
- you use non-Bambu printers exclusively, since it targets Bambu Lab hardware
- you want a fully managed cloud service rather than self-hosting
- you need a slicer itself rather than a management layer (it wraps OrcaSlicer/Bambu Studio)
- you are unwilling to run a server, Docker, or a Windows service
Facets
application · maturity active
monitoring self-hosted http-server scheduling analytics file-upload developer-tools self-hosted analytics hardware web-development windows self-hosted python 3d-printing bambu-lab print-farm mqtt filament-management slicing orcaslicer no-cloud printer-fleet-management nfc automation docker linux macos
6 sources
- readme: https://github.com/maziggy/bambuddy · fetched 2026-08-28 · f26388898aed
- homepage: http://bambuddy.cool/ · fetched 2026-08-29 · 4f8af8b64e62
- site_page: https://bambuddy.cool/features.html · fetched 2026-08-29 · ae00d3540910
- site_page: https://bambuddy.cool/installation.html · fetched 2026-08-29 · b15d3b8db370
- site_page: http://wiki.bambuddy.cool · fetched 2026-08-29 · 1146d27c621a
- site_page: https://bambuddy.cool/spoolbuddy.html · fetched 2026-08-29 · 38bc25262cf6
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| maziggy/bambuddy | main | 78 |
For agents
markdown · JSON · MCP: product_card(name="maziggy/bambuddy")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem