maziggy/bambuddy

Your printers. No cloud. Your rules.
Self-hosted command center for Bambu Lab — from one A1 to an entire print farm.

_{Corporate sponsor}

_{Sustaining sponsor}

🎮 Try the Live Demo • Features • Screenshots • Quick Start • Documentation • Discord • Contributing

Spin up your own private Bambuddy in ~10 seconds — no install, no signup, 30-minute session.

"Bambuddy is the companion app that Bambu Lab should have built from day one." — Adam Conway, XDA-Developers

Two leading 3D-printing publications independently concluded that Bambuddy's feature set already exceeds Bambu's own cloud:

"The features seem to exceed those provided by Bambu Lab's own cloud." — Fabbaloo

"The list of functions seems so extensive that it even goes beyond what Bambu Lab offers in its own cloud." — 3Druck.com

📄 See all press coverage →

Decide who prints on which printer, and what gets printed at all.

• 🖨️ Printer access per group — Limit a group to single printers or to whole locations (a location covers every printer in it, including ones added later). Members see and control only those printers, everywhere: dashboard, cameras, queue, archives, statistics, maintenance and live updates. Manage it by group or by printer on the Printer access page; a printer card's Who has access shows it for one printer.
• 👀 Jobs that wait for review — Without the new Print Without Review permission, a user can still queue jobs, but each one waits with a Waiting for review badge until staff start it. Covers every way a job gets queued: the print dialog, the file manager, pipelines, API keys and the webhook.
• 🔑 Nothing changes until you want it to — Groups without printer limits keep every printer, existing groups keep the right to start jobs, and administrators always see everything. API keys, camera links and overlay tokens reach only the printers of whoever created them.

👉 Printer Access Guide → · Job Review →

For labs, makerspaces and departments that bill print time. Entirely optional, off by default.

• 🏷️ Cost centers — A team, a course, a customer or a grant to print against. Every user also gets a private one automatically.
• 📉 Budgets — An optional total or monthly limit per cost center. A queued print's cost is reserved while it waits, so ten queued jobs can't each pass a check only the last would fail.
• 📒 One ledger — Every charge, deposit, withdrawal and adjustment on the new Finance page. Costs are computed on the server, and a print that fails half way is charged only for the filament it actually used.

👉 Billing Guide →

An order knows how many of each plate you wanted, so a failed print still counts as owed.

• 🔢 A quantity per plate — Set how many runs of each plate you need; the new Batches tab on the Print Queue shows target, done, still owed and failed for every plate.
• 🔁 Queue what's still owed — After a failed run, Queue N remaining re-queues the missing prints with the same printer, AMS mapping and print options.
• 💰 Measured cost — Material plus energy from the runs that actually happened, per plate.

👉 Batch Orders Guide →

Print from anywhere in the world — Bambuddy's Proxy Mode acts as a secure relay between your slicer and printer:

• 🔒 End-to-end TLS encryption — FTP, file transfer, and camera are transparently proxied with the printer's real TLS certificate
• 🛡️ Optional Tailscale integration — per-VP toggle + Docker socket mount surface the host's Tailscale IP on the VP card, so you know which 100.x.x.x to paste into the slicer when you want a virtual printer reachable over your tailnet (setup). Bambuddy's self-signed CA import is still required on the slicer side: Bambu Studio / OrcaSlicer validate printer TLS against a bundled BBL CA (not the system trust store), and their Add Printer dialog is IP-only (no hostname to match an LE cert against), so a publicly-trusted cert can't help on either dimension. Tailscale's role is the private tunnel (reachability from anywhere, no port forwarding), not cert-import elimination.
• 🌍 No cloud dependency — Direct connection through your own Bambuddy server
• 🔑 Uses printer's access code — No additional credentials needed
• ⚡ Full-speed printing — Transparent TCP proxy, only MQTT is decrypted for IP rewriting

