self-hosted

Homelab

A self-hosted stack for running services, experimenting with infrastructure, testing security tools, and testing new technologies. This is a work in progress, and the details below are subject to change as I continue to refine my setup.

Hardware

root@sv-docker-01:~# lshw --summary

host	role	specs
sv-docker-01	Primary compute node	Dell PowerEdge T320 · Intel Xeon E5-1410 (8T) @ 3.2GHz · 48GB RAM · Ubuntu 24.04.4 LTS
baller-sleeps	Primary Bot Node	Intel NUC8i7HNK (Hades Canyon) · 32GB RAM · Ubuntu 24.04 LTS

Services

Portainer

Management

Web UI for managing Docker containers, images, and stacks across the homelab.

Homer

Management

Static homepage dashboard with bookmarks to every self-hosted service.

Uptime Kuma

Observability

Self-hosted uptime monitoring and status page for internal services.

NetData

Observability

Per-second system and container performance monitoring.

Dozzle

Observability

Real-time log viewer for all running Docker containers.

NetAlertX

Networking

Scans the LAN and alerts on new or unknown devices joining the network.

DocMost

Documentation

Self-hosted wiki and documentation platform for homelab and project notes.

Excalidraw

Productivity

Self-hosted virtual whiteboard for diagramming and quick sketches.

Haven

Communication

Self-hosted Discord alternative for community chat and voice.

RustDesk

Remote Access

Self-hosted remote desktop server on baller-sleeps, used as a backup remote-access path.

Lockbox Relay

Community Bots

Discord bot on baller-sleeps handling in-character radio messaging for the roleplay community, based on my open source Discord bot.

TCL Event Bot

Community Bots

Discord bot on baller-sleeps for event planning and scheduling within the roleplay community.

Network & Ops Notes

›No dedicated router or firewall appliance — LAN and Wi-Fi coverage run on an Eero mesh system instead.
›Tailscale ties every device into a private tailnet, handling secure remote access without exposing services directly to the internet.
›Backups in progress: Solutions are currently being investigated for backing up the homelab and its services, including container volumes and configuration files. Github is used for version control of configuration files, but a more robust backup solution is needed for the entire homelab.