I'm a student working my way toward AI infrastructure and platform engineering — the systems that sit between raw hardware and the software running on top of it — and cybersecurity, along with whatever else catches my interest.
I don't learn well from pre-packaged tutorials. I'd rather build something from scratch and figure out why it doesn't work the first time — that's usually where the real understanding is. Right now that means working through networking, Linux, security and containers, writing small hand-coded tools along the way to make each concept concrete instead of just reading about it.
Sites like this one and subnetlab.dev are just the visible front end of that — what actually interests me is the infrastructure running underneath them: the servers, the networking, the deployment pipeline keeping them online. Slowly taking full ownership of that stack is the real goal.
Progress & write-ups on GitHub →
Small, self-directed tools — mostly standard-library-only Python, built to learn how something actually works rather than to pad a portfolio. Each one below is real: on GitHub, most already shipped and run against my own network, not a tutorial exercise.
Public documentation repo for my homelab: write-ups, network diagrams and sanitised configs.
view repo →Multi-service TCP honeypot. Poses as SSH, HTTP or FTP with a fake service banner and logs every connection thread-safely. Standard library only.
view repo →TCP port scanner and network monitor, command line. Standard library only, argparse-driven interface with an install script.
view repo →Threaded download-speed CLI. Standard library only, class-based, multiple concurrent streams.
view repo →Logs CPU, RAM and disk usage to a CSV file for later review.
view repo →Coming soon.
view repo →Hardware and software actually running everything above. A few AWS instances behind Cloudflare pick up where the rack leaves off — this site and subnetlab.dev live there, not on the R630.
| Servers | Dell PowerEdge R630 and an old laptop, both running Proxmox |
| Hypervisor | Proxmox VE, ZFS storage |
| Cluster | Deliberately not clustered — a 2-node cluster would put quorum in front of the gateway |
| Cloud | A few AWS instances behind Cloudflare — this site and subnetlab.dev |
| Firewall | OPNsense, running as a VM on the R630 |
| Remote access | WireGuard, road-warrior config |
| VMs | debian-lab (headless test box), db01 (MariaDB), and hermesVM running Hermes Agent — always-on, so I can connect to it and kick off automations anytime |
| Daily driver | Arch Linux (Omarchy), Hyprland |