Perfect for remote print farms, traveling makers, or accessing your home printer from work.

👉 Setup Guide →

No desktop slicer required. Drop an STL or 3MF into Bambuddy's File Manager, hit Slice, and the result lands as a ready-to-print .gcode.3mf in the same folder — without ever opening Bambu Studio or Orca Slicer.

• 🍰 One-click slicing — Slice from any browser. The job runs server-side in a tiny sidecar container, progress streams back as a toast, and the sliced file appears in your library when it's done.
• 📱 Slice from your phone or tablet — Bambuddy's PWA + the server-side slicer means you can drop an STL in from mobile and queue a print without ever touching a desktop.
• 🎒 Your own profiles — Pick printer, process and filament presets from your imported profiles, Orca Cloud, Bambu Cloud or the slicer's standard set.
• 🎛️ Full print settings — Process settings opens the slicer's whole parameter tree (Simple / Advanced / Expert, with search) so you can change walls, infill, supports or speeds for one slice. Slice as designed keeps the settings the file's designer saved instead.
• 🧭 Auto-orient and auto-arrange — Let the slicer turn parts onto their best side and lay them out on the plate. Combine to 3MF in the File Manager puts several STLs, or copies of one, onto a single plate first.
• 🔄 Re-slice for a different printer in one click — Open any sliced archive in Bambuddy and re-slice it for any printer, including across the single-nozzle ↔ dual-nozzle (H2D / H2D Pro) boundary that BambuStudio's CLI would normally reject. Bambuddy detects the class change and auto-arranges objects laid out for the source bed (e.g. X1C 256×256) so they land safely on the target (e.g. H2D 350×320 with its per-nozzle dead zones).
• 🍱 Slice all plates at once — Multi-plate projects (parted statues, multi-part kits) get a "Slice all N plates" toggle in the Slice dialog. One click produces a single .gcode.3mf containing every plate's gcode, ready for the printer. The toast shows "Plate 2 of 5 — Generating G-code (47%)" as the loop runs.
• 🔁 Same dispatch as the rest of Bambuddy — The sliced output flows into the existing queue / plate-picker / AMS-mapping path, so all the regular conveniences (multi-printer dispatch, AMS routing, scheduled prints) just work.

Optional but recommended — drop the slicer-api/ Compose stack next to your Bambuddy install and the Slice button lights up everywhere.

👉 Slicer Integration Guide →

Stop re-picking the same printer + process + filament + bed-type combination every slice. Save a Slicer Pipeline once from the Slice dialog, then apply the whole bundle to any file with a single click — from File Manager, Archives, or MakerWorld imports.

• 🧩 One-click reuse — A pipeline captures the entire Slice modal selection (printer + process + per-AMS-slot filaments + bed type) and surfaces as Run with pipeline → <name> on every sliceable row.
• 🎯 Specific printer or printer class — Pin a pipeline to one printer, or to a class (e.g. any X1C) and let the queue scheduler pick the first available match. Identical-fleet farms get a single recipe instead of one-per-printer.
• 🪢 Multi-copy fanout — Slice once, dispatch up to N copies. With class targeting the copies fan out across the matching printers in parallel — Spread (fastest wall-clock), Single printer (minimise colour-change overhead), or First N (one to each).
• 📊 Runs dashboard — A new Pipelines tab on the Print Queue page lists every run with colour-coded status badges (queued / slicing / dispatching / in-progress / completed / partial-failure / failed / cancelled), per-copy detail on expand, filter dropdowns (Pipeline / Status / Target), and a Retry failed button that re-runs only the copies that didn't complete — successful copies are never re-printed.
• 🔒 Permission-gated — Three permissions (pipelines:read / pipelines:write / pipelines:run) let you split authoring the recipe from spending filament with it.

👉 Slicer Pipelines Guide →

