Homelab Overview

Public-safe view of the compute, storage, network, and service stack behind xdev.lol. Internal hostnames, IP addresses, secrets, and exact routing details are intentionally omitted.

View projects Contact

160physical cores across the blade compute cluster

512 GBRAM across 4 x 128 GB blade memory sets

12 TBraw blade storage from 12 x 1 TB disks

10 Gbitcrosslink fabric between high-throughput nodes

24/7self-hosted apps, tools, and game services

Hardware Stack

Compute Node - Dell PowerEdge R630

CPU: Dual 14-core CPUs, 28 threads each, 56 threads total
Memory: 32 GB DDR4 ECC
Storage: Mixed SSD and HDD storage for VM disks, app data, and test workloads
Hypervisor: Proxmox VE
Guests: Debian, Ubuntu, Windows, app containers, game-service VMs
Role: Reverse proxy support, backend services, frontend apps, Minecraft workloads, automation

Storage Node - IBM Server

CPU: 8-core server platform
Memory: 48 GB DDR3 ECC
Boot: Dual 60 GB SAS drives in RAID1
Data Pool: 3 x 1.8 TB HDD pool with additional HDD cache capacity
OS: TrueNAS CORE with IPMI management
Role: File services, compression, snapshots, backups, and internal data management

Blade Compute Cluster

Layout: 4 blade nodes for dense compute, lab workloads, and future service expansion
CPU: Each blade has dual 20-core CPUs; 160 physical cores total across the cluster
Memory: 4 x 128 GB RAM sets, 512 GB total cluster memory
Storage: 12 x 1 TB disks, 12 TB raw capacity before filesystem, redundancy, or reserved space
Network: 10 Gbit crosslink for high-throughput traffic between compute, storage, and service paths
Role: Large test workloads, VM/container expansion, game infrastructure, build jobs, and internal services

Public Topology

This is the safe public shape of the network. The real topology includes private segmentation, management interfaces, tunnels, and failover paths that are not published.

Internet Edge TLS entry, DNS, reverse proxy, rate limits

Service Network Segmented web, dashboard, API, blade compute, and game workloads

Storage + Backup TrueNAS services, blade disks, snapshots, internal backup paths

Public diagram intentionally removes IP ranges, hostnames, provider details, firewall rules, and management endpoints.

Services and Use Cases

Web AppsPHP, React, APIs, dashboards, static assets, and internal tooling.

Game InfrastructureMinecraft services, proxy routing, plugins, test servers, and automation.

Media and FilesX-Tracks, local file services, snapshots, compression, and backup storage.

MonitoringAvailability checks, log review, service status, and incident troubleshooting.

AutomationScheduled scripts, deployment helpers, cleanup tasks, and operational glue.

Lab TestingSafe experimentation for networking, Linux, Windows, containers, and web stacks.

Blade ComputeDense CPU and RAM capacity for heavier VM, container, build, and game workloads.

Security and Operations

Access Control

Session-hardened login and permission checks for restricted tools.
Live heartbeat checks for account status and administrative lockout.
Total account and IP blocks for abuse, ban evasion, or access-control violations.

Network Safety

TLS reverse proxying with hardened headers where appropriate.
Segmentation between public services, storage, management, and experiments.
10 Gbit crosslink paths are used for internal high-throughput traffic where needed.
Public pages omit sensitive infrastructure details by design.

Current Roadmap

Short Term

Clean UI across all portals, legal pages, public repo views, and dashboard tools.

Reliability

Better health checks, clearer service status, and safer backup visibility.

Documentation

More public-safe writeups for projects without exposing private network details.