Questions you probably have

Yes. AGPL-3.0-licensed, self-hosted, no paid tier. The only thing you pay for is your own server (or run it on a Raspberry Pi).

Bambu Lab X1 (X1C, X1E), H2 (H2D, H2D Pro, H2C, H2S), P1 (P1P, P1S), P2 (P2S), A1 (A1, A1 mini), A2 (A2L) and X2 (X2D). Anything that exposes the standard Bambu MQTT and FTP endpoints with Developer Mode enabled.

No. The web UI runs on your local network. The Telegram bot reaches Telegram's API outbound - no inbound port required.

Not any more. BamDude forked from Bambuddy 2.2.2 and the two have diverged too far for a one-time import; start with an empty data directory and re-add your printers and spools.

Strictly local. BamDude talks to your printers over your LAN using Developer Mode. No cloud calls except optional Obico AI failure detection (opt-in).

Yes, two ways. SQLite is the default; set DATABASE_URL=embedded and BamDude runs a PostgreSQL 18 it ships with itself, or point DATABASE_URL at your own server. Switching imports your existing database automatically.

No. The Bell in the app holds a per-user inbox that fills whether or not any external channel is configured, so an alarm about hardware has somewhere to land from the first minute. External channels are for reaching you when you are not looking at the farm.

You configure per-chat notification settings, quiet hours, and event types. Defaults are conservative.