Define the archive problem first
A self-hosted deployment only matters if the private-library workflow is the right fit.
STL Shelf can run as self-hosted 3D model library software because it is open source, while the hosted version managed by us remains the easier path for most users.
Self-hosting is a deployment choice for ownership requirements, not the main product experience.
A self-hosted deployment only matters if the private-library workflow is the right fit.
Choose self-hosting only when the deployment model must align with a specific private-archive requirement.
The hosted version managed by us is the lower-friction choice for most users.
Self-hosting is relevant when private 3D model library software must run on infrastructure you control. If that requirement is absent, the hosted version removes unnecessary operational work.
STL Shelf is open-source software for managing private 3D printing model libraries. Self-hosting is available because of that, but the product remains primarily a private library workflow rather than a deployment story.
Yes. It can be self-hosted because it is open source.
Not for most users. The hosted version managed by us is usually the simpler option.
Setup details live in the repository documentation. This guide focuses on ownership, privacy, and deployment choice.
No.
Use the hosted product for speed or self-host the open-source stack when deployment control is non-negotiable.