Printbuddy
Docker app from ZappyZap's Repository
Printbuddy is a self-hosted command center for your 3D-printer fleet.
Overview
Readme
View on GitHub
One modern self-hosted dashboard for your 3D printer fleet.
Manage Bambu Lab, Klipper, and Prusa printers from one clean interface.
🌎 Website . 📚 Wiki · 📦 Latest release · 🚀 Demo . 💬 Discord Server
Demo login: admin / printbuddy
[!WARNING] This repository is still under active development
Printbuddy is not ready for public production use yet. Features may be incomplete, unstable, or subject to breaking changes without notice.
Use it for testing, development, and tinkering only.
You can check the current status of different features in the projects tab
What is Printbuddy?
Printbuddy is a modern, self-hosted dashboard with a broader goal:
A single, modern, self-hosted dashboard for managing different 3D printer ecosystems.
Printbuddy uses a provider-based architecture for multiple printer platforms.
Current state:
- Bambu Lab support from the original foundation ✅
- Prusa support via PrusaLink ✅ (Prusa Connect available, not tested)
- Klipper (open firmware) via Moonraker – Klipper, Mainsail and Fluidd ✅
- capability-based chamber, light and part-fan control (e.g. QIDI Q2)
- multi-tool toolheads shown as AMS-style tiles
- CFS display and control for K2-OpenHost (Kalico) printers
- OctoPrint (Marlin / RepRap printers) ⌛ (Implemented / In testing)
- Elegoo via SDCP (e.g. Centauri Carbon) ⌛ (Implemented / In testing)
- Provider architecture in place, further providers can be added ✅
Features
Printers
- Multi-printer dashboard for mixed fleets (Bambu Lab, Klipper/Moonraker, PrusaLink, OctoPrint, Elegoo SDCP)
- Printer discovery (Bambu SSDP, subnet scan for OctoPrint)
- Live status, temperatures, camera, manual controls and print control (start / pause / resume / cancel)
- File Manager per printer (list, upload, download, delete)
- Print archive with automatic start/finish detection for all providers
- Print queue, print farm monitor and farm command center
- Panda Breath support, smart plugs (Tasmota, REST, MQTT) and Home Assistant
Slicing & models
- Integrated slicer via optional Bambu Studio / OrcaSlicer sidecars – slice to
.gcode.3mfwithout a desktop slicer - 3D model viewer with wireframe and X-ray display modes, G-code viewer
- Model import page: import from MakerWorld and from a self-hosted GyroidVault library into the Printbuddy library (docs); finished prints can optionally be reported back to GyroidVault
Projects & filament
- Projects with a job plan: per-plate quantity, material and printer, running totals and one-click queueing
- Projects can be linked to a File Manager folder
- Filament inventory, Spoolman integration and maintenance tracking
Operations
- Notifications (incl. selectable source for progress milestones)
- Users, groups, MFA, OIDC / LDAP and API keys
- Backups (local and GitHub)
- Optional self-update from the UI via an updater sidecar that also updates itself and the slicer sidecars (docs)
- Self-hosted, Docker-based, modern web UI in multiple languages
Screenshots
Printbuddy Mascot / STL
Printbuddy also has its own little mascot.
Print your own Printbuddy
Download your Printbuddy here:
- MakerWorld:
https://makerworld.com/de/models/2894134-your-printbuddy#profileId-3234154 - Printables:
https://www.printables.com/model/1746692-your-printbuddy
Repository workflow
Development happens on the dev branch first.
- Commit and push work to
dev. - Test from
dev. - Merge approved changes into
main. - Release from
main.
dev -> active development
main -> stable releases
Docker quick start
For the first test deployment, build directly from the dev branch:
git clone -b dev https://github.com/vmhomelab/Printbuddy.git
cd Printbuddy
docker compose up -d --build
Optional sidecars
docker-compose.yml contains commented-out services you can enable:
bambu-studio-api/orca-slicer-api– integrated slicer, see Integrated slicerprintbuddy-updater– Update now button in the UI, see docs/self-update-sidecar.md. The updater needs Docker socket access, so only enable it if Printbuddy admins may manage containers on that host.
Integrated slicer
Printbuddy can slice models itself: pick printer, process and filament profiles in the Slice dialog and Printbuddy produces a printable .gcode.3mf. Slicing runs in an optional companion container:
| Sidecar | Port | Use it for |
|---|---|---|
bambu-studio-api |
3001 | Bambu Lab printers (required for newer models such as the X2D), AMD64 only |
orca-slicer-api |
3003 | Non-Bambu printers (Prusa, Voron, Creality, …) and older Bambu models, AMD64 + ARM64 |
Enable the sidecar in docker-compose.yml, then turn on Settings → Slicer → Use Slicer API. The connection test shows which slicer answers. The sidecar images use the latest tag and are kept in step with Printbuddy releases.
Full guide: docs/slicer-sidecar.md
Open Printbuddy in your browser:
http://<docker-host-ip>:8000
Linux host networking
On Linux, the compose file uses:
network_mode: host
This helps with Bambu discovery, camera access, and virtual-printer ports.
Docker Desktop
On Docker Desktop, remove:
network_mode: host
Then enable the commented ports: block in the compose file instead.
iPhone home-screen app
Optional: a small launcher opens Printbuddy full screen from the iPhone home screen and switches automatically between the local address on home Wi-Fi and a Tailscale address everywhere else. Setup: deploy/ios-launcher/README.md
Printer provider direction
Printbuddy introduces a provider boundary so printer-specific integrations can evolve without hard-coding every workflow to Bambu MQTT/FTP.
Planned providers:
| Provider | Description | Status |
|---|---|---|
bambu |
Existing Printbuddy / Bambu Lab MQTT + FTP support | Inherited ✅ |
klipper / mainsail / fluidd |
Moonraker-backed Klipper printer status and control (incl. chamber/light/fan capabilities, multi-tool, K2 CFS) | Implemented ✅ |
prusalink |
PrusaLink (local HTTP API) | Implemented ✅ |
prusaconnect |
Prusa Connect (cloud) | Implemented, not tested ⌛ |
pcl |
Prusa Connect Local (hosted server) | Implemented, in testing ⌛ |
elegoo_sdcp |
Elegoo SDCP (e.g. Centauri Carbon / CC1) | Implemented, in testing ⌛ |
octoprint |
OctoPrint REST API (Marlin / RepRap printers) | Implemented, in testing ⌛ |
Each printer stores its provider plus provider metadata; provider-specific clients are created through backend/app/services/printer_providers/factory.py.
Bambu remains the default provider for backwards compatibility.
Home Assistant
Printbuddy can be used with Home Assistant in two ways:
- Home Assistant add-on: run Printbuddy directly inside Home Assistant with Ingress, persistent add-on storage, and LAN printer access through host networking. Repository: vmhomelab/printbuddy-ha-addon
- Home Assistant custom integration: connect Home Assistant to an existing Printbuddy instance and expose configured printers as Home Assistant devices and telemetry entities. Repository: vmhomelab/ha-printbuddy-integration
Wiki pages:
Development setup
Backend
python3 -m venv venv
./venv/bin/pip install -r requirements.txt -r requirements-dev.txt
ruff check backend/
ruff format --check backend/
cd backend
../venv/bin/python -m pytest tests/ --tb=short
Frontend
cd frontend
npm ci
npm run lint
npx tsc --noEmit
npm run test:run
npm run build
Project status
Printbuddy is currently focused on:
- Cleaning up the project structure
- Adding provider metadata
- Preparing Klipper and Prusa support
- Keeping existing Bambu functionality working during the transition
Contributing
Contributions are welcome once the project structure becomes more stable.
For now, the best way to contribute is:
- Open an issue with your idea or bug report.
- Target pull requests against
dev. - Keep changes focused and easy to review.
- Test both backend and frontend before opening a pull request.
Attribution and license
Printbuddy keeps the upstream AGPL-3.0 license.
Historical upstream documentation and changelog entries are retained only where needed for license and release-history context.
Star History
Star History Chart
Printbuddy
Your tiny helper for keeping the printer chaos under control.
Categories
Download Statistics
Total Downloads Over Time
Related apps
Explore more like this
Explore allLinks
Details
vmhomelabde/printbuddy:latestRuntime arguments
- Web UI
http://[IP]:[Config:PORT]/- Network
host- Shell
sh- Privileged
- false
- Extra Params
--restart=unless-stopped --cap-add=NET_BIND_SERVICE
Template configuration
Set the operational time zone for print logs and scheduled tasks.
- Target
- TZ
- Default
- America/Toronto
- Value
- America/Toronto
The user ID for the container process. This should match the user ID of the Unraid user that owns the appdata folder.
- Default
- 99
- Value
- 99
The group ID for the container process. This should match the group ID of the Unraid user that owns the appdata folder.
- Default
- 100
- Value
- 100
The internal port Printbuddy uses for its web dashboard server. Since Network Mode is locked to 'host', changing this value directly alters the port used on your Unraid host (e.g. http://your-unraid-ip:8000).
- Target
- PORT
- Default
- 8000
- Value
- 8000
Persistent storage location for your SQLite database, custom settings, and print farm configurations.
- Target
- /app/data
- Default
- /mnt/user/appdata/printbuddy/data
- Value
- /mnt/user/appdata/printbuddy/data
Persistent storage folder where application runtime and printer connection logs are saved.
- Target
- /app/logs
- Default
- /mnt/user/appdata/printbuddy/logs
- Value
- /mnt/user/appdata/printbuddy/logs