forked from maziggy/bambuddy
-
-
Notifications
You must be signed in to change notification settings - Fork 1
What is Printbuddy
Marko@VMHOMELAB edited this page Jun 13, 2026
·
1 revision
Printbuddy is a self-hosted 3D printer management and print-archive dashboard.
The goal is simple: one clean web interface for different printer ecosystems instead of one tool for Bambu, another for Klipper, and another for Prusa.
- Shows multiple printers in one dashboard.
- Tracks current printer state, temperatures, progress, and camera access where supported.
- Archives print jobs with useful metadata so old prints can be found again.
- Provides queue, review, and virtual-printer workflows for supported slicer handoff scenarios.
- Adds optional notifications, backups, metrics, filament/inventory integrations, and Home Assistant integration paths.
- Runs self-hosted, usually through Docker Compose.
- It is not a slicer replacement by itself.
- It is not a cloud-hosted service.
- It does not make every printer expose identical capabilities. Bambu, Moonraker/Klipper, PrusaLink, and Prusa Connect have different APIs and limitations.
Printbuddy uses printer providers. Each provider knows how to talk to a specific printer ecosystem:
-
bambufor Bambu Lab LAN/MQTT/FTP workflows. -
klipper,fluidd, andmainsailfor Moonraker-backed Klipper printers. -
prusalinkfor local PrusaLink HTTP API printers. -
prusaconnectfor Prusa Connect Mobile API support.
That boundary is important. It keeps Bambu-only functions, Moonraker functions, and Prusa functions from being mixed together incorrectly.
Printbuddy is under active development. For normal installs, use the stable Docker image:
docker.io/vmhomelabde/printbuddy:latest
For testing development work, use the dev branch/image only when you explicitly want development behavior.