Open Lab Frame production, Docker, monitoring, Cloudflare Tunnel, and optional Tailscale exit node
In use
My Pi 5 hosts this website using Nginx inside a Docker
container. Cloudflare Tunnel connects it to
openlabframe.com. I also use dashboards to keep an eye
on the Pi, the tunnel, and the website. The monitoring stack helps me monitor these services.
Docker & Nginx
Run the web server that serves Open Lab Frame.
Cloudflare Tunnel
Connects the website to my domain without opening router ports.
Grafana
Shows CPU, memory, storage, network activity, and tunnel health.
Uptime Kuma
Checks website availability and tracks response times.
Website Dashboards
Pi 5 System MonitoringCloudflare Tunnel HealthWebsite UptimeWebsite RequestsWebsite BandwidthWebsite Visitors
Remote access & DNS filtering
Raspberry Pi 3 Model B
Hardware specs
Model
Raspberry Pi 3 Model B Rev 1.2
CPU
Broadcom BCM2837 quad-core Arm Cortex-A53
Memory
1 GB RAM
Network
10/100 Ethernet
Primary role
Pi-hole and Tailscale
Network role
Private DNS filtering and Tailscale subnet/DNS routing
Active
My Pi 3 runs Tailscale and Pi-hole. It provides private
remote access and DNS filtering for devices and networks
that I explicitly configure to use it, rather than forcing
those settings on every household client.
Tailscale
Connects my devices privately so I can access the Pi remotely.
Pi-hole
Filters DNS requests to block domains on my blocklists, including advertising and tracking domains.
Pi-hole Dashboard
Pi-hole DNS Filtering
Virtualization & media server
Lenovo ThinkCentre M70q Gen 5
Hardware specs
Model
Lenovo ThinkCentre M70q Gen 5
CPU
Intel Core i7-14700T — 20 cores / 28 threads
Memory
32 GB RAM
Storage
Samsung 970 EVO Plus 1 TB NVMe (boot / VMs); Samsung OEM 512 GB NVMe (additional datastore)
Graphics
Intel UHD Graphics 770
Network
Integrated Intel Gigabit Ethernet
Hypervisor
Proxmox VE 9.2.2
Active
My Lenovo ThinkCentre M70q Gen 5 replaced the previous HP ProDesk.
It runs my existing Proxmox installation, hosting three Debian VMs
for media, on-demand website development, and homelab management.
This is my current standalone virtualization host, planned to become PVE3.
Proxmox VE
Runs the virtual machines and provides the main virtualization platform for this homelab node.
Jellyfin
Runs inside its own Debian VM. The passed-through UHD 770 and Intel media drivers are verified; an end-to-end Quick Sync playback test is still a separate check.
Open Lab Frame Dev
A separate Debian VM used to develop, build, and test Open Lab Frame before deploying changes to production.
Homelab Management
A dedicated Debian VM running Portainer, Nginx Proxy Manager, RackPeek, and monitoring agents.
Roadmap · not deployed
What's next for the lab
These are plans, not currently running servers or a completed cluster.
The Lenovo stays in production while I build the next stages.
PVE1 · NAS / storageA planned storage and compute system; hardware and storage architecture remain separate planning work.NAS project notes
PVE2 · MINISFORUM MS-A2Planned Ryzen 9 9955HX, 64 GB development, lab, and game-hosting node. Not purchased or deployed.MS-A2 plan
PVE4 · management and monitoringA future mini PC for management and monitoring workloads; the current tools stay on VM102 and the Pi 5.Cluster roadmap
Minecraft · planned VM6 vCPU and 12 GB RAM on the Lenovo first, with a later move to PVE2. No VM has been created yet.Minecraft VM plan