Homelab Dashboard
Central overview of network services, hardware, and infrastructure for rlab.uk
System Status: Work In Progress
TODO: Work in progress - remove this when its ready.
The Genesis State is currently being defined. Automation via Ansible and Terraform is in active development. Expect broken links and "under construction" signs.
Introduction
Welcome to my Homelab documentation! This project serves as the Source of Truth for my personal network. While I primarily write this for my own sanity (future Ruben will thank current Ruben), I’m open to feedback and suggestions from the community.
The goal is a fully automated, Infrastructure as Code environment that can be destroyed and rebuilt with a single command.
Stack & Technologies
The following marquee represents the "Hardware and Software DNA" of the lab. This includes our Day 0 bootstrap tools and Day 1 production services.
Infrastructure Topology
The lab is divided into three distinct layers: Physical, Logical (Network), and Service.
1. Physical Layout
This diagram tracks the "bare metal" physical connections in the rack between the compute nodes and networking devices.
2. Network Map
This map outlines the VLAN structure, including the Site-to-Site VPN tunnels (using either WireGuard or NetBird) and the external VPS nodes that handle ingress traffic.
Physical Network
Virtual Network
3. Inventory & Virtualisation
Device Inventory
| Logical Name | Make | Model | Type | CPU | Memory | Storage | OS | Status |
|---|---|---|---|---|---|---|---|---|
R-BM-001 |
HP | Prodesk 400 G5 Mini | Server | i5-9500T | 64GB DDR4 | 258GB SSD | Proxmox | [(active)] |
R-BM-002 |
Minisforum | ms-01 | Server | i9-13900H | 8GB DDR5 | (2x1TB)SSD+(2x4TB)HHD | Proxmox | [(initialised)] |
R-NT-001 |
GLinet | Flint 3 (gl-be9300) | Network | 1GB DDR4 | 8GB | OpenWRT | [(active)] | |
R-BM-003 |
Raspberry Pi | 4 Compute | IoT | K3S | [(Unallocated)] | |||
R-BM-004 |
Raspberry Pi | 3B | IoT | K3S | [(Unallocated)] | |||
R-BM-005 |
Raspberry Pi | 2 | IoT | K3S | [(Unallocated)] | |||
R-NT-004 |
GLinet | Comet (gl-rm1) | Network | CUSTOM | [(active)] | |||
R-NT-003 |
TP-Link | nan | Network | N/a | [(Unallocated)] | |||
R-NT-002 |
MikroTik | hEX refresh | Network | nan | RouterOS | [(active)] |
Device to service Map
| Physical Host | VM Name | Purpose | Services | Service Type | Unnamed: 5 |
|---|---|---|---|---|---|
| R-BM-001 | core-vm-1 | Host critical core services | authentication | #core |
nan |
| nan | nan | nan | traefik | nan | nan |
| nan | nan | nan | beszel | nan | nan |
| R-BM-001 | prod-vm-1 | Stable production services | jellyfin | #media |
nan |
| nan | nan | nan | traefik | nan | nan |
| forgejo, forgejo-runner, code-server, jupyter | #code |
nan | |||
| mkdocs, paperless-ngx | #productivity |
nan | |||
| grafana, prometheus, loki, tempo, alertmanager, netdata | #monitoring |
nan | |||
| R-BM-001 | prod-vm-2 | nan | ollama, openwebui, kokoro-tts | #ai |
nan |
| nan | nan | nan | nan | nan | nan |
| nan | nan | nan | |||
| R-BM-002 | storage-vm | Data storage layer | next cloud | #storage |
nan |
| R-BM-002 | arr-vm | Media management stack | gluetun, qbitorrent, qui, sonarr, radarr, lidarr, prowlarr, bazarr | #media-management |
nan |
| R-BM-001 | test-vm | Non-production testing | koel | #media |
nan |
| gradio, n8n | #ai |
nan | |||
| crafty | #gaming |
nan | |||
| penpot, joplin, Stirling PDF, kiwix | #productivity |
nan | |||
| vaultwarden, frigate | #security |
nan | |||
| duplicati | #backup |
nan | |||
| R-BM-002 | win-vm | Windows applications | #windows |
nan |