• Own your data — All print history stored locally, no cloud dependency
• Works offline — Uses Developer Mode for direct printer control via local network
• Full automation — Schedule prints, auto power-off, get notified when done
• Multi-printer support — Manage your entire print farm from one interface

Plus: Configurable slicer (Bambu Studio / OrcaSlicer) • Customizable themes (style, background, accent) • Mobile responsive • Keyboard shortcuts • 15 languages (EN/DE/ES/FR/IT/JA/KO/NL/PT-BR/RU/SV/TR/UK/ZH-CN/ZH-TW) • Auto updates • Database backup/restore • System info dashboard

Spin up your own private Bambuddy with simulated printers and pre-loaded print history. Click around freely — it's your sandbox. ~10 seconds to spawn, 30-minute session, no signup.

Prefer a video walkthrough?

Click to watch the demo on YouTube

Refreshed printer card in 1.2.5b2 — tighter layout, popovers for all controls (temperature setpoints, fan speeds, jog), and a bottom-aligned power row. The screenshots below predate the refresh.

• Python 3.10+ (3.11/3.12 recommended)
• Bambu Lab printer with Developer Mode enabled (see below)
• "Store sent files on external storage" enabled in Bambu Studio/OrcaSlicer
• Same local network as printer

Self-contained .exe — no Python, Node, Docker, or Git required on the target machine. The installer bundles Python 3.13, the React frontend, ffmpeg, and registers Bambuddy as a Windows service.

Download the latest installer:

https://github.com/maziggy/bambuddy/releases/latest/download/bambuddy-windows-x64-setup.exe

Run it (one-time UAC prompt — admin install) → Bambuddy starts as a Windows service and the dashboard opens at http://localhost:8000 automatically. Data lives at C:\ProgramData\Bambuddy\, install at C:\Program Files\Bambuddy\. To update, just run a newer installer over the existing install — your database and archives are preserved.

SmartScreen warning: until our SignPath OSS code-signing approval lands, you'll see "Windows protected your PC" on first run. Click More info → Run anyway.

See the Windows Installer Guide for service management, logs, and troubleshooting.

Option A: Pre-built image (fastest)

mkdir bambuddy && cd bambuddy
curl -O https://raw.githubusercontent.com/maziggy/bambuddy/main/docker-compose.yml
docker compose up -d

Option B: Build from source

git clone https://github.com/maziggy/bambuddy.git
cd bambuddy
docker compose up -d --build

Open http://localhost:8000 in your browser.

Multi-architecture support: Pre-built images are available for linux/amd64 and linux/arm64 (Raspberry Pi 4/5).

macOS/Windows users: Docker Desktop doesn't support network_mode: host. Edit docker-compose.yml: comment out network_mode: host and uncomment the ports: section. Printer discovery won't work - add printers manually by IP.

Linux users: If you get "permission denied" errors, either prefix commands with sudo (e.g., sudo docker compose up -d) or add your user to the docker group.

# Pre-built image: just pull the latest
docker compose pull && docker compose up -d

# From source: rebuild after pulling changes
cd bambuddy && git pull && docker compose up -d --build

# Pull the current beta
docker pull ghcr.io/maziggy/bambuddy:0.2.2b1
# or from Docker Hub
docker pull maziggy/bambuddy:0.2.2b1

# View logs
docker compose logs -f

# Stop/Start
docker compose down
docker compose up -d

# Shell access
docker compose exec bambuddy /bin/bash

ports:
  - "3000:8000"  # Access on port 3000

server {
    listen 443 ssl http2;
    server_name bambuddy.yourdomain.com;

    ssl_certificate /path/to/cert.pem;
    ssl_certificate_key /path/to/key.pem;

    location / {
        proxy_pass http://localhost:8000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_read_timeout 86400;
    }
}

services:
  bambuddy:
    build: .
    network_mode: host

# Clone and setup
git clone https://github.com/maziggy/bambuddy.git
cd bambuddy
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt

