Quick Answer: A Prusa Connect local server is a self-hosted Go binary that manages your 3D printers from a machine you control. Download the release for Linux, Windows, macOS or Raspberry Pi, start it, and open http://<this computer>:8080/ in a browser. Each printer finds the server through a small config file on a USB drive, and you approve it with a code. Your accounts, print history and files stay on that machine.

Keeping three printers in sync across three browser tabs gets old fast. Add a camera feed, a slicer queue and a spreadsheet of print history, and you're running a small operation with no real tooling. Prusa Connect takes a different route: one server you run yourself, with a dashboard for every printer and an API for everything else. This is practical self-hosted 3D printer management, so here's what the server does, how a printer joins it, and where it still reaches out to the internet.

What the server is, and what "local" really means

The server is a single Go binary with the web app built in. It runs on Linux, Windows, macOS and the Raspberry Pi, and it keeps accounts, printers, print history and print files on the machine it runs on. Nothing needs a vendor cloud to make the dashboard work.

Here's the part most guides skip. Local doesn't mean offline. By default the server reads the extension marketplace and checks for updates over the internet. The common assumption is that self-hosting removes every external dependency, but it only removes the cloud dependency for your printers. The update channel stays open unless you close it.

If you need a quiet box, set core.marketplace.enabled: false and core.upgrade.enabled: false in config.yaml. You give up automatic update checks and extension discovery in exchange for fewer outbound connections. So does Prusa Connect need internet access? For the printers and the dashboard, no. For updates and the marketplace, yes, unless you switch them off.

Connecting a printer without handing over a token

A Prusa printer finds the server through a file on a USB drive. The Add a printer page in the web app generates that file with your server's address already filled in. It holds a hostname, a port and a TLS flag, and nothing secret.

The printer gets its token only when you approve it, so a copied USB file doesn't expose a credential. That's a deliberate design choice, and it's a good one. Here's the sequence:

  1. Put the downloaded file in the top folder of a USB drive.
  2. Insert the drive into the printer.
  3. Open Settings, Network, Prusa Connect and choose Load Settings.
  4. Choose Add Printer to Connect. The printer shows a code.
  5. On the Add a printer page, match the code to the printer's display, then choose Approve.

Don't skip step five. If you approve without comparing codes, you're trusting whatever device sent the request. The hostname in that file is the only address the printer knows. If your router hands the server a new IP after a reboot, every printer goes quiet. Set a DHCP reservation for the server, or use a stable local hostname.

Install and run: three paths, one decision

You have three ways to start, and each suits a different setup:

  • Release binary: Download the file for your machine from the Releases page. On Linux and macOS, run chmod +x first. This suits a Raspberry Pi or a home server you'll run as a service.
  • Docker: Run docker compose -f docker-compose.local.yml up -d prusa-connect, then open http://localhost:8080/. Check the writable paths before you go live. If you recreate a container without those paths mounted, you lose the accounts and history stored there.
  • Demo from source: Run make demo. It builds the server, connects simulated printers and prints an address and a sign-in account. You need Go and pnpm. The source builds with Go 1.26.11 or newer.

Whichever path you pick, the setup wizard runs the first time you open the address. Answer its questions, then create your admin account before you add any printers.

If you have no hardware yet, the printer simulator speaks the same WebSocket protocol as the firmware. Run go run ./tools/printersim -url http://127.0.0.1:8080 -model MK4 -count 5 to connect five simulated printers. The project's own load test runs 400 simulated printers against one server, which gives you a sense of headroom. It's a test result, though, not a promise about your network.

Accounts, permissions and the integration surface

People can sign in with a password or through an OpenID Connect provider. Each person gets only the printers and actions you grant. Here's where it gets interesting: permissions work per printer and per action. Someone can watch a printer's temperatures without any right to start a job. That split matters on a shared farm, where the person checking progress shouldn't be the one who can send a file.

