Open-Source Databases · Donkie

Spoolman

Spoolman is a self-hosted web service that tracks 3D printer filament inventory and monitors spool usage in real time. It integrates with popular 3D printing platforms like OctoPrint and Klipper, automatically updating spool weights as printing progresses and providing a centralized database for filament management.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/Donkie/Spoolman

2.6k

GitHub stars

260

Forks

Python

Primary language

MIT

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	Donkie/Spoolman
Owner	Donkie
Primary language	Python
License	MIT — OSI-approved
Stars	2.6k
Forks	260
Open issues	299
Latest release	v0.24.0 (2026-07-07)
Last updated	2026-07-08
Source	https://github.com/Donkie/Spoolman

What Spoolman is

Python-based REST API service with WebSocket support for real-time updates, compatible with SQLite, PostgreSQL, MySQL, and CockroachDB. Provides multi-printer management, Prometheus integration for historical analysis, and a React-based web client with label printing and QR code generation capabilities.

Quickstart

Get the Spoolman source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/Donkie/Spoolman.git2cd Spoolman3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Filament Inventory Management for Multi-Printer Farms

Organizations or enthusiasts running multiple 3D printers can centralize spool tracking, automatically log filament consumption across all devices, and generate usage reports via Prometheus integration for cost optimization.

OctoPrint/Klipper Ecosystem Integration

Teams already invested in OctoPrint, Moonraker, or Klipper can deploy Spoolman as a lightweight spool-tracking microservice without replacing existing infrastructure, leveraging native plugins and API hooks.

Home Assistant Smart Home Integration

Home automation setups can embed Spoolman to trigger alerts when filament runs low, log printing metrics to historical dashboards, and enable voice-controlled inventory queries via the MCP Server integration.

Implementation considerations

Database selection: SQLite suitable for small setups; PostgreSQL/MySQL recommended for production multi-printer deployments due to concurrency and scalability.
API authentication model not detailed in provided data; review security posture and access control mechanisms before exposing to untrusted networks.
WebSocket requirement for real-time updates may require reverse proxy configuration (nginx/Traefik); verify firewall and load-balancer compatibility in your stack.
Community filament database (SpoolmanDB) requires periodic sync; consider data freshness strategy and conflict resolution for local vs. upstream changes.
Label printing and QR code generation add dependency on client-side rendering; test across browsers and mobile devices if using print functionality at scale.

When to avoid it — and what to weigh

Proprietary 3D Printer Ecosystem Lock-in — If your primary printer runs a closed ecosystem with no REST API or WebSocket support, Spoolman integration will be limited or impossible without custom middleware.
Minimal DevOps Resources — This is a self-hosted service requiring database management, container orchestration, and ongoing maintenance; not suitable for teams seeking fully managed SaaS solutions with zero operational burden.
High-Compliance, Regulated Environments — Enterprise environments requiring SOC 2, HIPAA, or FedRAMP compliance cannot rely on a single-maintainer community project; no evidence of formal security audits or compliance certifications provided.
Real-Time High-Availability SLAs — If you need guaranteed 99.9%+ uptime with service-level guarantees, Spoolman—as a community-maintained project—offers no formal SLA or commercial support contract.

License & commercial use

MIT License (OSI-approved, permissive). Allows commercial use, modification, and distribution with attribution and liability disclaimer. No copyleft obligations.

MIT license permits commercial deployment without royalties or license restrictions. However, there is no commercial support, warranty, or liability indemnification from the maintainer. Deploying in commercial environments should include internal support planning and potential forking strategy if upstream maintenance stalls.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Moderate
DEV.co fit	Good
Assessment confidence	High

Security considerations

No formal security audit data provided. Self-hosted deployment places responsibility on operator for network isolation, authentication setup, and secret management. WebSocket communication should be encrypted (WSS). Database credentials and API tokens require careful rotation policy. Community-driven security patches; no formal vulnerability disclosure process mentioned.

Alternatives to consider

Mainsail / Fluidd (Klipper front-ends)

Native Klipper integration but lack dedicated filament tracking; better for unified UI if printer compatibility is primary concern.

OctoPrint Plugins (octoprint-spoolman or similar)

Tighter OctoPrint integration but limited to single-printer or ad-hoc spool management; less scalable for farms.

Home Assistant + Template Sensors

Full home automation integration but requires manual scripting and lacks dedicated filament database; steeper learning curve for non-technical users.

Software development agency

Build on Spoolman with DEV.co software developers

Devco specializes in containerized microservices, API integrations, and DevOps infrastructure. We can architect, deploy, and maintain Spoolman for your multi-printer farm or home automation setup. Contact us for a consultation.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

sandman2 psycopg schemaspy

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Databases API Development Custom Software Development DevOps & Infrastructure Talk to DEV.co

Spoolman FAQ

Can Spoolman run on a Raspberry Pi?

Unknown. Installation page references Docker; actual resource requirements (CPU, RAM, disk I/O) not specified. Feasibility depends on Pi model, database choice (SQLite vs. PostgreSQL), and concurrent printer count. Recommend testing with a small deployment.

Does Spoolman support cloud deployment (AWS, Azure, GCP)?

Unknown. No explicit cloud hosting documentation provided. Containerized architecture suggests compatibility, but data residency, ingress routing, and managed database integration require custom configuration.

Is there a mobile app for Spoolman?

Not mentioned in the provided data. Web client is responsive; mobile browser access may work, but native iOS/Android apps are not documented.

What happens if Spoolman goes offline during a print?

Unknown. The relationship between Spoolman availability and printer operation is not detailed. If Spoolman is only for historical tracking (not real-time printer control), downtime should not interrupt printing; verify architecture with maintainer or code review.

Custom software development services

Need help beyond evaluating Spoolman? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source databases integrations — and maintain them long-term.

Need Help Deploying Spoolman?

Talk to DEV.co Schedule a Consultation