I'm an infrastructure and systems engineer working in an enterprise ITS department — managing networks at scale, virtualization clusters, and increasingly, AI-augmented ops tooling.

My stack spans hardware → Linux → networks → cloud-native → LLMs, built entirely through hands-on practice.
I believe in owning the full stack: if something breaks, I fix it. If it doesn't exist yet, I build it.

Modular, protocol-aware vulnerability lab environment

Started as an FTP lab (vsftpd + Kali attacker + live pcap capture), evolved into a reusable multi-protocol security lab framework.

• Covers: SSH · HTTP · Databases · SMTP · SMB · DNS · FTP
• Designed for eJPT/CTF practice and protocol-level packet analysis
• Fully containerized, spins up and tears down in seconds

Personal knowledge base and technical writeup site

Built with Docusaurus + Docker, deployed via nginx — a living archive of solutions, lab notes, and Obsidian exports made public.

┌─────────────────────────────────────────────────┐
│  Proxmox Node       │  16GB RAM · Dual NVMe      │
│  ASUS ROG G15       │  RTX 3060 6GB · llama.cpp  │
│  VPS (Cloud)        │  Public-facing services    │
└─────────────────────────────────────────────────┘

• llama.cpp running as a systemd service; ctx-size tuned to ~32K with quantized KV cache on remaining VRAM
• Hugo static site (Congo theme) with GitHub Actions CI/CD pipeline
• Discord webhook alerts via Proxmox Handlebars templating for infra events

• 🎯 Pursuing eJPT certification
• 🧪 Expanding the Security Lab with new protocol modules
• 🏋️ Training calisthenics — working toward the handstand
• 🗣️ Learning Hindi (Duolingo streak intact)

"If you can't fix it, you don't own it."

I prefer systems I understand end-to-end — from the NIC driver to the LLM context window.
Self-hosting isn't just a hobby. It's how I learn what enterprise tools actually do under the hood.