NAS & self-hosting
Do you need a Docker or NAS server to organize your 3D print library?
By Petros, who builds Meshory · Updated Aug 27, 2026 · 9 min read
No, you don't need a server. Most search results for organizing a 3D print library on a NAS point at self-hosted web apps: Manyfold, PrintStash, GyroidVault, each a Docker container you run on the NAS itself. Self-hosting solves problems a desktop app can't, and the sections below say which ones. But it is one pattern, not the price of admission. The other pattern keeps the NAS as plain storage and puts the library brains in a desktop app that scans the share in place: no containers, no database, no ports, nothing to administer. Here is what each buys you, what each costs, and how to tell which one your library needs.
The question usually arrives at a specific moment: the model collection has outgrown one computer, a NAS is already humming in a closet, and every article about organizing it opens with a docker-compose file. Before copying that file, work out what the server is for, because for a lot of libraries it solves a problem the owner doesn't have.
What a self-hosted library server is
The tools that dominate this search are web applications you install on your own hardware. Manyfold is the best known: an open-source (AGPL) Rails app distributed as a Docker container, with tags, collections, an interactive viewer, multi-user permissions, and Fediverse federation so libraries can follow each other across instances. PrintStash is a self-hosted vault built around G-code revisions and Klipper integration. GyroidVault adds model versioning and print logs. Different emphases, same shape: the application runs on your NAS or home server, works against the model files stored there, and you use the library through a browser.
The appeal is concrete. The NAS is already on around the clock, so the library is reachable whenever you are. Anything with a browser can open it, phones and tablets included. Several people can share one library, each with their own account and permissions. If you want to publish your collection, Manyfold can even federate it. No desktop app matches any of that. The question is whether you need it, because it comes bundled with a second job.
What running a server costs you
A self-hosted library is a service, and a service needs an administrator: you. For a typical Manyfold install, the job looks like this:
- The stack: Manyfold's Solo edition is one all-in-one container; the Standard edition expects PostgreSQL or MySQL plus Redis running alongside it. Either way you're writing and maintaining a compose file on the NAS.
- The network: the app listens on a port. Reaching it comfortably means a hostname, maybe a reverse proxy, and a decision about whether it's ever exposed beyond your LAN.
- The updates: Manyfold is pre-1.0 and moves quickly, which is good news that arrives as a stream of releases you apply, read changelogs for, and occasionally roll back.
- The backups: your tags, collections and user accounts now live in the app's database, separate from the models. That database joins the backup rotation, because losing it means redoing the organizing work.
None of this is hard for someone who already runs a homelab. For them it's an evening to set up and a routine to maintain, and our comparison with Manyfold is straight about that: if docker-compose and volumes are familiar words, the wall isn't a wall. But the maintenance never ends, and for everyone who wanted an organized library rather than a new service to operate, the whole second job is optional.
A NAS that already runs Docker for other services tilts the math: one more container is a small marginal cost, and self-hosting gets proportionally more attractive. The setup this guide argues against is standing up Docker for the first time just to browse your own models.
The no-server pattern: NAS as storage, desktop as brains
The alternative splits the roles. The NAS does what a NAS is good at: holding files, redundantly, always on. Every computer mounts the share the normal way, over SMB or NFS, so it shows up as a folder. And the library intelligence (indexing, thumbnails, search, duplicate detection) lives in a desktop app on each computer, pointed at the mount. No software runs on the NAS at all.
Meshory is built for exactly this pattern. A NAS mount is a first-class source next to local folders: add it once and it's indexed, browsable and duplicate-scanned in place, with nothing moved, renamed or uploaded. Network sources are treated with care by design. The file watcher that runs on local folders doesn't hold up well over SMB, so mounts are refreshed on a short cycle instead, and again whenever the app window regains focus. If the NAS goes offline, the app backs off gracefully and picks the source back up when it's reachable again. And duplicate fingerprinting on network folders runs at a gentler, NAS-friendly pace that only reads files whose size matches another file's, with a settings switch to keep it off the share entirely.
Scale is the usual worry with the desktop pattern, so here is the reference number: Meshory was hardened against a 3.5 TB library of 118,270 models held on a NAS, and indexing it takes about a minute and a half, plus roughly seven minutes to read inside its 7,500 archives. The step-by-step, from mounting the share to the first scan, is in scanning a NAS folder into your library.
Multi-computer setups need no extra work: one license covers every computer you own, with no activation limits, so the desktop and the laptop can both index the same share. And because the app is private by default, there are no accounts and nothing listening on your network. The library is exactly as exposed as the share itself, no more.
Side by side
| Self-hosted server (Manyfold et al.) | Desktop app + NAS mount (Meshory) | |
|---|---|---|
| Setup | Docker on the NAS; database and Redis for larger installs | Install an app, mount the share, add it as a source |
| Access | Any browser on the network, phones included | The computers the app is installed on |
| Multi-user | Yes: accounts, roles, per-model permissions | No: single-user by design |
| Maintenance | Updates, backups and networking are yours to run | App updates itself; nothing else to operate |
| Where the files live | On the server's storage | On the NAS, untouched, readable by anything else |
| Duplicate detection | Exact checksums (Manyfold); geometry matching is an open request | Content hash, geometry hash, and a near-duplicate review queue |
| Cost | Free (open source), plus your time | One-time purchase, every computer covered |
Which pattern fits your library
Choose the server if any of these describe you: several people need the same library with their own accounts; you want to browse from a phone or tablet; you want to publish or federate your collection; or you simply enjoy running services, in which case none of the costs above count as costs. Those are the cases where Manyfold and its peers win outright, and the full comparison hub walks through each tool's strengths without pretending otherwise.
Choose the desktop pattern if the library is yours (or yours and a partner's), lived in from computers rather than phones, and you want the organizing done this week rather than after a Docker detour. You get things the servers don't have, too: ZIP, RAR and 7Z bundles browsed in place without extracting, geometry-aware duplicate detection rather than exact checksums alone, and an app that works the same against local drives when you're away from the NAS.
It's also not a lifetime commitment either way. The share doesn't care what reads it: a container on the NAS and a desktop app on your PC can both index the same folders, so trying one pattern costs nothing but the setup time, and the folder structure from the complete organizing guide works identically under both.
NAS libraries without a server: common questions
Can I store STL files on a NAS without running a server?
Yes. A NAS share is just storage: mount it on your computer over SMB or NFS and it behaves like any folder. A desktop library app such as Meshory then indexes the mount in place, renders thumbnails, and finds duplicates without any software running on the NAS itself. Server apps like Manyfold are for sharing a library between people, not a requirement for organizing one.
Do I need Docker to organize 3D print files on a NAS?
No. Docker is how self-hosted library servers like Manyfold and PrintStash are distributed, so guides about them start with a compose file. If you skip the server pattern entirely and point a desktop app at the mounted share, Docker never enters the picture: the NAS holds the files and the app on your computer does the organizing.
Is Manyfold or a desktop app better for a NAS library?
It depends on who the library is for. Manyfold is better when several people need accounts on one shared library, when you want browser access from any device, or when you want to publish your collection. A desktop app is better when the library is personal, when you don't want to administer a service, or when you need things Manyfold lacks, like geometry-aware duplicate matching and browsing inside archives.
Does Meshory run on the NAS itself?
No. Meshory is a desktop app for macOS, Windows and Linux; it reads the NAS through a mounted share rather than running on the NAS hardware. If you specifically want an app that lives on the NAS and serves a web page, that's the self-hosted category: Manyfold, PrintStash and GyroidVault all work that way.
What happens when the NAS is offline?
With a desktop app, the library index lives on your computer, so search and browsing of already-indexed models keep working; Meshory backs off from the unreachable mount and picks the source back up automatically once it's reachable again. With a self-hosted server the situation inverts: the NAS going down takes the whole library interface with it.
Can several computers use the same NAS library?
Yes. Each computer mounts the same share and indexes it with its own copy of the app. Meshory's license explicitly allows this: one purchase covers every computer you own, with no activation limits. Tags and collections are kept per computer, so if you need one shared set of accounts and permissions across a household, that's the case where a multi-user server earns its keep.
The organized library, minus the server.
Point Meshory at your NAS mount and it indexes everything in place: thumbnails, search and duplicate detection with nothing to administer. One-time purchase, every computer covered.