Manyfold Hosting
Organize your 3D-printable model collection with tags, collections, and previews -- a self-hosted library for makers.
- One click deploy
- 1 GB RAM Memory needed
- 15 GB Disk Space Needed
- From 2 € Price
Official links
Manyfold’s official links and original website
Manyfold Website
More
Tech
- Docker image
- manyfold3d/manyfold:latest
- Default port
- 3214
How Manyfold works
Manyfold scans one or more libraries of 3D model files, builds records for the discovered content, and produces visual previews that make folders easier to browse. Users can add tags, creators, collections, and relationships, then organise models without relying only on filenames and directory depth. Maintenance checks identify selected problems in library structure or model records.
The catalogue stack runs Manyfold with SQLite for application records and Redis as a supporting service. Multiuser mode and registration are enabled initially, and the first registered user becomes the administrator. That makes prompt setup important: the intended owner should claim the installation, create approved accounts, and disable public registration when open signup is no longer required.
Key Manyfold features
Rendered and interactive previews help users recognise a model before downloading or printing it. Tags, creators, collections, and relationships describe content from several angles, while library scanning discovers files already stored in configured folders. Folder-management tools can reorganise content, and problem detection helps identify missing or inconsistent metadata.
Manyfold also supports private and public sharing choices, multiple users, and supported identity options. Those capabilities do not establish ownership or redistribution rights for uploaded models. Operators remain responsible for licences, privacy, access control, and the legality of files placed in the library.
Who uses Manyfold
Individual makers can index personal STL and related model collections, workshops can share approved files among members, and small design teams can preserve relationships between parts or variants. It is especially useful when a folder tree has become too large to understand from filenames alone.
The application is not a slicer, print queue, marketplace, or rights-management system. Printing still requires suitable software and hardware, and sharing a model remains subject to its licence and any restrictions imposed by the creator.
Self-hosting Manyfold: requirements and cost
Manyfold resource use depends on file count, model size, preview generation, scans, tags, users, searches, and library maintenance work. SQLite stores application records in the configured data volume, Redis supports the running service, and model files live in the library storage. The mapping does not mark Manyfold for the standard storage step-up, but large archives should still monitor disk consumption closely.
AvaHost maps Manyfold to Plan 1 at €2. Manyfold includes one-click deployment, automated HTTPS for a custom hostname, application updates, and scheduled backups. The first user becomes administrator and registration begins enabled, so claim the service promptly and close signup after creating intended accounts. Application email is disabled, and the hosting plan does not include 3D models, slicing software, printers, or marketplace content.
F.A.Q
Manyfold starts at €2 on Plan 1. File count, model size, preview rendering, scans, users, searches, and maintenance work influence resource use. The plan hosts the catalogue service and its persistent data, but it does not include model content, slicing software, printer control, marketplace access, or rights to redistribute uploaded files.
The catalogue configuration stores Manyfold records in SQLite and packages Redis as a supporting service. A separate PostgreSQL or MariaDB container is not required, so the relational-database plan adjustment does not apply. Model files live in the configured library volume; protect that storage, the SQLite data, Redis state, and application configuration together.
A custom hostname can serve Manyfold with automated HTTPS after DNS points to AvaHost. Choose the final address before sharing public model pages, configuring identity providers, or distributing bookmarks. After a domain change, verify sign-in, previews, downloads, public links, API calls, and any federated or external reference that may retain the former URL.
The first registered user becomes administrator, and registration is enabled in the catalogue configuration. Claim the installation promptly, create only the intended accounts, then disable open signup when it is no longer needed. Application email is disabled, so mail-based invitations and recovery are unavailable. Review library permissions and model-sharing rights before exposing content publicly.