Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
An inventory management system for electronic components: assign each part to a category, footprint, manufacturer, storage locations and prices, attach datasheets, generate barcodes and labels, build bills of materials for projects, and keep an event log of changes. Users and groups have fine-grained permissions, and it can pull part data from suppliers such as Digikey and Farnell and act as a KiCad parts source. A Symfony (PHP) application; the Docker image runs with SQLite, or with MySQL or PostgreSQL.
Runs on a VPS from $4/mo (Kamatera 1GB, 1 GB RAM) · prices checked Nov 2026
Fits home hardware (180 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 untested), Raspberry Pi 5 (8 GB) (arm64 untested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick Part-DB when you keep electronic components and want to know what you have, where it is and what it costs. Each part gets a category, footprint, manufacturer, storage locations and prices, with datasheets attached, barcode labels, project bills of materials and an event log. It can pull part data from suppliers such as Digikey and Farnell, acts as a KiCad parts source and has an API. It is AGPL-3.0 PHP on Symfony. Our snippet is the project's Docker Compose example with the SQLite database, the image pinned to the `v2.20.4` tag and a generated `APP_SECRET`, followed by the documented database migration, which prints the initial admin password. We did not find an upstream RAM minimum, so our 256 MB floor is an estimate. InvenTree is the heavier choice when you also need purchase orders and a background worker, Homebox is a simpler home inventory and Snipe-IT is for IT assets.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# Part-DB — electronic parts inventory — based on the project's Docker Compose example (SQLite), pinned to v2.20.4
echo "APP_SECRET=$(openssl rand -hex 32)" > .env
cat > docker-compose.yml <<'EOF'
services:
partdb:
container_name: partdb
image: jbtronics/part-db1:v2.20.4
restart: unless-stopped
ports:
- '8080:80'
volumes:
- ./uploads:/var/www/html/uploads
- ./public_media:/var/www/html/public/media
- ./db:/var/www/html/var/db
environment:
- DATABASE_URL=sqlite:///%kernel.project_dir%/var/db/app.db
- DATABASE_SQLITE_ENFORCE_FOREIGN_KEYS=1
- APP_ENV=docker
- APP_SECRET=${APP_SECRET}
- DEFAULT_LANG=en
- DEFAULT_TIMEZONE=UTC
- BASE_CURRENCY=EUR
- INSTANCE_NAME=Part-DB
- ALLOW_ATTACHMENT_DOWNLOADS=0
- USE_GRAVATAR=0
EOF
docker compose up -d
timeout 120 bash -c 'until curl -s -o /dev/null http://localhost:8080/; do sleep 3; done'
docker exec --user=www-data partdb php bin/console doctrine:migrations:migrate --no-interaction
timeout 120 bash -c 'until curl -fsSL http://localhost:8080/ >/dev/null; do sleep 3; done'
# → http://SERVER_IP:8080 — sign in as admin with the initial password printed by the migration abovePart-DB's Docker installation page and configuration docs flag these before you use it:
Part-DB used 180 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 256 MB.
The Part-DB install snippet is marked verified on Ubuntu 26.04 (Nov 2026).