Your K2 Plus fleet, run as a farm
K2 Plus machines — and anything else running Klipper and Moonraker — on one dashboard: live status, the camera, chamber temperatures, CFS spools, a queue that sends each job to the first free printer with the right filament and waits for you to clear the bed. Orders in from your shop, delivery notes out. Built on a shop that runs three of them every day.
Printer Farm with K2 Plus and any Klipper / Moonraker printer
Found and connected with nothing to configure
A stock K2 Plus needs no API key: the agent finds it on your network, the farm talks Moonraker on port 7125, the camera is picked up through the K2 bridge.
The queue, the pool and the bed-clear gate
Queue to the pool and the first free K2 with the right filament loaded takes the job; a file sliced for a 0.6 nozzle waits for a printer with one. Nothing starts on an occupied bed.
Klipper controls where you need them
A Fluidd-style move panel, your macros, the console, the light switch, chamber heating and CFS spool tracking that survives the printer's own counters being reset.
Maintenance that learns
The K2's own service items are mirrored with ✓ I did this logging an event, and the farm learns real intervals from your fleet — belt tension, lubrication, nozzle changes.
Three steps, and your Creality K2 Plus printers are on the dashboard
One small agent bridges your workshop to the cloud. Your files stay with you; the cloud is the dashboard.
Install the farm agent
A small program on a Windows or Linux computer that stays on, on the same network as the printers. One outbound connection, no router changes.
Scan for printers
The agent scans the network and lists each Moonraker printer by hostname; pick a K2 Plus and the address is filled in. A stock K2 needs no key — root access is not required.
Add the rest of the fleet the same way
Any Klipper printer (Qidi, Voron, Sovol, a Pi on a bedslinger) is the same type; Moonraker's optional API key goes in one field if yours asks for one.
Honest notes for Creality K2 Plus owners
- A revision sliced for Klipper can be queued onto any G-code printer in the fleet, but a K2 Plus file is not a Qidi file: the pool matches the sliced-for model and the nozzle, and says why when it can't.
- Chamber heating, the CFS and the K2's maintenance counters are all handled; the belt-tension and input-shaper routines can be scheduled to run when a printer is idle with a clear bed.
Runs alongside
Common questions
Do I need root on the K2 Plus?
Which other Klipper printers work?
Does it track CFS spools?
Run the whole job from one system
Free 14-day Workshop trial, no card. From £8 a month after, by fleet size.
Everything Printer Farm does, end to end →