Self-Host Homebox: Home Inventory Management 2026

TL;DR

Homebox (AGPL 3.0, ~3K GitHub stars, Go/Vue) is a home inventory management system. Catalog everything you own — electronics, furniture, tools, kitchen items — with locations, labels, warranty info, purchase details, and even QR codes for physical labeling. Perfect for insurance claims, moving, decluttering, or just knowing where everything is. Sortly charges $9/month; Homebox is free and keeps your data private.

Key Takeaways

Homebox: AGPL 3.0, ~3K stars, Go/Vue — home inventory management
Locations: Organize by room, closet, drawer, shelf — nested hierarchy
Labels: Flexible tagging — Electronics, Kitchen, Important Docs
QR codes: Generate and print QR labels that link to item details
Warranty tracking: Store purchase date, warranty expiry, receipts
CSV import/export: Bulk import from spreadsheets

Part 1: Docker Setup

# docker-compose.yml
services:
  homebox:
    image: ghcr.io/sysadminsmedia/homebox:latest
    container_name: homebox
    restart: unless-stopped
    ports:
      - "7745:7745"
    volumes:
      - homebox_data:/data
    environment:
      HBOX_LOG_LEVEL: info
      HBOX_LOG_FORMAT: text
      HBOX_WEB_MAX_UPLOAD_SIZE: 10    # MB

volumes:
  homebox_data:

docker compose up -d

Visit http://your-server:7745 → create your account → start cataloging.

Part 2: HTTPS with Caddy

inventory.yourdomain.com {
    reverse_proxy localhost:7745
}

Part 3: Setting Up Locations

Locations represent physical places where items are stored:

Location hierarchy

🏠 Home
  ├── 🛋️ Living Room
  │   ├── TV Stand
  │   └── Bookshelf
  ├── 🍳 Kitchen
  │   ├── Upper Cabinets
  │   ├── Lower Cabinets
  │   └── Pantry
  ├── 🛏️ Bedroom
  │   ├── Closet
  │   └── Nightstand
  ├── 🖥️ Office
  │   ├── Desk
  │   └── Cable Drawer
  └── 🏗️ Garage
      ├── Tool Wall
      ├── Storage Shelf 1
      └── Storage Shelf 2

Create locations:

Locations → + Create Location
Name: Kitchen
Parent: Home (for nested hierarchy)
Description: optional notes

Part 4: Adding Items

Basic item

Items → + Create Item
Fill in:
- Name: MacBook Pro 16"
- Description: M3 Max, 36GB RAM, 1TB SSD
- Location: Office → Desk
- Labels: Electronics, Work
- Quantity: 1

Purchase details

Purchase Details:
  - Purchase From: Apple Store
  - Purchase Price: $3,499
  - Purchase Date: 2025-11-15

Warranty information

Warranty:
  - Warranty Expires: 2028-11-15
  - Warranty Details: AppleCare+ (3 years)
  - Lifetime Warranty: No

Attachments

Upload photos, receipts, manuals:

Photos: Take a picture of the item
Receipts: Upload purchase receipt (PDF or image)
Manuals: Product manual PDFs
Warranty cards: Scanned warranty documents

Part 5: Labels

Labels are flexible tags for cross-cutting categorization:

Suggested label system

Category:    Electronics, Furniture, Kitchen, Tools, Clothing, Books
Priority:    Important, Valuable, Insured
Status:      In Use, Storage, Needs Repair, For Sale, Lent Out
Room:        (use Locations instead for physical placement)

Create labels

Labels → + Create Label
Name: Electronics
Description: optional

Filter by labels

Click any label to filter items — great for:

Insurance claim: Filter by Insured + Valuable to list high-value items
Moving: Filter by Fragile to identify items needing special packing
Maintenance: Filter by Needs Repair to track items needing attention

Part 6: QR Codes

Generate QR labels

Select an item → QR Code tab
Print the QR code
Stick it on the item or its storage bin
Scan with your phone → opens item details directly

Bulk QR labels

Print a sheet of QR codes for multiple items:

Items → Select multiple items
Generate QR Labels
Print on label sheets (Avery-compatible)

Use cases

Stick on storage bins in the garage
Label cable drawers
Tag electronics with serial numbers
Label boxes when moving

Part 7: CSV Import/Export

Import from spreadsheet

Import Name,Import Description,Import Location,Import Labels,Import Quantity,Import Purchase Price,Import Purchase From,Import Purchase Date
MacBook Pro,M3 Max 36GB,Office / Desk,Electronics;Work,1,3499,Apple Store,2025-11-15
Standing Desk,Uplift V2 72x30,Office,Furniture;Work,1,899,Uplift Desk,2024-06-01
KitchenAid Mixer,Professional 600,Kitchen / Counter,Kitchen;Appliance,1,349,Amazon,2023-12-25

Items → Import → CSV → upload → map columns → import.

Export

Items → Export → CSV

Full item database exported as CSV — use for insurance documentation or spreadsheet analysis.

Part 8: Reports and Statistics

Overview dashboard

Total items: Count of all cataloged items
Total value: Sum of all purchase prices
Items by location: Bar chart of item distribution
Items by label: Category breakdown
Warranties expiring soon: Upcoming expirations

Insurance documentation

Export your entire inventory with:

Item name and description
Purchase price and date
Photos and receipts
Serial numbers
Current location

This is invaluable for:

Home insurance claims: Documented proof of ownership
Rental insurance: Required for renter's insurance
Tax purposes: Track depreciable business assets

Maintenance

# Update:
docker compose pull
docker compose up -d

# Backup:
tar -czf homebox-backup-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect homebox_homebox_data --format '{{.Mountpoint}}')

# Logs:
docker compose logs -f homebox

Why Self-Host Homebox?

The case for self-hosting Homebox comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Homebox means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Homebox, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Homebox headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Homebox data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Homebox without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Homebox's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Homebox backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Homebox's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Homebox's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Homebox's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Homebox's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f homebox

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Homebox's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

Confirm the container is running: docker compose ps
Test locally on the server: curl -I http://localhost:PORT
If local access works but external doesn't, check your firewall: ufw status
If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats homebox. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Homebox Updated

Homebox follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Homebox is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See also: Grocy — household management with groceries, recipes, and chores

See all open source productivity tools at OSSAlt.com/categories/productivity.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)