ask the nozzle

Blog › Print Farm

Bambu Lab Print Farm Without Cloud: The Real Setup, Limits and Fixes

6 November 2026·10 min read·Print Farm

Detailed view of a 3D printer mechanism in a dark setting, highlighting technology.

Running a Bambu Lab print farm without cloud is entirely possible, but the mechanism changed significantly in 2025. There are now two distinct “no-cloud” paths and they are not the same thing: the standard LAN-only Mode toggle on each printer, and Bambu Farm Manager, which keeps your print data local but works by replacing Bambu’s cloud with a local server you run yourself. Get the two confused and your fleet won’t discover, or third-party software won’t be allowed to drive the machines. This guide sets out exactly how each works, what the Authorization Control System (ACS) and Developer Mode changed, how to get discovery working across VLANs, and how to update firmware with no internet in the loop.

What “no cloud” actually means on a Bambu Lab printer

LAN-only Mode disconnects the printer from Bambu Lab’s cloud so it only talks to devices on your local network. Print jobs and monitoring route directly over the LAN with no cloud relay: Bambu Studio communicates with the printer using an MQTT-based protocol, no print data passes through Bambu’s servers, and the camera feed is available locally. Bambu describes it as letting printers “work in a local area network, and communicate with the slicer for sending files and monitoring without requiring internet access.” It is available on all current models.

The trade-offs are predictable. In LAN-only Mode you lose cloud-only features: the Bambu Handy app, skip-objects, remote access from outside your network, and — depending on firmware — cloud timelapses and model history. For a farm that lives in one building, none of that is a real loss. The point is that the print pipeline no longer depends on an external service being up.

One caveat worth flagging: there are forum reports of specific app/firmware combinations where LAN-only Mode behaved oddly without any internet present. That conflicts with Bambu’s own description and most other evidence, so treat it as version-dependent rather than universal — test your exact firmware before you commit a production schedule to it.

The Authorization Control System (ACS) and Developer Mode

This is the single most important change for anyone running Bambu hardware with third-party or self-hosted software. In January 2025 Bambu announced the Authorization Control System; stable firmware followed in March 2025 on the X1 and June 2025 on the P1 and A1. Once ACS is in place, certain commands require authorised access in both cloud mode and normal LAN mode — with one exception.

That exception is Developer Mode, a per-printer toggle added alongside the ACS rollout. With LAN-only Mode enabled, Developer Mode is what actually lets local applications drive the printer — start prints, set temperatures, send movement commands. Without it, a printer in plain LAN mode will block third-party write actions. Developer Mode also will not allow the printer to connect to Bambu Cloud, so it is exclusively a local-network arrangement.

The alternative Bambu offers is Bambu Connect, a separate local connection middleware. It is not the same as LAN-only Mode, may not be supported on every model, and community testing suggests it can still route some traffic. If your goal is genuinely local printing, confirm you are selecting plain LAN and, where you need third-party control, Developer Mode — not Bambu Connect.

In short: for a self-hosted or third-party-driven Bambu farm, the working recipe is LAN-only Mode plus Developer Mode on each printer. That combination keeps data local and keeps the printer willing to take commands.

Bambu Farm Manager: official, cloud-free fleet control

After nearly a year in beta, Bambu launched its own local fleet tool — Bambu Farm Manager — with a soft launch on 2025-05-27 and a public announcement on 2025-07-03. It allows full fleet control without relying on cloud connectivity, and it is free at launch, with more advanced features planned at a future paid tier.

Architecturally it is two programs: a Server component that runs 24/7 in the background to keep communication with your printers alive, and a Client interface to manage print operations. From one dashboard you can queue files by printer availability, monitor real-time progress, send commands to groups of printers at once, organise folders/tags/filters, and set staggered start times to manage power load across the fleet. There is no hard printer-count limit — it scales with your PC and network capacity, and at least one early adopter runs roughly 35–45 machines on it.

Requirements and the gotchas that catch people out

ItemDetail
Operating systemWindows 10+ (64-bit) only. macOS client and Linux/Docker server listed as planned, not yet released — verify current status.
ComponentsServer (24/7 background) + Client interface, installed separately.
Version pairingClient and server must both be the same major version (3.0); 3.0 and 2.0 components cannot pair.
Wi-Fi band2.4 GHz only — most models don’t support 5 GHz. Server must share the LAN with the printers (or be reachable by IP across subnets).
DiscoverySupports IP range scanning to find printers auto-discovery misses.
Internet for setupStill needed for server activation, printer verification and firmware downloads. The activation certificate must be renewed every six months.

Now the subtle part. Farm Manager is “cloud-free” in that your print data stays local — but it works by making the printer treat your local server as its cloud, not by using the standard LAN-only toggle. In practice each printer is unbound from Bambu Handy, and LAN-only Mode is turned OFF so the printer will accept the Farm Manager connection. If you leave a printer in LAN-only Mode by itself, Farm Manager may not discover or adopt it. So do not conflate “Bambu Farm Manager” with “the LAN-only Mode toggle” — for Farm Manager, LAN-only is off and the local server takes over.

Because setup, activation and firmware still require internet, and because the certificate renews every six months, Farm Manager is best described as data-local rather than fully air-gapped. If your requirement is true zero-internet operation, that distinction matters.

Supported models

At launch Farm Manager covered the P1, A1 and X1 Carbon, with the X1E and H2 Dual following. Later documentation lists minimum firmware per model (for example the H2C, H2D and H2S around 01.02.00.00, the H2D Pro and X2D around 01.01.00.00). Model and firmware coverage is evolving fast — check the current Bambu wiki table before you plan a mixed fleet.

Networking a Bambu farm without cloud

