I build tools to solve problems I'm facing, or because something seems interesting enough to apply a concept I'm working through — sometimes both.
Professional background in Java, Spring Boot, and enterprise backend systems at a large bank — containerization, OpenShift/K8s operations, CI/CD automation, and security remediation at compliance scale. Outside of work I run a two-node homelab for end-to-end project ownership: building, shipping, and operating software I actually use. Currently focused on Rust systems programming and local AI infrastructure.
|
Homelab MCP server A Rust workspace that exposes homelab infrastructure (Proxmox, OPNsense) as AI-callable MCP tools — node/cluster status, DHCP leases, and more. Deployed behind Cloudflare Zero Trust
with atomic CI/CD deploy and automatic rollback. Split into
|
Self-hosted local LLM Discord bot A persona-agnostic Discord bot backed by a local Ollama model. Threaded conversations, optional SearXNG web search, and two-tier memory — hot per-thread history in Redis, durable
cross-thread recall via
|
|
Local-first memory library for LLM apps A Rust crate providing persistent memory for LLM applications — SQLite + FTS5 BM25 retrieval, recency-decay scoring, and token-budget-aware context assembly. No network calls, no
async runtime, no cloud dependency. Powers
|
|
Professional
Homelab & Personal
I learn by building. Applying a concept until it becomes a skill is the only path that actually sticks. Most of what's here is that process made visible.
- Rust systems programming — shipping production tooling in the homelab
- Local LLM inference and AI-augmented infrastructure (Ollama, llama.cpp, MCP)
- GPU compute fundamentals (cuda-oxide, Rust + CUDA)
- Security tooling and compliance engineering (professional focus)