If you are not familiar with Botqueue here’s a brief description from the developer:

BotQueue is an online platform for distributing print jobs to multiple 3D printers for production. As the name suggests, it allows you to create a print queue which contains jobs. Your connected bots will grab jobs and produce them. As each job is competed, the operator is prompted to remove and verify the output. Upon successful completion, the bot will grab the next job and start producing it. This continues until the queue is empty. If a bot fails, it is taken offline for repairs.

Another huge benefit of BotQueue is online access to your bots. The main interface to control your machines is through the BotQueue website. This means you can access your bots from anywhere in the world. You could queue up a print while on the road, and come home to a finished object on your 3D printer. Future support is planned for webcams, so you will even be able to check up on the printing progress remotely.

The best part of all this? It’s 100% completely open source. Both the web server and client software are licensed under GPLv3. An instance of the BotQueue server is being hosted on, but you are free to run your own local server for private production, a public server for hosted printing, or whatever you want. The code is located at

BotQueue is designed for running machines as close to 100% capacity as possible. However, it would work just fine for everyday single-machine, sporadic use. It would also work well for putting development machines through life testing as it tracks failures, printing time, and general usage statistics.

I saw this mentioned on Hackaday recently and decided to give it a shot. I’m liking it! I wish it handled errors a bit better, but it’s rather straight forward. I’d like a way to stop a machine, control it’s X,Y and Z movement and recovery from things a bit better. You want to make sure your start and end gcode in Slic3r is somewhat set up for hands free operation. I’m going to end up running the Botqueue server locally on my desktop, but it’s working quite well.

I’m interested in seeing what other people have done with it!