Every item holds a memory · Inventory management, movement diary, reminders

KoiX HomiaryHome inventory diary

A self-hosted inventory system for people and households, run with Docker on your own machine. Assets, members, locations, categories and tags all live in your own database, and every change leaves a record you can read back.

Status
Released · actively updated
For
Individuals / households
Platform
Self-hosted with Docker, used in a browser
Data
SQLite or PostgreSQL

Core experience

Things get forgotten.
Their stories shouldn’t.

A household accumulates more than anyone can hold in memory—what was bought, where it ended up, whether it is still under warranty. KoiX Homiary writes each asset as a diary: every change of location, owner, keeper, or status is recorded automatically, so you can read all the way back to the day it arrived.

01

Asset records with an automatic diary

Name, brand, model, serial number, category, purchase price and valuation, warranty, and asset tag live in one record. Every change of location, owner, keeper, or status is written into the diary automatically, and you can always add a note by hand.

02

The shape of a home: members, places, categories, tags

A location tree of any depth, household members with permissions, standalone categories, and a colour-coded tag system. A whole location can be moved along with its children, and every asset keeps its own transfer record; a category or tag that still holds assets refuses to be deleted.

03

Overview, valuation trend, reminders

Asset count, valuation and total spend—both split between physical and virtual—new items this month, and member stats are gathered on the dashboard, alongside a valuation trend accumulated by purchase date and a category breakdown. Warranty, return, and maintenance reminders follow your settings; the header bell reads the same data, and it can go out as one daily email digest.

Modules

Twelve pages, the whole life of one thing

Every page reads and writes the database directly—the numbers on screen come from real data, with no fixtures left in the repository.

01Dashboard
Counts, valuation and spend, trends, category split and recent events on one screen.
02Physical assets
Server-side search and filters, card or table view, eight ways to sort.
03Virtual assets
Subscriptions, domains and licences in their own list—no location, no loans or repairs.
04Asset detail
The full record and warranty; location, owner and status changes log themselves.
05Members
Members, permissions and active state, with live owned-asset counts and valuation.
06Spaces and locations
A location tree of any depth; move a whole level and every asset keeps a transfer record.
07Categories
Categories and colours with live counts; renaming leaves existing assets alone.
08Tags
Tags and colours; deleting a tag also clears it from the assets that carried it.
09Care and renewals
Repair records, this year’s cost against last, items under warranty, and repeating due dates.
10Loans and returns
Loans and returns, with due-soon and overdue worked out and written back to the asset.
11Disposal
Selling, gifting and scrapping, with fees, payout and profit or loss, plus the data-wipe checklist.
12Settings
Currency, password, automatic backups, reminder rules, email notifications and theme.

Deploy

One command, on your own machine

The image is published on Docker Hub for linux/amd64 and linux/arm64, matched automatically on pull. Everything persistent lives in /data inside the container—database, config and backups—so mounting it as a volume keeps upgrades and rollbacks away from your data. The one piece still unfinished is asset photos and receipt attachments: the table is built and included in backups, but there is no upload interface yet.

  • A single docker run brings it up: publish port 3000 and mount /data as a named volume.
  • The first visit lands on the setup page: choose SQLite or PostgreSQL and create the admin account.
  • No account ships with the image; SMTP, backup schedule and reminder rules are configured in settings, not through environment variables.
  • The container speaks plain HTTP—terminate TLS in front of it with Nginx, Caddy, or Traefik before exposing it.

Next product

Continue to KoiX ToolKit