Proxmox VE as the primary hypervisor. Running KVM virtual machines and LXC containers — services are isolated, resources allocated deliberately, and nothing runs as a mystery appliance.

• KVM VMs and LXC containers, isolated per service
• Dedicated storage per VM/service
• 3-node HA configuration
• CPU/RAM allocation tuned per actual workload
• Everything rebuildable from config + backup snapshot

Dedicated PBS instance for all VMs and containers. Not just "it saves stuff" — the backup strategy is the part that matters.

• 3-2-1 enforced: 3 copies  •  2 storage types  •  1 offsite
• Snapshot-based backups with chunk-level deduplication
• Scheduled automated jobs — no manual steps, no exceptions
• Offsite replication to 2 separate physical locations
• Sync is not a backup. Recovery is tested, not assumed.

• PiHole for DNS resolution, local overrides, and ad/tracker blocking
• Solved: reliable remote access despite ISP and router limitations
• Services reachable externally without unnecessary exposure
• Familiar with the gap between "it connects" and "it stays connected"

Systems here are modular, rebuildable, and fully understood. Nothing runs because it seems to work. If it runs here, I can explain exactly how and why. No magic. No black boxes.

• This town ain't even big enough for one of us
• Starship
• Solitorium
• Think
• Marching Orders

Spotify
YouTube
YouTube Music
Apple Music

→ Full discography

• Sensors: Arduino DHT22 (serial)  |  Raspberry Pi GPIO DHT22
• Relays: 4-channel serial modules  |  FTDI BitBang via USB adapter (up to 8 relays)
• COM: Windows/Linux COM port  |  native Raspberry Pi GPIO
• Platforms: Windows x86/x64  |  Linux  |  Raspberry Pi ARM

• Polling model: probes check in at configurable intervals
• REST API for remote monitoring and setpoint control
• SQLite for persistent temperature history and state
• JSON configuration — fully configurable, nothing hardcoded
• Emergency heat logic: automatically activates backup heat when outdoor temps drop below a configurable threshold — a heat pump alone isn't enough in extreme cold
• HVAC modes: Heat  •  Cool  •  Auto  •  Fan-Only

Cross-platform app (Android, Windows, Linux, Web) built alongside the server. Queries the REST API — shows live temps, lets you adjust setpoints and switch modes remotely.

Self-hosted mail used as an actual daily driver — not a demo, not "mostly working." Running your own mail server is fragile and annoying. I do it because I want control and I've accepted the tradeoff.

• MX, SPF, DKIM, DMARC — configured and actively maintained
• Active deliverability management (yes, including the blacklist problem)
• Zero dependency on Google or Microsoft for personal mail

Full SSL lifecycle is automated: certs renew and deploy without touching anything manually. Nothing has ever gone down here because someone forgot a renewal date.

Nextcloud for file sync across all devices — replaces OneDrive and Google Drive. Immich for photo management and backup. Both self-hosted, no cloud dependency.

Self-hosted AI stack: TTS generation and multiple task-specific agents. Local-first — nothing leaves the network, no cloud dependency for AI workflows. Practical use, not just spinning up demos.

• Text-to-speech generation (local, offline)
• Multiple agents scoped to different task types
• No data leaves the LAN