// the take
Spoolman is a self-hosted database for tracking 3D-printer filament spools, syncing spool weight automatically as Klipper/Moonraker or OctoPrint print jobs consume filament. It's for anyone running more than a printer or two who's tired of guessing how much filament is left on a spool.
Real integration, not just a CRUD app — Moonraker/OctoPrint push live weight updates over websockets as a print progresses, so the data stays accurate without manual entry. It supports SQLite, PostgreSQL, MySQL, and CockroachDB, so it scales from a single Raspberry Pi to a shared multi-printer setup. The ecosystem around it is real: Home Assistant, Prometheus metrics, and even an MCP server for AI assistants, which suggests the API is solid enough that other projects build on it rather than around it.
It's a one-person project (sponsorship ask front and center in the README), so bus-factor risk is real for something you'd depend on to not lose inventory data. The project is mid-migration between two separate client codebases (a React one and a new SvelteKit one) shipped side by side with an env var to fall back to the old one — that's a sign the new client may still have rough edges, and you're the one who has to notice and flip the switch. The README says nothing about authentication or access control, which matters since this is a networked service meant to be hit by multiple printers and clients; if you expose it beyond localhost you're on your own for securing it. The filament spec data relies on a community-maintained database (SpoolmanDB), so coverage and accuracy for less common brands will vary.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →