English
Spoolman Hosting
Track 3D-printing filament spools, usage, and inventory with a tidy web database and API.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- ghcr.io/donkie/spoolman:latest
- Default port
- 8000
How Spoolman works
Spoolman keeps manufacturers, filament types, individual spools, locations, custom fields, and usage records in one inventory. The web client lets an operator create and edit records, search or group the collection, filter by material or location, and prepare labels with QR codes for identifying physical spools.
A REST API and WebSocket updates let compatible printing software read and change inventory data. Moonraker, Klipper front ends, OctoPrint, Home Assistant, and other integrations can report consumption as jobs progress. Those integrations remain separate systems and must be pointed at the hosted Spoolman address by the user.
Key Spoolman features
The catalogue package persists the Spoolman data directory, which includes the default local database and application state. No PostgreSQL or MariaDB service is provisioned. Inventory records, usage history, labels, custom fields, and integration settings therefore depend on the attached application volume remaining available through updates and recovery.
Spoolman has no built-in user authentication. Its upstream security guidance states that anyone who can reach the service can read and change the inventory. HTTPS protects traffic in transit but does not add an account gate, so the hosted page must not present the public URL as a private multi-user workspace.
Who uses Spoolman
Home printers use Spoolman to remember which reel is mounted, how much material remains, and where replacements are stored. Shared workshops can label shelves and spools, while small production teams connect several printers to one inventory so consumption updates do not live in separate spreadsheets.
The application is designed around filament administration rather than printer control. It does not schedule jobs, slice models, operate printers, or supply OctoPrint, Moonraker, Klipper, Home Assistant, Prometheus, label hardware, or scanner devices as part of the hosted package.
Self-hosting Spoolman: requirements and cost
Resource use grows with spool and filament records, usage history, label assets, API traffic, WebSocket activity, integrations, simultaneous printers, and concurrent browsers. The catalogue records PostgreSQL and MariaDB as Not required and persists the application data directory, so the local database and inventory files must be treated as one recovery set.
On AvaHost, Spoolman uses Plan 1 at €2. The hosted Spoolman package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Spoolman itself provides no authentication layer. Anyone who can reach the assigned domain can view or modify inventory, and AvaHost does not claim an added access-control proxy. Connect only trusted integrations, keep API consumers under your control, and avoid placing sensitive operational data in an openly reachable instance.
F.A.Q
Spoolman starts at €2 on Plan 1. The entry plan suits a modest filament catalogue and light API activity. Spool count, usage history, label data, WebSocket traffic, connected printer services, and simultaneous browsers are the practical signals for deciding whether the installation needs more processing or storage.
Spoolman does not include built-in authentication, and the hosted template does not add a separate access-control layer. Anyone who can reach the domain can inspect or change inventory records. Use the service only with a trusted access path and do not treat HTTPS by itself as protection against unauthorised inventory changes.
Compatible software can connect through Spoolman’s documented API, but the printer service, plug-in, credentials, and network configuration are not bundled. Point each trusted integration to the final HTTPS address, test read and write behaviour with a non-critical spool, and confirm that no untrusted system can reach the same endpoint.
AvaHost applies application updates and keeps the persistent Spoolman data directory attached to the service. Scheduled backups are included for the hosted installation. The local database, custom fields, labels, and usage records should be considered one data set, so review important integrations and inventory totals after a substantial upstream change.