Skyler
Back to portfolio

Personal project / 2024–2026

Homelab Infrastructure

An evolving homelab and work infrastructure built around clear trust boundaries. A Tailscale mesh connects personal devices, a Proxmox host, and a Raspberry Pi. Public requests enter through Cloudflare and travel over outbound tunnels to the appropriate service, while internal tools remain private. Proxmox runs isolated containers and VM guests; the Pi carries the smaller always-on personal services.

Role

Infrastructure architecture, deployment, and operations

Year

2024–2026

Full stack

9 tools

Interactive logical map

Hover, focus, or select a node
Homelab and work infrastructurePublic requests pass through Cloudflare tunnels while devices and hosts communicate over a private Tailscale mesh.TAILSCALE MESH / PRIVATE ACCESSWORK SERVER / PROXMOXHOME PI / ALWAYS ONWWWPublic visitorDNSDomainCFCloudflare edgePXWork ProxmoxPCWork PCMBMacBookLTLaptopHPHome PCPIRaspberry Pi 5N8Nn8nVWVaultwardenWEBPublic stageVMVM guestsN8Nn8nVWVaultwardenHAHome AssistantMCMinecraft
Public request pathPrivate Tailscale meshHosted service link
Project interface — live capture or reconstruction from the working implementation

Full stack

  • 01Proxmox VE
  • 02LXC
  • 03Virtual machines
  • 04Tailscale
  • 05Cloudflare Tunnel
  • 06Raspberry Pi 5
  • 07n8n
  • 08Vaultwarden
  • 09Home Assistant

01

Built around

  • Public services use outbound Cloudflare tunnels, so the network does not need publicly exposed inbound ports.
  • Tailscale provides one private access plane across work hardware, personal computers, laptops, and the Pi.
  • Work-hosted and personal traffic use distinct service paths while still sharing a legible operating model.

02

If I kept going

  • Add one observability layer for service health, tunnel state, storage, and backup freshness.
  • Move more of the repeatable setup into versioned infrastructure-as-code and documented recovery drills.
Next projectVirtual Gamepad