# Run (--loop asyncio avoids a uvloop TLS bug that can truncate VP FTP uploads)
uvicorn backend.app.main:app --host 0.0.0.0 --port 8000 --loop asyncio

Open http://localhost:8000 and add your printer!

Need detailed instructions? See the Installation Guide

Windows PowerShell (run as Administrator — the installer self-elevates via UAC if not):

powershell -ExecutionPolicy Bypass -Command "iwr -useb https://raw.githubusercontent.com/maziggy/bambuddy/main/install/windows-installer.ps1 -OutFile windows-installer.ps1; .\windows-installer.ps1"

Installs Bambuddy natively on Windows using Git, Python, a virtual environment, separate data/log directories, and optional NSSM Windows Service registration. See the Windows Installer Guide for parameters and unattended-install options.

Developer Mode allows third-party software like Bambuddy to control your printer over the local network.

1. On printer: Settings → Network → LAN Only Mode → Enable
2. Enable Developer Mode (appears after LAN Only Mode is enabled)
3. Note the Access Code displayed
4. Find IP address in network settings
5. Find Serial Number in device info

Note: Developer Mode disables cloud features but provides full local control. Standard LAN Mode (without Developer Mode) only allows read-only monitoring.

In Bambu Studio or OrcaSlicer, enable "Store sent files on external storage" so that print files (3MF) are saved to the printer's SD card. Bambuddy needs these files to extract thumbnails and 3D model previews.

1. Open Bambu Studio or OrcaSlicer
2. Go to the Device tab for your printer
3. In Print Options, enable Store Sent Files on External Storage

Full documentation available at wiki.bambuddy.cool:

• Installation — All installation methods
• Getting Started — First printer setup
• Features — Detailed feature guides
• Troubleshooting — Common issues & solutions
• API Reference — REST API documentation

Contributions welcome! Ways to help:

1. 📝 Document — Improve the wiki and guides (urgently needed!)
2. Test — Report issues with your printer model
3. Translate — Add new languages
4. Code — Submit PRs for bugs or features
5. 🔒 Security review — (specifically wanted, see below)

Not sure where to start? Reach out on Discord or email martin@bambuddy.cool — I'll help you find something that fits.

I'm bringing on a contributor whose specific focus is keeping an eye on Bambuddy's security.

Concretely:

Track the dev branch and flag changes touching auth, permissions, token handling, or the CI security backstops. Async post-merge — no gating of in-flight PRs.

What matters more than formal qualifications: fail-closed thinking by default, comfortable reading the auth layer (FastAPI + SQLAlchemy on the backend, a small React surface), willing to push back on except Exception shapes in security-sensitive code.

No fixed time commitment. If you're interested — or know someone who fits — email martin@bambuddy.cool or DM on Discord.

See CONTRIBUTING.md for guidelines.

AGPL-3.0 License — see LICENSE for details.

• SpoolEase by yanshay — early inspiration for NFC-based spool tracking and AMS inventory concepts
• Bambu Lab for amazing printers
• The reverse engineering community for protocol documentation
• All testers and contributors

Bambuddy stays independent because real people support it directly. If Bambuddy makes your printers more useful, please consider:

• GitHub Sponsors — five recurring tiers from $5/mo (Backer) to $300/mo (Corporate). Supporter+ ($15/mo) get access to a private sponsors space with a monthly newsletter and early release notes. Patron+ ($35/mo) vote on the quarterly roadmap. Sustaining Sponsor+ ($150/mo) get a direct async email line for technical questions (~2-3 business days). Corporate ($300/mo) get priority email response (next business day), README header logo, sitewide footer logo on bambuddy.cool, and Press page placement.
• Ko-fi — one-time tip or recurring.

Sponsors get listed in BACKERS.md. Need commercial support (SLA, multi-printer consulting)? Email martin@bambuddy.cool.

Made with ❤️ for the 3D printing community

Join our Discord • Report Bug • Request Feature • Documentation