Hi, I'm
Richard Vega
A data analyst who builds things that have to be right — the models, the pipelines that feed them, and the tooling that checks both.
Day to day that means Python and machine learning: cross-validated model selection, classical models benchmarked honestly against LLMs, and time-series pipelines over live market data. I came to it by way of Army intelligence and federal policy research, which is where I learned that the useful half of an analysis is the half somebody can act on.
Outside of work I run a self-hosted platform on my own hardware — a trading system, a home-infrastructure control plane, and the static-analysis tooling that keeps a 1,900-file monorepo honest. This site is part of it: generated inside the platform, then served from an isolated host that holds nothing else.
New here? Start with these
Market is the trading platform and the one with source published. Homelab is the control plane that runs everything else, and Pentest Lab is the isolated security lab. If you would rather just read code, go straight to Code.
Projects
Twelve applications in one monorepo, each deployed on its own and each sharing a single library for the parts every app needs — authentication, database sessions, time-series writes, collector supervision, and one design system.
Trading platform — FastAPI backend, React dashboard, live tick collectors into a time-series store, an options-pricing layer, and a bot engine with pluggable strategies. The backtesting harness is published under Code.
Infrastructure control plane for the whole platform — device auto-discovery, per-unit health pollers, config-as-code for the home-automation stack, and control-plane actions kept behind an explicit arm switch.
Personal budgeting — paycheck forecast against actual withholding, accounts, expenses, recurring bills, and a formula registry so the math is declared in one place rather than scattered across views.
Industry calculator for EVE Online — recursive blueprint bill-of-materials with exact material efficiency and per-job rounding, shared-intermediate batching, and cost-optimal buy-vs-build against live market prices.
Recipe manager over the USDA FoodData Central dataset — calories, macros, vitamins and minerals, meal planning, pantry tracking, and a generated shopping list.
Plant tracker — care schedules, growth and watering logs, and scheduled notifications, with a single owner for each reminder so no plant gets notified about twice.
Chores and to-dos with Tody-style urgency decay, recurring and seasonal tasks, and an order-of-operations planner for work that has to happen in sequence.
Marketplace monitor and bidder across two sources, consolidating multi-search watchlists and burst-polling around listing drops. Dry-run by default behind independent two-key arm switches.
Sensor-node network — probes report channel-agnostic readings and a detector flags rolling z-score deviations as candidate anomalies, with per-node alert status.
Wireless and network security dashboard for an isolated lab, with a server-enforced scope allowlist and the actuator held behind an mTLS relay so it can only ever act inside the lab.
Evidence-backed resume and cover-letter generator — job-posting ingestion, requirement-to-evidence coverage mapping, and a page count that is measured from the rendered document rather than estimated.
ESPHome firmware for a WiFi PWM fan controller driving a spot-cooling hub over hot rack gear, surfaced as a first-class device in the home-automation stack.
Want to read the source?
The pages here describe the work — this is how you read it. The full, browsable source for the published exhibits sits behind a one-time email code. No account to create, no password to choose, and it takes about twenty seconds.
- Open the source browser from the Code page.
- Enter any email address you can receive mail at.
- Cloudflare emails you a six-digit code; type it in.
- That is it — the full file tree, plus a snapshot archive you can download.
The gate is there so the snapshot is not bulk-scraped, not to keep you out. Authentication happens at the network edge before a request ever reaches the server, and the server itself holds no credentials, no database, and no route back into the platform.