Skip to content
GitHub

Supporting practice / Infrastructure

Built locally.
Learned by operating.

My homelab is the working environment behind personal applications and everyday tools. It is where software meets deployment, service dependencies, monitoring and recovery.

Run the application

Containers and explicit configuration connect the application to its runtime. The work includes deployment and real browser checks, not only a successful build.

Understand the dependencies

Service records describe each component’s purpose and how it connects to the rest of the stack. Private addresses and operational access remain private.

Plan for recovery

Monitoring and backup workflows create evidence to investigate failures. A saved backup is not automatically proof that a restore will work.

Public architecture, private operations

This is a documented service catalog, not a live health feed or an uptime guarantee. Status labels reflect the recorded project state.

See the daily operations case study
Showing 37 of 37 services.

11 records / core

Core infrastructure

The network, hosts, backups, and access layer that keep every private app reachable and recoverable.

9 records / media

Media library

A connected path for requesting, organizing, watching, and tracking films, shows, anime, and photos.

6 records / automation

Automation

Bots, smart-home routines, and small workflows that turn repeated chores into quiet background work.

4 records / monitor

Monitoring & alerts

Health checks, metrics, logs, and alerts that reveal drift before a small problem becomes an outage.

3 records / ai

Local AI

Private model runtimes, chat tools, and voice experiments running on hardware I control.

4 records / personal

Personal Cloud

Files, documents, passwords, and useful daily tools kept in a cloud that remains under my control.