prusa3d/prusa-connect
DevOps & Self-hostingSelf-hosted Go server that connects, monitors and controls a fleet of 3D printers over your own network.
What it is
Prusa Connect is a self-hosted server for managing a fleet of 3D printers. It ships as a single Go binary with the web app embedded, runs on Linux, Windows, macOS and Raspberry Pi, and keeps accounts, printers, print history and print files on the machine you run it on. There is no cloud dependency: printers talk to your server over your own network, and users sign in with local accounts or an OpenID Connect provider.
The server drives Prusa printers through a built-in driver and reaches other vendors through drivers that implement the sdk/connectorapi contract. A Klipper/Moonraker driver is included as an example (examples/adapters/moonraker), so non-Prusa hardware can join the same fleet view. A running server serves its API reference at /docs and an OpenAPI document at /openapi.json.
Quick start
The fastest way to try it without hardware is the demo, which builds the server, connects simulated printers, and prints the address and a sign-in account:
make demo
This requires Go and pnpm; see Build from source for prerequisites. Press Ctrl+C to stop everything.
For a real deployment, download the binary for your machine from Releases, make it executable on Linux/macOS, start it, and open http://<this computer>:8080/ to complete the setup wizard. The install-from-a-release guide explains which file to pick, how to verify it, and how to run it as a service. Docker users can instead run:
docker compose -f docker-compose.local.yml up -d prusa-connect
and open http://localhost:8080/; Container deployment covers ports, writable paths and health checks.
Connecting a printer
A Prusa printer finds the server through a configuration file on a USB drive. The Add a printer page generates the file with your server address, for example:
[service::connect]
hostname = 192.168.1.100
port = 8080
tls = false
Place it in the drive's top folder, insert the drive, then go to Settings → Network → Prusa Connect → Load Settings and choose Add Printer to Connect. The printer displays a code; confirm it on the Add a printer page and approve. The printer then receives its token during approval, so the file itself contains none. Custom certificates can encrypt the connection (certificates).
Constraints
- Public beta: releases are 0.x pre-releases, and configuration, API and extension SDK may change between releases. Back up data before updating.
- By default the server reads the extension marketplace and checks for updates online;
core.marketplace.enabled: falseandcore.upgrade.enabled: falseinconfig.yamldisable this. - Building from source needs Go 1.26.11 or newer, plus make with a POSIX shell (Git Bash on Windows); Node.js and pnpm are needed only for the web app and documentation.
- The licence is OCL v1.1 + Micro v1 + NoSaaS v1 + SWAtt v1: non-commercial use, modification and redistribution are permitted with attribution under the same terms; businesses may run and modify it internally up to €1M annual gross revenue, but may not offer it to third parties as a service. Larger businesses, hosting services and embedding it in commercial products need a separate business licence from Prusa.
HotRepo's take
The repository first appears in HotRepo's new-project list for Go on 2026-11-17, recording 100 stars and 6 forks within a growth window of roughly 12 hours. That is a single snapshot, so it supports no trend claim; what stands out instead is the scope: a vendor-made, self-hostable fleet server with REST, SSE and MQTT integrations, a driver SDK and a license that deliberately restricts third-party hosting. Anyone evaluating it should weigh the beta status and the NoSaaS terms alongside the deployment options.
Written by AI from the project's README, updated . The project's own docs are the source of truth.
You might also like
- rhfbgfgfdg999999/3d-printer-liveA local 3D printer streaming scene that turns Douyin, Kuaishou and TikTok comments, likes and gifts into printed viewer avatars.
- fleetdm/fleetA self-hostable control plane for MDM, patching, software deployment and compliance across fleets of laptops, servers and mobile devices.
- OrcaSlicer/OrcaSlicerOpen-source desktop slicer that turns 3D models into printer-specific G-code with calibration and support controls.
- TouchWorkStation/omarchy-serverTurns an Omarchy Arch machine into a browser-managed home server for self-hosted apps, files, VMs and remote desktop.
- traccar/traccarSelf-hosted GPS tracking server for fleets, assets or personal trackers, connecting 200+ device protocols to one dashboard and API.