Discovery is where most farm networking problems start. Despite some blogs stating otherwise, the strong technical evidence is that Bambu printers use a non-standard SSDP/UDP broadcast mechanism (ports 2021 and 1900), not mDNS. That broadcast does not cross VLANs or subnets, and mDNS reflectors do nothing for Bambu hardware. A working OPNsense setup confirms it: on a single flat network the printer sends SSDP-style UDP broadcasts that Studio picks up; put the printer on a separate VLAN and discovery silently fails. (Bambu’s own help article is reported to mention mDNS, so treat this as genuinely contested — but lean on SSDP when you’re troubleshooting.)

To make discovery work across VLANs, enable SSDP broadcast/multicast forwarding between the two networks at the router. Tools like udpbroadcastrelay on OPNsense, or a small Python SSDP bridge forwarding ports 2021/1900, do the job. Remember that this only fixes discovery — Bambu Studio still needs a normal unicast path to the printer’s IP for everything after that. One user also reports that Bambu’s published LAN-Mode port list looks incomplete: they printed fine without opening everything listed, but needed 2024/tcp, which isn’t on the list. Verify ports against the current wiki and your own packet captures rather than trusting any single list.

A sane farm networking baseline:

  • Assign each printer a static IP via DHCP reservation so job routing and camera URLs never move.
  • Put all printers on a dedicated VLAN, and forward SSDP across to your workstation VLAN for discovery.
  • Block internet access for the printer VLAN at the router — belt and braces, so that even if LAN-only Mode is toggled off, the hardware still can’t reach the internet.
  • Remember the security reality: anyone on the local network with the access code can connect to a printer. That matters in shared or coworking spaces.

Firmware updates with no internet in the loop

You can update firmware while a printer stays in LAN-only Mode, without re-enabling Cloud mode and without Bambu Handy — via an offline update from removable media. The X1/X1C/X1E, P1P/P1S and A1/A1 Mini use a microSD card; the H2 series uses USB.

There’s a chicken-and-egg catch: the printer must already be on a recent enough firmware for offline updates to exist. The P1 series gained offline support at v01.07.00.00 (so a P1S must be on 01.07.00.00 or newer), and the A1 series at v01.04.00.00. The process:

  1. Download the firmware file from bambulab.com.
  2. Copy it to the root of the SD card or USB stick — do not rename it and do not decompress it.
  3. Insert the media and go to Settings → Firmware → Update Offline, then select the version.

Downgrades work the same way: the downgrade package is pulled from Bambu’s CDN, copied to the card, and triggered from Settings → Firmware → Update from SD card. The printer will accept both newer and older packages by this route.

Where Printer Farm fits — mixed fleets and selling parts

Bambu Farm Manager is a solid, free way to queue and monitor Bambu-only machines locally. If your farm is Bambu-only and you just need queueing and monitoring, it’s a reasonable choice. But most working farms aren’t single-brand, and most farms that sell parts need more than a queue — they need orders, works orders, stock, true cost per part and despatch.

That’s the gap Printer Farm fills. It runs the whole job end to end across a mixed fleet — Bambu Lab in LAN mode, plus Creality and any Klipper/Moonraker printer, FlashForge, OctoPrint, PrusaLink and Duet. A web order comes in from WooCommerce, Shopify or your own custom website connected through the farm’s shop API; stock is used first and one click raises a works order for exactly the shortfall; the job is sliced (the real OrcaSlicer engine, in the browser or on your PC through ATN Slicer); the queue dispatches it to the first free compatible printer with the right filament loaded; cameras with AI failure alerts watch the print; good parts bank into stock with a real cost per part (mixed plates split by weight); and despatch raises a numbered delivery note. It keeps your data local too: a small agent runs on a Windows or Linux computer that stays on, your files stay on your own machine, and slicing runs on your PC through ATN Slicer (or on our servers on Workshop and above).

If you’re weighing up queue tooling specifically, our guide to running one backlog across a whole fleet goes deeper, and Etsy sellers should read turning orders into shipped parts without babysitting machines. You can start a free 14-day Workshop trial (no card) to try it on your own hardware.

FAQ

Can I run a Bambu Lab print farm with no internet at all?

Printing itself, yes — LAN-only Mode plus Developer Mode keeps print jobs, monitoring and the camera feed entirely on your local network. But setup is a different matter: Bambu Farm Manager still needs internet for server activation, printer verification and firmware downloads, and its activation certificate renews every six months. Firmware can be updated offline by SD/USB once the printer is on a recent enough version. So “data stays local” is achievable; “never touches the internet” is harder.

Does LAN-only Mode need to be on or off for Bambu Farm Manager?

Off. Farm Manager replaces Bambu’s cloud with your local server, and the printer must be able to accept that server connection — so LAN-only Mode is turned off and the printer is unbound from Handy. This is the opposite of what you’d do for third-party software, which needs LAN-only Mode plus Developer Mode on.

Why can’t Bambu Studio find my printers across VLANs?

Bambu uses an SSDP/UDP broadcast on ports 2021 and 1900 for discovery, and broadcasts don’t cross VLANs or subnets. Forward SSDP between the networks (for example with udpbroadcastrelay on OPNsense) and make sure there’s a unicast path to each printer’s IP afterwards. mDNS reflectors won’t help.

Will the Authorization Control System break my existing farm software?

It can. After ACS, printers block third-party write actions in both cloud and normal LAN mode. To let local or self-hosted software drive the machine you need Developer Mode enabled (in LAN-only Mode), or Bambu’s own Bambu Connect middleware. Check your firmware version against your software’s requirements before updating a production fleet.

Related: 3D Print Failure Diagnosis: Read the Symptom, Find the Real Cause

Related: 3D Print Farm Cost Per Part: The Formula, the Numbers and Where the Money Actually Goes

← All articlesMore in Print Farm →