Introduction
Inventorix is a self-hostable inventory and asset management application built on Laravel 13 and Filament 5. This Administration Manual covers installing, deploying, configuring, and operating Inventorix in production — it is written for the person running the instance, not the day-to-day user.
What Inventorix is
Section titled “What Inventorix is”Inventorix gives small teams a clean web UI for tracking physical assets from purchase through retirement. Everything runs inside a single Docker container; there is no external agent or proprietary cloud service required.
Key highlights from the project:
- Filament v5 admin panel with a responsive UI
- QR-code generation for individual assets
- PDF exports powered by DomPDF
- Microsoft Entra ID (Azure AD) SSO via Laravel Socialite
- Activity log and tagging via the Spatie ecosystem
- Production runtime: Laravel Octane on FrankenPHP
- Background jobs managed by Laravel Horizon
Architecture
Section titled “Architecture”| Layer | Technology |
|---|---|
| Application framework | Laravel 13 |
| Admin panel | Filament v5 |
| HTTP server | Laravel Octane on FrankenPHP |
| Queue worker | Laravel Horizon |
| Database | MySQL or MariaDB |
| Cache / queue backend | Redis |
| File storage | S3-compatible object storage (or local disk) |
| PDF generation | barryvdh/laravel-dompdf |
| Activity logging | spatie/laravel-activitylog |
| Tags | Filament Spatie Tags plugin |
| SSO | socialiteproviders/microsoft-azure via Laravel Socialite |
The application exposes a single Filament panel (App) on port 8000. Horizon is not started by the entrypoint; it must be run as a separate container or process (see the Docker deployment page). The Horizon dashboard is available at /horizon on the app container.
Feature tour
Section titled “Feature tour”Assets
Section titled “Assets”The core of Inventorix is the Asset resource. Each asset record carries:
- A type (from the AssetType catalogue), a model (from the AssetModel catalogue linked to a Manufacturer), a serial number, purchase date, purchase type, purchase price, and warranty end date.
- A state (tracked as an enum on each asset).
- An owner (a user) and a place (a location).
- Tags for free-form categorisation.
- An attached invoice file stored on the configured filesystem disk.
Assets can be imported from and exported to CSV through Filament’s built-in import/export actions.
Catalogue
Section titled “Catalogue”Three supporting resources maintain the reference data that assets link to:
- Manufacturers — brand names (e.g. Dell, Apple).
- Asset Models — specific product models linked to a manufacturer.
- Asset Types — categories such as Laptop, Monitor, Printer.
Locations (Places)
Section titled “Locations (Places)”The Places resource stores physical locations where assets reside. Each asset carries a place_id foreign key so you can filter and report by location.
Handovers
Section titled “Handovers”The Handover resource records transfers of one or more assets between users. Each handover captures the signing date, the assets involved, and the previous and new owner for every asset in the batch. A handover wizard action guides the operator through the process. Handover history is visible per-asset and as a top-level list.
Incidents
Section titled “Incidents”The Incident resource tracks damage or failure events on individual assets. Incidents are linked to a specific asset and have an open date.
Warranty tracking and notifications
Section titled “Warranty tracking and notifications”Assets carry a guarantee_end date. The warranty:scan-expiries Artisan command scans upcoming warranty expirations and sends a grouped email digest to configured recipients. Lead-time days and recipient addresses are configured through the Warranty Settings page in the panel. The command is designed to be run on a schedule (e.g. daily via cron).
QR code generation
Section titled “QR code generation”The QR Code Generator page (/app/qr-code-generator) produces printable QR codes for one or more assets. Individual assets also have a Print QR action directly on their record.
Evaluation reports
Section titled “Evaluation reports”The Evaluation section provides several built-in reports accessible from the panel:
- Asset Aging Report
- Asset Value Report
- Assets Per Employee Report
- Guarantee Status Report
- Handover History Report
- Incident History Report
- Inventory by Location Report
- State Overview Report
Reports render in-panel and can be exported as PDFs.
Activity log
Section titled “Activity log”Every create, update, and delete action on assets and related records is logged automatically by Spatie Activitylog. Logs are visible per-asset on its History relation tab.
User management
Section titled “User management”Users are managed inside the panel through the Users resource. Access to the panel is gated by the login_enabled flag on each user record. Multi-factor authentication (TOTP app) is supported and enforced optionally through Auth Settings.
Settings
Section titled “Settings”A Settings cluster in the panel groups the following configuration pages:
- General Settings — application-wide defaults.
- Auth Settings — MFA enforcement, SSO toggle.
- Mail Settings — outbound mail configuration.
- Warranty Settings — notification lead days and recipients.
What this manual covers
Section titled “What this manual covers”| Section | Content |
|---|---|
| Requirements | PHP, database, Redis, storage prerequisites |
| Docker deployment | Quickstart, compose example, entrypoint behaviour |
| Environment configuration | All env-var groups explained |
| First run | Migrations, creating the first admin user |
The user manual (navigating the panel as a day-to-day operator) and the reference section (complete env-var table, CLI command reference) are covered in their respective parts of this documentation site.