Print farms
3D model library management for print farms
By Petros, who builds Meshory · Updated Sep 18, 2026 · 9 min read
A print farm runs on two systems that get confused for one. Farm management software operates the machines: queues, job routing, printer assignment, orders, G-code. A model library manager answers a different question entirely, which is what you own, where it is, and which of the six copies is the one you print. Farm software is largely silent on that second question, and the bigger the library the louder it gets. This page sets out which layer covers what, and is specific about where Meshory stops, because it is a library tool and not farm management software.
Disclosure: we make Meshory, which sits in the library layer only. It does not control printers, hold a queue, track orders or manage operators, and the section near the end lists what it does not do in plain terms before the one on what it does. Facts about other products come from their own sites, checked on September 18, 2026.
Two layers, and only one of them is about printers
PrintStash, a self-hosted farm tool and therefore not a neutral party either, puts the split well in its own August 2026 comparison: a file manager is "a library layer above the machine", and "the printer fixes which software controls the machine; it does not fix where your models, G-code revisions, and print history live". That is the distinction worth holding onto while you evaluate anything in this space.
| Job | Farm management software | Model library manager |
|---|---|---|
| Route jobs to printers | Yes | No |
| Queue and schedule production | Yes | No |
| Orders, SKUs and customers | Usually | No |
| G-code revisions and print history | Usually | No |
| Operator accounts and permissions | Usually | Rarely |
| Find a model across a 40,000-file archive | Rarely | Yes, this is the whole job |
| Detect the same part saved six times | No | Yes, by content and by geometry |
| Render a preview for every file on a NAS | No | Yes |
| Read inside unopened ZIP and RAR bundles | No | Yes |
Most farms end up running one of each, which is the right answer rather than a compromise. The mistake is expecting either one to cover the other half.
What farm management software covers
If printers, queues and orders are the problem, these are the tools, and none of them is Meshory.
| Tool | Shape | What it is for |
|---|---|---|
| Printago | Cloud, with a self-hosted option | Order intake, job routing and production queues across Bambu Lab, Creality, Prusa, Snapmaker, Elegoo and anything on Klipper or Moonraker. Nested folders for parts and SKUs, plus global search |
| PrintStash | Self-hosted, Docker, free and AGPL | Source models, G-code revisions, slicer settings, printer jobs and outcomes on one record. Aimed explicitly at small farms |
| SimplyPrint | Mainly cloud | Vendor-agnostic fleet management across a wide range of printer brands, with files and print history attached |
| AutoFarm3D (3DQue) | Cloud | Automated queues and AI failure detection, with bulk upload, folder sorting and file version control alongside |
| 3DPrinterOS | Cloud | Enterprise and education: centralised file storage, version control, user permissions and remote fleet control |
| Daedalus | Self-hosted, open source | Product and SKU catalogues, immutable design versions, 3MF parsing, material costs, orders and multi-printer control |
| Karmen | Self-hosted or cloud | Print-file repositories with remote printer oversight, scheduling and slicer integration |
The library problems farm software leaves alone
These get worse with scale, which is why they bite farms harder than hobbyists.
The same part, saved six times, under six names
A farm accumulates duplicates faster than anyone: re-downloads, a kit bought twice in different bundles, a part re-exported at a different scale, the same model converted from STL to 3MF for a different printer. Most tools that claim duplicate detection hash the file bytes, which catches a renamed copy and misses every one of those, because a re-export shares no bytes with its original. Matching the mesh itself is what closes that gap, and hash vs. geometry-aware detection works through exactly which copies each method finds.
A library you cannot see
Farm software shows you the files you have already pushed into it. It does not render a preview for the 40,000 models sitting on the NAS that nobody has touched since the Kickstarter arrived, and an operator who cannot see a model will re-download or re-buy it rather than dig. Thumbnails across the whole archive are the cheapest fix for that, and the one farm tools are least likely to include.
Bundles nobody ever extracted
Creator and Kickstarter drops arrive as ZIP, RAR and 7Z and sit unopened, which means their contents are invisible to search and to any duplicate check. Reading inside archives without extracting them is the difference between a library you can search and one where a meaningful share is a black box.
A mixed fleet means mixed project files
A farm running Bambu alongside Creality or Snapmaker ends up with slicer projects that only open in the slicer that made them. Meshory's 3MF converter, in beta under Tools, moves a Bambu Studio, OrcaSlicer, Snapmaker Orca or Creality Print project to one of the others as a new 3MF, with plates and painted colours carried across and the original left untouched. Print settings you changed come across from the release after 1.9.0, so on the current release they do not.
What Meshory does not do for a farm
Taking this first, because it is shorter to check and it decides whether the rest of this page applies to you.
- No printer control: it does not connect to printers, dispatch jobs, hold a production queue or monitor anything. A queue is on the roadmap, framed around a market or gift run rather than production, and it has not shipped.
- No orders, SKUs or customers: there is no product catalogue and no link between a model and a thing you sell.
- No G-code tracking: it does not version G-code, store known-good G-code against a model revision and profile, or parse slicer settings back out of a sliced file.
- No print history: successes, failures, reprints and material consumed are not recorded. Filament can be assigned to a model, and spool and printer tracking are on the roadmap rather than shipped.
- No accounts, permissions or audit trail: it is a single-user desktop app. Several people can each run it against the same NAS share, but there is no shared state between them, no roles and no record of who changed what.
If any of those is the problem you are trying to solve, the table above is where to look, and PrintStash or Daedalus are the obvious starting points for a self-hosted farm.
What Meshory does do for a farm
One job, at the scale a farm actually has. It indexes folders in place on macOS, Windows and Linux, including NAS and network shares, and moves nothing.
- Every model visible: automatic thumbnails for STL, 3MF, OBJ, FBX, STEP and Rhino 3DM, and a real 3D viewer including multi-plate Bambu projects.
- Duplicates found three ways: file content, mesh geometry and whole folders, so a re-export or a format conversion still groups with its original, and a folder holding the same set of models collapses into one finding.
- Archives read in place: zIP, RAR, 7Z and TAR/TGZ browsed like folders, with every model inside getting a thumbnail and counting toward duplicate detection.
- Search, tags and collections across the whole library, with optional AI tagging on your own OpenRouter key rather than ours.
- Straight into the slicer: 15+ installed slicers auto-detected, one click from the library, plus the 3MF converter for a mixed fleet.
- No seats to manage: a licence key and no account, and the documented position is no activation limits, so several workstations are not several purchases.
On scale, the honest number rather than an adjective: it was built and hardened against a 118,270-model, 3.5TB library on one NAS share before it shipped, and scanning a NAS folder covers how network sources are handled.
How the two layers fit together
- 1The library lives where it already lives, on the NAS or the shared drive. Nothing gets migrated into a new home.
- 2A library manager indexes it in place, renders previews, and clears the duplicates before anything downstream has to deal with them.
- 3An operator finds the model, converts the project if the target printer needs a different slicer, and opens it in the slicer.
- 4Farm software takes it from there: slice, queue, route to a printer, record the outcome against the order.
Deduplicating first is worth doing in that order. Every duplicate you carry into a production system becomes a duplicate SKU, a duplicate job or an operator printing the wrong revision.
Print farm library questions
Is Meshory print farm management software?
No. It is a model library manager: it indexes, previews, searches and deduplicates the files a farm owns. It does not control printers, hold a queue, track orders or manage operators. Farms generally run a library tool and a farm management tool side by side, and PrintStash, Printago and Daedalus are the ones to look at for the production half.
Can several operators use it against the same NAS library?
Each can run Meshory on their own machine pointed at the same share, and the documented licence position is no activation limits and no seats to manage. What you do not get is shared state: tags, collections and notes made on one machine stay on that machine, and there are no accounts, roles or audit trail. For a team that needs one shared library with permissions, a self-hosted server like Manyfold or PrintStash is the better shape.
Does it track print jobs, filament or costs?
Filament can be assigned to a model from a filament library of brand, material and colour. Print jobs, success and failure records, material consumed and costs are not tracked, and spool and printer tracking sit on the roadmap rather than in the product.
What does it do about duplicates at farm scale?
It matches on three levels: an exact content hash for renamed copies, a mesh geometry fingerprint so a re-export or a format conversion still groups with the original, and whole-folder matching so a folder holding the same set of models collapses into one finding. Detection reaches inside archives and across NAS mounts, and nothing is deleted for you.
Can it convert projects between slicers for a mixed fleet?
In beta, yes, between Bambu Studio, OrcaSlicer, Snapmaker Orca and Creality Print. Plates and painted colours carry across into a new 3MF and the original file is never touched. The print settings you changed come across from the release after 1.9.0, which means not on the current release.
The library half, measured on your own share.
Point Meshory at the NAS, let it render, and look at the duplicate count before you decide anything. It is the one number that tells you whether the library layer is worth solving separately.