Prusa Research has released a version of Prusa Connect that you run yourself. The company tagged Prusa Connect 0.1.0-beta.1 on GitHub on 17 November as a pre-release, and the release notes describe it in one line: "Prusa Connect is a server you run on your own network. Your printers connect to it, and you use them from its web app and its API. Nothing goes through a cloud service." Until now, Prusa Connect was the company's hosted fleet-management service. It now ships as a single binary that runs on a home server, a workshop PC or a Raspberry Pi.

The timing is pointed. Hackaday's Jenny List covered the release the next day and presented it as a response to the heavier reliance on the cloud found in printers such as Bambu Lab's. It also suits shops that print commercially sensitive parts and don't want job files leaving the building.

What you actually download

According to the project README, Prusa Connect is one Go binary with the web app built in. Accounts, printers, print history and files all stay on the machine that runs it. The repository was created on 17 November, the same day as the release, and GitHub lists its language as Go.

The build matrix is wide. Linux builds cover amd64, aarch64, armv7 and armhf, and the armhf build targets the Raspberry Pi Zero, Zero W and Pi 1. There are Windows builds for amd64 and arm64, and macOS builds for both Intel and Apple Silicon. Each full build includes:

  • the web app and HTTP API
  • a live event stream
  • MQTT support
  • SQLite and PostgreSQL storage backends
  • Prometheus metrics

MQTT, metrics and PostgreSQL are off by default and have to be enabled. Prusa also publishes prusa_connect_minimal_* builds for Linux. These include only the API and the printer connection, with no web app, which suits anyone who wants to put their own front end or automation on top.

Features: more than a remote start button

The README describes a fairly complete tool for a 0.1 release. A fleet dashboard shows every connected machine. From the browser you can send G-code and start, pause, resume or stop jobs. Accounts can log in with a password or through OpenID Connect, and permissions can be set per person, so a makerspace could let members use one machine and not another.

For integration, there is a REST API, server-sent events, and event sinks that forward printer events to MQTT, AMQP, Kafka or webhooks. That list reads like it was written for print farms and small production shops already running message brokers. There is also an extension marketplace with an SDK. Prusa says its load test runs 400 simulated printers against one server.

Supported Prusa hardware out of the box:

  • CORE One, CORE One L, CORE One INDX and CORE One L INDX
  • MK4/MK4S and MK3.9/MK3.9S
  • MK3.5/MK3.5S
  • XL
  • MINI

A driver API lets other manufacturers' printers be added. Hackaday notes this is how non-Prusa machines would be supported. The README points to an example driver for Klipper printers that run Moonraker, and says a community driver already passes the same conformance suite as the Prusa one.

"No cloud," with two switches to flip

Purists should know that the server does reach out to the internet by default in two places: the extension marketplace and update checks. Both can be turned off in config.yaml with core.marketplace.enabled: false and core.upgrade.enabled: false. On a fully isolated network, set both before deployment.

Advertisement

The beta label also matters. The README warns that the 0.x pre-releases are a public beta, and that the configuration format, the API and the extension SDK may change between versions. Users are told to back up before updating. Anyone who scripts against the API now should expect to rewrite some of it.

What changed in beta.1

The first tagged release already has a changelog. Among the items:

  • The build moves to Go 1.26.11, which fixes GO-2026-6859 in the net/http package.
  • The camera beside a running print on a printer's Now tab now plays its live view only when you press play.
  • GET /api/v1/devices/{device_id}/files no longer waits for the printer. Previously that call could fail with 409 or 504 errors.
  • The fleet severity filter drops its "Needs hands" tier, and a paused printer now falls under "Needs attention".

The licence is not what you might assume

The source is public, but this is not an MIT or GPL project. GitHub's API reports the licence as "Other." The README badge lists the Open Community Licence v1.1 along with add-ons labelled Micro, NoSaaS and SWAtt. Hackaday describes the Open Community Licence as making everything available but restricting some users. Large enterprises, for example, have to buy a paid version.

The README summary is more specific. Non-commercial use is broadly free, and a business may run and modify the software for its own internal use up to one million euros of annual gross revenue, affiliates included. A business may not offer it to others as a service, and anything beyond that needs a separate business licence. The README also says the licence texts themselves are what count, so anyone planning commercial use should read them.

Advertisement

For hobbyists, small print farms and makerspaces, this is probably not a problem. For a large company hoping to drop in a free fleet manager, it is.

How it stacks up against OctoPrint and Obico

The obvious comparison is with OctoPrint plus a self-hosted Obico instance, which many makers use to get local control and AI-based failure detection without a vendor cloud. Hackaday's commenters raised this. One said local Prusa Connect has no AI failure detection and is much less mature than OctoPrint plus Obico. Others asked how camera support will work in practice.

These criticisms are fair, but they also show what Prusa is aiming for. Prusa Connect is built as one server for many printers, with accounts, permissions, message-bus integration and Prometheus metrics. Its closer competitors look like farm-management tools, not a single-printer host on a Pi.

What It Means for Makers

If you own recent Prusa hardware and have avoided Prusa Connect because it meant sending every job through someone else's servers, that reason is gone. The cost is running a server and accepting beta-quality software. The binary is small enough for a spare Raspberry Pi, and the minimal Linux builds suit anyone building their own tools.

Shops with more than a handful of machines look likely to get the most from it. Per-person permissions, OpenID Connect sign-in, MQTT/Kafka/webhook event sinks and a 400-printer load test are features aimed at print farms, school labs and makerspaces that want to keep jobs on their own network.

The caveats are real. The API and configuration may change during the 0.x series, the marketplace and update checks must be switched off for a truly offline setup, and the licence limits some commercial use. If you rely on AI failure detection, OctoPrint plus Obico is still the more complete option for now, according to Hackaday's commenters.

The broader point is that a major printer maker has shipped a cloud-free fleet server with a public API and a driver interface for other brands, while some makers lean harder on the cloud. That alone makes it worth a test install.

Sources