Warracker, a self hosted warranty tracker that records what you own, when cover expires and where the receipts are.
Warracker is an open source, self hosted warranty tracker. It replaces the receipt in a drawer, the confirmation email in one inbox and the manual in another with a single searchable record per product: purchase date and price, vendor, serial and model numbers, warranty length or an exact expiry date, notes, tags, and the paperwork itself. Receipts, invoices, manuals and product photos are uploaded and stay attached to the entry for as long as you keep it.
A dashboard sorts and filters by expiry so the things about to run out surface on their own, and a statistics view shows what has been spent and what is still covered. Expiry reminders can go out by email through your own mail server, or as push notifications to Discord, Slack, Telegram, Teams, ntfy and dozens of other services. It supports multiple users with an administrator role, optional single sign on through any OpenID Connect provider, optional integration with a Paperless-ngx archive, a light and dark interface, and more than a dozen translated languages. It suits households, landlords, workshops, IT teams and finance teams who need to know what is still under warranty and be able to prove it.
The upstream project hands ownership of an instance to whoever registers first, and will accept that registration on an empty database whatever the registration setting says, so a public address is a race between the owner and a stranger. The cloudimg image never enters that state: first boot seeds exactly one administrator with a password unique to the machine and closes public registration in the same step, so the registration endpoint refuses everyone from the moment the instance is reachable. The session signing key, both PostgreSQL role passwords and the administrator password are all generated on the machine at first boot and written to a root only file, and a guard runs before the application and the web server start that refuses to serve on any empty, unrotated or published default value. Uploaded documents are treated as private data: the upload directory is not world readable, the web server will not serve it directly, and every download requires a valid session. PostgreSQL and the application server listen on loopback only. The complete corresponding source ships on the image with its checksum and the licence, and every deployment is fully patched with unattended security updates enabled, a paired deploy guide and 24/7 cloudimg support.
Real screenshots taken while testing this image against its deployment guide.