A household inventory that stays focused
Homebox solves a problem that is mundane until a move, insurance claim, repair, or warranty dispute makes it urgent: remembering what you own and where it is. The app stores items inside locations and categories, adds tags and custom fields, accepts photos and documents, and tracks prices, warranties, sales, and maintenance. Search turns that record into something more useful than a spreadsheet buried in cloud storage.
The scope is a major strength. Homebox is not trying to manage a warehouse or become a full home-automation hub. Its screens are designed around ordinary possessions and work on desktops, tablets, and phones. You can catalog a laptop with its serial number and receipt, put tools under a garage shelf, or attach a warranty to an appliance. QR labels provide a practical bridge between the database and the physical object.
The current repository continues the original project by hay-kot. It uses a Go backend, an embedded web interface, and SQLite by default. The README says the complete container generally uses less than 50 MB while idle. That is the right shape for a home server: one small application, one persistent data location, and no required external database.
Starting is easy, operating still matters
The published Docker command is enough for a useful trial. Mount /data, expose the application, set a time zone, and Homebox is ready in a browser. Official regular, rootless, and hardened images let operators choose a sensible security posture. Release binaries also exist for several systems and processor types.
The details become important once the inventory matters. The production Compose example adds an API-key pepper and explicitly controls analytics. A rootless or hardened bind mount needs ownership set for user 65532. The hardened image has no shell or utilities and cannot use the MQTT client. The maintainers primarily validate Linux and Docker, warn about Windows file-permission problems, and describe RISC-V binaries as experimental. Docker is therefore the sensible default even though a standalone binary looks simpler.
Homebox can grow beyond SQLite. PostgreSQL is documented, as are local, S3-compatible, Google Cloud, and Azure object storage. OIDC supports outside identity providers and group restrictions. Those are valuable options, but they create more pieces to secure and back up. A small household should resist adding them without a real need. Keep the data volume durable, put remote access behind HTTPS, pin or control updates, and practice restoring the database and attachments.
The data model is useful, with export catches
Locations, labels, entity types, and custom fields make Homebox flexible without forcing every user into an IT inventory vocabulary. Purchase information and warranty dates support insurance and replacement decisions. Maintenance entries suit filters, tools, vehicles, and appliances. Images help distinguish similar items, while documents keep receipts close to the records they support.
Bulk entry is less tidy. The documentation recommends CSV for large imports and explains a useful HB.import_ref value that deduplicates or updates existing items. It also lists hard limits: imports and exports omit attachments, exports flatten nested location paths to an item's direct parent, and item-to-item relationships cannot be specified. An open issue reports that Homebox's own export leaves HB.import_ref empty, so exporting and re-importing the unchanged file can create duplicates instead of behaving as a safe round trip. Anyone migrating or regularly editing inventory in a spreadsheet should test that workflow on a copy first.
QR scanning also deserves a device check. It is central to the appeal of labels, yet an active report describes the mobile scanner opening to a failed camera feed until the user switches between front and rear sensors, sometimes repeatedly. That does not make labels useless, but it is exactly the sort of friction that can stop family members from maintaining the inventory. Test the phones that will actually be used before printing a large label batch.
It is not enterprise asset management
Homebox supports multiple users and OIDC, but its account model is still being improved. An open project epic collects requests for better user and account administration. That matters for a family sharing one collection far less than it does for a company that needs precise roles, approvals, checkouts, and auditable responsibility. Snipe-IT is a more natural fit for the latter.
The interface also carries visible rough edges. Current reports cover low-contrast form borders in dark mode, inconsistent location ordering, archived items appearing in one location view but not another, and Cyrillic search failing on the first word of an item name. These are specific usability defects rather than signs that the core idea is broken. They do mean a multilingual household or a user with accessibility needs should spend time in the public demo before importing data.
Healthy development and a clear buying decision
The repository was pushed on August 7, 2026, while issues and pull requests were still being updated on August 8. The latest tagged release, v0.26.2, arrived June 14 with fixes for several newly introduced bugs. GitHub's open count of 120 combines issues and pull requests, and the recent queue includes both bug reports and substantial feature work. The project is active, though that activity also reflects software that is changing quickly.
Documentation is better than the short README alone suggests. The separate site covers Docker and binaries, every configuration variable, SQLite and PostgreSQL, storage backends, proxies, OIDC, importing, user concepts, and development. The public stable and nightly demos lower the cost of judging the interface before installation.
Homebox earns a recommendation for personal inventories because it chooses the right level of ambition. It makes detailed records possible without demanding business-process ceremony, and the default deployment fits modest hardware. The honest qualification is that data portability, mobile scanning, and user administration are not finished stories. Start with a representative room, verify export and restore behavior, then expand if the household actually keeps using it.