Available for work · Remote · Warsaw

Diego Rueda Galán — Platform Engineer

Self-hosted infrastructure,
thoughtfully integrated with AI.

I build and run resilient digital environments — Infrastructure-as-Code with NixOS, Docker, observability, and MCP tooling that lets engineers ship faster.

24
Services running
46
GitHub repos
99.97%
Uptime · 90d

Featured Projects

LiftCraft — Full-Stack Training Platform with MCP Tool Integration

LiftCraft — Full-Stack Training Platform with MCP Tool Integration

A production-grade training-planning platform built solo — Rails 8 REST API, React 19 + TypeScript (strict), PostgreSQL 17 — designed so every analytics report is reachable by Claude Code (or any MCP client) as a structured agent tool. 45 whitelisted reports in `Analytics::Registry` cover strength, cardio, hypertrophy, load (ACWR, monotony/strain, fitness-fatigue), periodization, compliance, body-composition, and cross-block comparison. 60 models, 41 controllers, 64 services, 13 Pundit policies, 86 migrations, ~66k LOC across backend + frontend. Multi-env Docker Compose (dev, dev2, test; prod scaffolded), git-crypt secrets, Devise + TOTP 2FA, device tokens with auto-revocation. Zero LLM-generated SQL — every report is Ruby code, registry lookup refuses unknown keys.

RailsReactTypeScriptPostgreSQLMCP+2
One repo runs everything — Claude Code from my NixOS dotfiles

One repo runs everything — Claude Code from my NixOS dotfiles

I run my servers, my monitoring, my research and about 30 projects from one folder: my NixOS repo, where every machine I manage is a profile. Claude Code works from there. It edits the Nix files and pushes; a build farm builds every profile, the servers deploy themselves with a check and rollback, and my workstations deploy when I click. It reads alerts and metrics from Prometheus, a daily pipeline matches new CVEs against what runs on my machines, and bigger questions end up in the repo as plans (57 so far), sometimes researched by parallel agents. Each project keeps its own repo and memory; the dotfiles repo holds the registry and the tickets go to one self-hosted Plane. What it may touch is decided by code first (94 allow and 34 deny base rules from one Nix module, a hook in front of every command); a second model audits each step, and I verify its findings before anything ships.

Claude CodeMCPAI IntegrationNixOSAutomation+1
NixOS Infrastructure-as-Code — Set it up once, switch it on anywhere

NixOS Infrastructure-as-Code — Set it up once, switch it on anywhere

Setting up a PC by hand used to cost me most of a day, and again after every reinstall. Now each module (shell, Docker, SSH hardening, games) is written once in a NixOS flake, and each machine turns it on with one line like `dockerEnable = true;`. One repo builds 10 machine profiles: desktops, laptops, a Windows WSL setup, a VPS and a NAS. 219 switches, 204 off by default, and shared code never checks the machine name. Over 3,000 commits since July 2024.

NixOSInfrastructure as CodeNix FlakesReproducible SystemsPlatform Engineering

Experience · 9y total

Where I've worked

DSV (formerly DB Schenker)

Apr 2026 – Present·8mo

DB Schenker

Sep 2019 – Apr 2026·6y 9mo