Open-Source Databases · Part-DB

Part-DB-server

Part-DB is an open-source web-based inventory management system designed for electronics components. It provides multi-user access with fine-grained permissions, barcode scanning, BOM management, and integration with cloud suppliers and KiCad.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/Part-DB/Part-DB-server

1.7k

GitHub stars

215

Forks

PHP

Primary language

AGPL-3.0

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	Part-DB/Part-DB-server
Owner	Part-DB
Primary language	PHP
License	AGPL-3.0 — OSI-approved
Stars	1.7k
Forks	215
Open issues	205
Latest release	v2.13.1 (2026-06-29)
Last updated	2026-07-06
Source	https://github.com/Part-DB/Part-DB-server

What Part-DB-server is

PHP/Symfony 7 application supporting MySQL, MariaDB, PostgreSQL, and SQLite backends. Requires PHP 8.2+, includes REST API, two-factor authentication (TOTP/WebAuthn), optional SAML SSO, and responsive web UI built with modern frontend tooling.

Quickstart

Get the Part-DB-server source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/Part-DB/Part-DB-server.git2cd Part-DB-server3# follow the project's README for install & configuration

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

Best use cases

Electronics Hobbyist/Maker Space Inventory

Track personal or shared component inventory with barcode scanning, organized by category/footprint/manufacturer. Low-cost self-hosted deployment suits small teams.

Small Company/University Component Management

Multi-user system with role-based permissions, audit trails, and project-level BOM tracking. Supports cost tracking across multiple currencies.

KiCad Integration Workflow

Central datasource for electronic parts; KiCad plugin allows direct visibility of available inventory within the design tool, reducing manual cross-referencing.

Implementation considerations

Database choice (MySQL vs. PostgreSQL vs. SQLite) impacts performance and concurrency; for multi-user deployments, MySQL/PostgreSQL preferred and cannot be easily changed post-setup.
Requires Node.js 22+ and Yarn for frontend asset building; cannot skip this step during initial deployment or upgrades.
Admin password generation during database migration must be captured immediately; recovery requires CLI access with `app:set-password` command.
Two-factor authentication and SAML SSO are optional but recommended for multi-user production instances; configuration adds setup complexity.
Reverse proxy deployments must explicitly set `TRUSTED_PROXIES` env var to avoid HTTP/HTTPS and hostname issues.

When to avoid it — and what to weigh

Requires Proprietary SaaS Only — Part-DB requires self-hosting on your own infrastructure. If you need a fully managed cloud service, this is not suitable.
Limited DevOps Capability — Deployment demands shell access, knowledge of web server configuration (Apache/nginx), PHP environment setup, and database administration. Self-hosting adds operational burden.
AGPL-3.0 License Restrictions — If you modify the application and distribute it as a service, you must open-source your modifications. Review AGPL obligations before modifying or embedding.
Enterprise Single Sign-On via LDAP Natively — LDAP/AD integration requires an intermediate service (e.g., Keycloak). Direct LDAP connector is not built in; requires additional infrastructure.

License & commercial use

Licensed under AGPL-3.0 (GNU Affero General Public License v3.0). This is a copyleft license: any distribution or modification must open-source derived works and provide source code to users. Network use triggers distribution obligations.

Commercial use of Part-DB as-is (self-hosted internal tool) is permitted under AGPL-3.0. However, if you modify Part-DB and offer it as a service to others (SaaS), you must release your modifications as open-source and comply with AGPL copyleft terms. Embedding Part-DB into a proprietary product requires careful legal review. Requires explicit counsel for commercial derivatives.

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

Two-factor authentication (TOTP and WebAuthn/U2F) available and can be enforced per user group. SAML SSO support enables delegation to identity providers. Fine-grained permission model allows role-based access control. Event log tracks user actions for audit. Sensitive features: database password, admin account, and reverse proxy `X-Forwarded-*` headers must be configured correctly. No explicit mention of encryption at rest, rate limiting, or OWASP compliance in provided data; security posture requires independent assessment and configuration review.

Alternatives to consider

KiCad Schematic and PCB Editor (Built-in Part Libraries)

If your workflow is KiCad-centric and inventory complexity is low, KiCad's native library system plus external part databases (DigiKey API, etc.) may suffice without a separate inventory system.

Proprietary SaaS (e.g., Snappy Inventory, Cin7, TrackStock)

If you prefer hosted cloud services, no-ops management, and vendor support, commercial SaaS platforms eliminate self-hosting operational burden and may include more enterprise features.

Legacy Part-DB (< 1.0.0)

If you have an existing legacy Part-DB deployment, the rewrites introduces breaking changes; however, upgrade path is documented and recommended by maintainers.

Software development agency

Build on Part-DB-server with DEV.co software developers

Part-DB offers a powerful, free, self-hosted solution for electronics inventory. Explore the demo, review deployment requirements, and assess AGPL compliance for your use case. Contact us for custom deployment, integration, or compliance review support.

Talk to DEV.co

Related open-source tools

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

db databasement buntdb

Related on DEV.co

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

Open-Source Databases Custom Web Application Development API Development & Integration DevOps & Infrastructure Setup Talk to DEV.co

Part-DB-server FAQ

Can I use Part-DB in the cloud (AWS, Azure, DigitalOcean)?

Yes. Part-DB can run on any VPS/cloud instance with PHP 8.2, a web server, and database support. Docker image simplifies cloud deployment. Ensure reverse proxy headers are trusted correctly.

What is the upgrade path from legacy Part-DB (< 1.0)?

A dedicated upgrade guide exists at docs.part-db.de/upgrade_legacy.html. The rewrite is significant; review the guide before planning a migration.

Can I use Part-DB offline?

No. Part-DB is a web-based application requiring a running web server and database. Offline usage is not supported. However, mobile access via responsive UI is available in-browser.

Does Part-DB charge licensing or subscription fees?

No. Part-DB is free open-source software (AGPL-3.0). No license fees apply. Costs are limited to hosting infrastructure and your operational time.

Software development & web development with DEV.co

Adopting Part-DB-server is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source databases software in production.

Ready to Manage Your Component Inventory?

Talk to DEV.co Schedule a Consultation