A self-hosted digital asset manager for 3d print files.
2.1k
Stars
126
Forks
496
Open issues
30
Contributors
AI Analysis
Manyfold is a self-hosted web application for organizing and managing collections of 3D models, with particular focus on 3D printing use cases. It serves makers, hobbyists, and professionals who need to catalog STL, OBJ, and other 3D print files locally without cloud dependency. Best suited for users comfortable running self-hosted services; not intended as a casual cloud-based file storage tool.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Self-hosted 3D model manager for print files; modest adoption in maker communities, active maintenance.
Manyfold is a Rails-based web application for organizing, previewing, and managing 3D model collections with focus on 3D printing workflows. It targets makers, hobbyists, and small teams with local/networked storage needs who want to avoid cloud dependency. Adoption appears concentrated in the 3D printing community (Fediverse presence, Mastodon activity). Real-world production usage is not explicitly documented in public channels.
Project initiated February 2021. Evolved from a personal asset management need into a community-driven tool. Now supported by OpenCollective donations and active volunteer contributors. Architecture reflects Rails conventions with focus on self-hosting simplicity.
Steady acquisition of ~45 stars per week (as of June 2026 snapshot) suggests modest but consistent interest. Growth appears organic within maker/3D printing circles rather than mainstream adoption wave. Recent activity (last push June 29, 2026) indicates active development cycle. Growth is slow relative to similar tools (filestash: 14k stars, modly: 4k stars) but this likely reflects narrower positioning rather than abandonment.
Adoption not verified. No published case studies, organization lists, or deployment count in README. Demo instance exists (try.manyfold.app) for evaluation. Community channels listed (Matrix chat, Fediverse social media, OpenCollective) suggest active user base exists but scale and deployment numbers are opaque. README emphasizes self-hosting simplicity and local control (appropriate for privacy-conscious makers) but production deployment specifics not documented.
Rails monolith with PostgreSQL (production) or SQLite (development). Server-side rendering with plain HTTP requests; no XHR/WebSocket yet. Three.js for client-side 3D rendering, Mittsu (Ruby THREE.js port) for server-side 3D analysis. Sidekiq for async jobs (thumbnail generation, file analysis via Assimp). Likely intended for single-instance or small-team deployments given Rails architecture.
Not documented in README. Presence of Codacy quality badge suggests CI/CD pipeline and some automated quality checks, but test strategy, coverage percentage, and test frameworks not detailed.
Last commit June 29, 2026 (within 24 hours of analysis date). Active CI/CD with GitHub Actions. Rubocop, ERB lint, and TypeScript linting enforced. Devcontainer support and clear development setup instructions suggest maintainer investment. Issue tracker mentioned; 'good first issue' label present (signals onboarding effort). No clear evidence of stalled PRs or unaddressed issues in README, but issue backlog size/age not visible.
ADOPT IF: you are a maker or small team managing a local/networked 3D model library and want self-hosted control with basic search, preview, and metadata features; you accept Rails-based infrastructure and don't need high-volume concurrent access or advanced permission models. AVOID IF: you need multi-tenant SaaS, cloud-native architecture, or enterprise-scale concurrent user support; your primary need is standalone 3D viewing rather than collection management; you lack Ruby/Rails infrastructure familiarity or ops capacity. MONITOR IF: you are evaluating self-hosted asset management for 3D workflows and want to track feature additions (ActivityPub federation mentioned in README, indicating federation plans); real-world deployment success stories would strengthen confidence in production stability.
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
3/10
- Adoption not quantified: production deployment count, total managed models, or user base size not public; community size unclear from available signals.
- Ruby/Rails operational burden: requires PostgreSQL, background job runner (Sidekiq), asset pipeline management; higher ops complexity than stateless tools; smaller operator community than Python/Go/Node alternatives.
- Single-instance design bias: architecture suggests scaling to multi-instance or high-concurrency may not be native; unclear how well it performs with large model collections (millions of files) or many concurrent users.
- Limited API surface: README mentions 'plain old HTTP requests' with no XHR/WebSocket; ActivityPub federation in development suggests future interop but current programmatic integration points not evident.
- Niche positioning lock-in: if 3D printing/maker community does not grow or consolidates around competing tools, adoption may plateau; mainstream asset manager adoption (beyond makers) appears unlikely given specialized UX.
Likely to remain a stable, actively maintained tool for 3D printing enthusiast and small maker communities. Mainstream asset manager adoption improbable; growth will track 3D printing industry adoption curves. Federation (ActivityPub) if completed could expand interoperability appeal. Slow, sustainable trajectory rather than rapid adoption or decline.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://manyfold.app
- Language
- Ruby
- License
- AGPL-3.0
- Last updated
- 11h ago
- Created
- 66mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Locally removed folders being recreated at scan
Manyfold issue trying to resolve a bunch of merges
Restrict library upload permissions
Write documentation on how to write plugins
Enable/disable plugins from UI
Top contributors
Similar repos
mickael-kerjean/filestash
Filestash is a universal file management platform that provides web-based and...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
2.1k | +10 | Ruby | 7/10 | 11h ago |
|
|
14.4k | — | Go | 7/10 | 10h ago |
|
|
4.5k | — | C++ | 8/10 | 1d ago |
|
|
2.6k | — | Python | 8/10 | 2d ago |
|
|
1k | — | PHP | 7/10 | 2d ago |
|
|
4.3k | — | TypeScript | 7/10 | 14h ago |
Filestash (14k stars, Go) is a general-purpose file manager. Manyfold is 3D-model-specific with built-in preview, metadata extraction (Assimp), and 3D printing workflow focus. Filestash broader; Manyfold deeper for this niche.
Modly (4.2k stars, TypeScript) appears focused on 3D model visualization/sharing. Manyfold emphasizes local asset management and self-hosting. Different primary use case (sharing vs. personal/team collection curation).
F3D (4.5k stars, C++) is a standalone 3D file viewer. Manyfold adds collection management, tagging, search, and multi-user support via web UI. F3D is client tool; Manyfold is server-centric.
Mayo (2.1k stars, C++) is a lightweight 3D viewer. Manyfold adds asset management layer, database, and web UI. Similar star count but different architectural scope.
Assimp (13k stars, C++) is a 3D model import library. Manyfold uses Assimp as a dependency for model analysis and metadata extraction, not a competitor.

