In a companion post I covered the infrastructure and orchestration layer of my homelab. This post is the full service catalog: everything that actually runs on top of that infrastructure.
Productivity & Data
| Service |
What it does |
| Nextcloud |
File sync and collaboration |
| Paperless |
Document management with OCR |
| Grocy |
Grocery and household tracking |
| Actual |
Budget tracking |
| Monica |
Personal CRM |
| NocoDB |
Database web UI (Airtable alternative) |
| n8n |
Workflow automation |
| Service |
What it does |
| Immich (2 instances) |
Photo management (Google Photos alternative) |
| Jellyfin |
Media streaming server |
| Kavita |
Ebook and manga reader |
| Prowlarr |
Indexer management |
| Strava Stats |
Fitness statistics dashboard |
Home Automation & Security
| Service |
What it does |
| Home Assistant |
Home automation hub |
| Frigate |
NVR with AI object detection (details) |
| ESPHome |
IoT firmware compiler for custom sensors |
Communication
| Service |
What it does |
| Matrix |
Self-hosted messaging (Synapse) |
| TT-RSS |
RSS reader |
AI & Compute
| Service |
What it does |
| Ollama |
LLM inference on Intel Arc B580 |
| llama.cpp |
Vision model for Frigate scene descriptions |
| MCP Server |
Obsidian vault API for AI assistants |
Infrastructure
| Service |
What it does |
| Komodo |
Deployment orchestration (details) |
| Gitea |
Self-hosted Git |
| Traefik |
Reverse proxy with auto TLS |
| Authelia |
Single sign-on + two-factor authentication |
| Technitium DNS (x2) |
Internal DNS zones (redundant) |
| Unbound |
Recursive DNS resolver (on OPNsense) |
| OPNsense |
Firewall, router, VPN |
| Omada Controller |
WiFi access point management |
| Dockge |
Docker Compose UI |
Monitoring & Observability
| Service |
What it does |
| Prometheus |
Metrics collection |
| Grafana |
Dashboards and visualization |
| Uptime Kuma |
Service uptime monitoring |
| cAdvisor (x2) |
Container resource metrics |
| NetAlertX |
Network device monitoring |
| LibreSpeed |
LAN speed testing |
| MySpeed |
Internet speed tracking over time |
| ntfy |
Push notifications |
| Chrony + GPS |
Stratum 1 NTP time source |
Backup & Sync
| Service |
What it does |
| Proxmox Backup Server |
VM and container backups |
| Resilio Sync (x2) |
Cross-site file synchronization |
| Storj |
Decentralized storage node |
Security & Access
| Service |
What it does |
| Vaultwarden |
Bitwarden-compatible password manager |
| Guacamole |
Browser-based remote desktop |
| WireGuard |
VPN (on OPNsense) |
Web & Analytics
| Service |
What it does |
| Matomo |
Privacy-respecting web analytics |
| Whoogle |
Private Google search proxy |
Why self-host all of this?
The obvious question is: why not just use cloud services? A few reasons:
Data sovereignty. My photos, documents, passwords, and communications stay on hardware I control. No third party is mining my data or training models on it.
No subscriptions. The total recurring cost is electricity. No monthly fees for photo storage, file sync, password management, or any of the other services that cloud providers love to charge for.
Reliability. My services don’t go down when someone else’s cloud has an outage. They also don’t get discontinued, acquired, or enshittified.
Learning. Running this infrastructure teaches you more about networking, Linux, containers, storage, and monitoring than any course ever could.
The trade-off is maintenance time. But with proper orchestration (see the Komodo post), that time is minimal. Most days, everything just runs.
