I build logistics, hospitality and agentic systems — from the route solver to the dashboard.
Off-hours I take things apart: binaries, protocols, and anything that ships without docs.

• better-route — self-hosted route optimization & delivery management. VROOM + OSRM under the hood, no per-driver fees. Also has a mobile client (Flutter) and a landing.
• restai — multi-tenant hospitality system: orders, tables, kitchen and billing for restaurants that share one deployment.
• Reverse engineering — undocumented formats, closed protocols and apps that were never meant to be automated. I keep reverse-skill forked as my routing layer for binary analysis and security research, and yape-sonido came out of poking at an Android app that hardcodes its notification sound.

Core — TypeScript · Next.js · Rust · Python Also ship with — Kotlin (Android) · Dart/Flutter · Elixir Infra — Docker · Cloudflare Workers · PostgreSQL · CI/CD Domain — VROOM · OSRM · multi-tenant architecture · agentic pipelines Reversing — binary analysis · protocol reversing · disassembly

Planning analyst first, engineer second — I tend to start from the operational constraint (a fleet, a kitchen, a shift) and work backwards to the system. That's why most of what I publish is self-hostable and open source instead of another SaaS with a per-seat meter.

The reverse engineering habit feeds the same thing: half of integrating with the real world is figuring out an undocumented format, a closed protocol or an app that was never meant to be automated. yape-sonido started exactly like that.

GitHub stats

_{Reach me through GitHub — issues and discussions on any of my repos are open.}