Other programs get the same data the web app shows. The REST API has its own reference at /docs, and the OpenAPI document sits at /openapi.json. Server-sent events stream live state to a browser or script. Event sinks push events to MQTT, AMQP, Kafka or webhooks.

Need a custom alert when a print fails? Subscribe to the events instead of polling the API every few seconds. Polling works, but it adds load and lags behind the event stream. Pin your version before you build on any of this. The API, the SSE format and the extension SDK can all change between 0.x releases.

Other makers, and the three ways to extend it

The server talks to a printer through a driver. The Prusa driver is built in, and anyone can write another. The SDK in sdk/connectorapi defines the contract, and the Prusa driver and a community driver pass the same conformance suite. The example in examples/adapters/moonraker is a driver for Klipper printers running Moonraker, so you can see a working Moonraker driver before you write your own. The make scaffold-driver command writes the first files.

Extending the server itself works in three ways:

Extension typeHow it runsGood forWatch out for
ModuleSeparate program the server starts and supervises; restarted on failureNew pages, API routes, its own recordsYou own its uptime and its data
BuiltinCompiled into the serverPrinter drivers, such as the Prusa driverAny change means a rebuild and a new release
ScriptExpression in the config file that turns an event into a messageSending an event to a web addressLogic lives in YAML, which is harder to test than Go

The rule of thumb: use a script for a single outbound notification, and a module when you need state or a UI. Reach for a builtin only if you're writing a driver you plan to ship.

Licence: self-hosting for yourself is not self-hosting for clients

The project is released under OCL v1.1 with the Micro, NoSaaS and SWAtt add-ons. For non-commercial use you can run, change and take the project apart. A business can run it for its own internal use, including production, up to one million euros of annual gross revenue, affiliates included.

Here's the trap. A print farm operator who hosts the dashboard for customers, or exposes its API to them, breaks the NoSaaS clause even though the server is "self-hosted" on the operator's own hardware. The licence cares who the service is offered to, not where the box sits. Anything beyond the internal-use limit, including a hosted service, needs a separate business licence. Write to sales@prusa3d.com for one. Read the LICENSE file itself, because it's the text that counts, not this summary.

Where it's still rough

The project is in public beta. The releases are 0.x pre-releases, and the configuration, the API and the extension SDK can change from one release to the next. Back up your data before every update, and keep a copy of config.yaml with it.

Fixed addresses and approval codes cover most setups. Custom certificates cover the rest, and the certificates guide in the docs folder explains how to use your own. Plan for the rough edges. You'll get more out of a beta you understand than one you're hoping will behave.

Frequently Asked Questions

what is a prusa connect local server?

A Prusa Connect local server is the self-hosted version of the project: one Go binary with the web app built in, which you run on your own Linux, Windows, macOS or Raspberry Pi machine. It stores accounts, printers, print history and files locally. Printers connect to it over your own network, so you control the data and the access.

how do i add a prusa printer to my own server?

Open the Add a printer page in the web app and download the generated file. Copy it to a USB drive, insert the drive into the printer, and choose Load Settings, then Add Printer to Connect. Match the code on the printer's screen to the one in the web app, then approve it.

does a prusa connect local server need the internet?

Printers and the dashboard work on your local network. The server does check the extension marketplace and look for updates over the internet by default. To stop those checks, set core.marketplace.enabled and core.upgrade.enabled to false in config.yaml.

can i use prusa connect with printers from other makers?

Yes. The server talks to each printer through a driver, and the SDK's connectorapi package defines the contract. The project includes a Moonraker example for Klipper printers, and make scaffold-driver creates the starter files for a new driver.

Start with the demo this week

A Prusa Connect local server is easiest to judge by running one. Run make demo on a spare machine, open the address it prints, and time how long the simulated fleet takes to appear. Then check which outbound connections the server makes, and decide whether the update checks suit your network. Pass this to someone wrestling with a shared print queue who needs a cleaner answer than a dozen browser tabs.