A lightweight filament tracker for home 3D printing.

Spoolman light is a self-hosted web service for tracking your 3D printer filament spools. It is a simplified fork of Donkie/Spoolman designed for home use — one or two printers and a shelf of spools — with no database server, no vendor management, and no external integrations required.

• Filament & Spool Tracking: Keep records of filament types and individual spools, including RGBA color(s) on the spool.
• Location Management: Organise spools into named locations (shelves, dry boxes, etc.) with live spool counts.
• Weight Tracking: Record initial and current weight (scale readings); used weight and remaining percentage are derived automatically.
• SpoolmanDB Search: Filament lookup via the SpoolmanDB online database (GET /api/v1/filament/search).
• Data Export: Download the full data store as JSON via GET /api/v1/export.
• REST API: Clean REST API compatible with Spoolman-aware clients (Klipper plugins, OrcaSlicer, etc.).
• Web Client: Built-in browser UI with dark mode support.
• Simple Storage: All data stored in a single JSON file — no database server required.

Build the image and start a container with a persistent data volume:

docker build -t spoolman-light .
docker run -d \
  --name spoolman \
  --restart unless-stopped \
  -p 8000:8000 \
  -v spoolman_data:/data \
  spoolman-light

Or use the included docker-compose.yml:

docker compose up -d

The web UI is available at http://localhost:8000.

Building requires Linux/WSL/Docker — cargo leptos build fails on native Windows because openssl-sys needs OpenSSL dev headers. Build inside WSL, a Linux machine, or via docker build . which handles everything in a multi-stage container.

All variables can be set in a .env file in the working directory — the server loads it silently on startup (a missing file is not an error).

Step 1 — build the image on a Linux machine or in WSL:

docker build -t spoolman-light:latest .

Step 2 — transfer the image to the NAS. Either:

• Export/import via file:

  docker save spoolman-light:latest | gzip > spoolman-light.tar.gz
  scp spoolman-light.tar.gz admin@synology:/volume1/docker/

  Then in Container Manager → Image → Add → Add from File.

• Or push to a registry and pull from Synology:

  docker tag spoolman-light:latest yourname/spoolman-light:latest
  docker push yourname/spoolman-light:latest

Step 3 — create a data directory on the NAS and fix ownership (the container runs as uid 65532):

# SSH into Synology
mkdir -p /volume1/docker/spoolman-light/data
chown 65532 /volume1/docker/spoolman-light/data

Step 4 — deploy via Container Manager → Project → Create, using this compose file:

services:
  spoolman:
    image: spoolman-light:latest
    restart: unless-stopped
    ports:
      - "8000:8000"
    volumes:
      - /volume1/docker/spoolman-light/data:/data
    environment:
      - SPOOLMAN_DATA_FILE=/data/spoolman.json
    security_opt:
      - no-new-privileges:true

Step 5 (optional) — HTTPS via DSM reverse proxy: in Control Panel → Login Portal → Advanced → Reverse Proxy add a rule pointing https://spoolman.yourdomain → http://localhost:8000.

Your data persists in /volume1/docker/spoolman-light/data/spoolman.json and is visible in File Station.

Requirements: Rust stable (see rust-toolchain.toml), cargo-leptos, wasm32-unknown-unknown target.

rustup target add wasm32-unknown-unknown
cargo install cargo-leptos --locked

cargo leptos build --release
./target/release/spoolman-server

A Filament is a material specification shared across one or more spools — the brand, material type, and print settings. Colours live on individual spools, not on the filament.

SpoolmanDB lookup — the search bar at the top of the form queries the SpoolmanDB online database. Selecting a result auto-fills all fields, saving manual entry.

A Spool is a physical roll of filament. It references a Filament for material properties and adds colour, weight, location, and pricing.

Weight tracking — after each print, open the spool and enter the new scale reading in Current weight. The UI derives:

• Used weight = initial weight − current weight
• Remaining filament = current weight − (initial weight − net weight), i.e. net weight minus used filament

Why no empty-spool weight database? Other trackers subtract an empty spool weight taken from a community-maintained catalog. Spoolman light instead has you weigh the full, factory-new spool. That reading is at least the nominal filament weight (e.g. 1000 g) plus the empty spool, measured on your own scale for your actual spool. This is more reliable than a community-provided measurement of a similar empty spool.

Locations are named storage spots (dry box, shelf A, printer enclosure, …). Each location shows a live count of spools stored there. Spools can be filtered by location in the spool list.

The Color sidebar entry (/colors) shows spools as a card grid instead of a table — each card filled with the spool's colour(s) and labelled with colour name, filament, material, remaining weight and location. Cards are ordered by hue then lightness, with greys, black and white grouped last. The material filter is shared with the spool table (a checkbox row here, the table's dropdown there); sort and page position are remembered separately per view.

Default view (Settings) — spool or color; decides which view the / route renders. Default spool.

The entire application ships as a single self-contained binary with no Python runtime, no Node.js, and no external database.

If you have data in the original Donkie/Spoolman, use the included converter script to produce a spoolman.json file that this service can load.

Step 1 — export from the old Spoolman:

GET /api/v1/export/spools?fmt=json    → save as spools_export.json
GET /api/v1/export/filaments?fmt=json → save as filaments_export.json  (optional)

Step 2 — convert:

python scripts/convert_export.py spools_export.json \
    --filaments filaments_export.json \
    --output spoolman.json

Step 3 — start this service pointing SPOOLMAN_DATA_FILE at the output file:

docker run -p 8000:8000 -v /path/to/data:/data \
  -e SPOOLMAN_DATA_FILE=/data/spoolman.json \
  spoolman-light

--filaments is optional but recommended — it includes filaments that have no associated spools.

There is no data-upload/restore endpoint or UI. To import or restore spoolman.json, stop the server, replace the file at the path reported by /info, and restart.

This fork deliberately omits features that add complexity without value for home use:

• No Vendor entity (vendor is a plain string on Filament)
• No extra-fields system
• No WebSocket live-updates (use polling)
• No Prometheus metrics
• No multi-database support (JSON file only)
• No QR / label printing page

• https://github.com/yanshay/SpoolEase
• https://github.com/olmos-cmd/Filament-Tracker
• https://github.com/Tellus75/spool_manager_U1/blob/main/README.en.md
• https://github.com/XMan0085/Filament-Manager
• https://github.com/LatinoF/LTFSpoolManager
• https://github.com/Fire-Devils/filaman-system