The Problem
Learning infrastructure requires somewhere real to operate it. Cloud-only experiments can hide the relationships between compute, storage, networks, identity, application state, and recovery.
The Build
The lab combines virtualized compute, dedicated service hosts, containerized applications, network storage, private AI services, monitoring workflows, and a reverse-proxy layer. It supports both practical household services and long-running technical experiments.
Architecture
A deliberately simplified public view. Operational addresses, credentials, firewall rules, and recovery details are excluded.
Challenges
- Understanding dependencies across many independently evolving services.
- Balancing convenience with deliberate public exposure.
- Keeping shared storage and container permissions predictable.
- Creating documentation that is useful without publishing an attack map.
What I Learned
The most valuable infrastructure skill is not memorizing commands—it is building an accurate model of the system before changing it. Backups also matter only when scope, retention, and restoration are understood.
Current Status
Actively operated and progressively documented. This public case study intentionally omits addresses, hostnames, firewall rules, credentials, and recovery procedures.
Next Step
Continue consolidating service ownership, dependency maps, backup verification, and alerting while tightening access boundaries in planned maintenance windows.
Evidence
Public evidence grows with the project.
Repositories, diagrams, screenshots, and demonstrations are linked only when they are accurate, safe, and ready for public use.
Browse Xander Cyber Lab on GitHub ↗Public safety note: This case study is architectural and educational. Sensitive topology, authentication, credentials, and production configuration remain private.