PrintStash-API

PrintStash API is the deprecated backend container for the legacy two-container PrintStash deployment, a self-hosted 3D print library and G-code vault.

  • Backup
  • Productivity
  • Tools & Utilities
PrintStash API is the deprecated backend container for the legacy two-container PrintStash deployment, a self-hosted 3D print library and G-code vault. It stores STL, 3MF, OBJ, STEP, G-code, and BGCODE files with searchable metadata, thumbnails, collections, tags, revisions, print history, user access, printer connections, and backups. Use it only for existing two-container installations; new installs should use the unified PrintStash template.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

33/100 Low

Maintained
34last commit 391 days ago
Popular
61 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
701 GB minimum RAM

Availability: platform listings confirmed today, links checked 19 days ago

GitHub stars
1
Open issues
0
Last commit
2025-10-26
License
Apache-2.0
Activity
stale

Checked today - source: GitHub (GrolimundSolutions/PrintStash-api)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 1 CPU core(s).

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Use the official one-line installer Run the provided curl install command in a terminal on the machine you want to host PrintStash. This uses the official installer, so you don’t need a cloud account or extra telemetry setup before starting. source
  • Legacy two-container setup For legacy installs only, deploy the API with PrintStash-Frontend on a user-defined Docker network named printstash, set VAULT_JWT_SECRET, and let the frontend reach the API as hostname api. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How should legacy PrintStash-API be deployed?

It is for legacy installs only. Deploy the API with PrintStash-Frontend on a user-defined Docker network named printstash, set VAULT_JWT_SECRET, and let the frontend reach the API as the hostname api.

When do I need to configure PrintStash after installation?

Configure it after installation or when changing the server environment. The documentation covers core concepts such as Models, Artifacts, revisions, the Vault, and shared volumes.

Can self-hosted PrintStash be connected to S3 storage?

A self-hosted print-shop example wires PrintStash into S3 storage and uses a zero-secret CI/CD pipeline.

What print-status notifications can be sent?

PrintStash can alert when a print finishes, fails, is cancelled, or a printer goes offline. Alerts can be delivered to webhooks, Discord, Telegram, or ntfy.

Do I need a cloud account for the official installer?

No. The official one-line installer starts PrintStash without a cloud account or extra telemetry setup.

Answers sourced from blog.wizard-networks.com, ca.unraid.net, printstash.org, wiki.printstash.org, www.printstash.org

Community

Collected 49 days ago - public community threads