Hello — I'm Lou.

I'm David Alejandro Mireles Llamas — Lou for short. I've been building production systems since before it was fashionable to talk about them, and loust.pro is the umbrella under which I do it: a small systems-architecture firm running real infrastructure for real operators, not a portfolio site with mockups.

The work lives in three layers. Below the surface: a VPS substrate hardened from the bottom up, multi-tenant SaaS cores on Next.js + Astro + TypeScript over PostgreSQL with isolated namespaces, and the open research I index under my public ORCID. Between the surface and the operator: agentic AI infrastructure, network transport hardening under hostile transit, server-side attribution pipelines. Above the surface: the products, dashboards, and showcases you can click through.

Most of what I write runs in Go, Rust, or Python — the languages that earn their operational cost. The runtime choices follow the same rule: Kubernetes when the workload justifies the operator cost, containerized systemd-nspawn when it doesn't, distributed control planes when there's actual coordination to do. Observability is grounded in kernel PSI and copy-on-invalid patterns over native memory pools — these are not aspirations, they are the way the production systems stay debuggable at 3am.

I work at the bridge between creative and technical execution. Creatives, agencies, and tech teams all have different operational grammars; I've spent years learning to translate between them without losing precision. A music video release looks different from a Kubernetes migration, but the operational questions underneath are surprisingly similar: who owns this, what does success look like, what does failure look like, and how do we keep going when it doesn't.

Heritage matters to me. I'm from a fourth-generation family of entrepreneurs in Mérida, Yucatán, and the operational seriousness I bring to infrastructure work is partly inherited — small-business sense plus technical depth, not in opposition but in synthesis. It is the reason I optimize for practical cost, latency, throughput, and reliability rather than performative overengineering.

For most of my career I've worked where the creative and technical sides meet: agencies launching campaigns, production houses shipping media, founders standing up operator-platforms, recruiters asking what makes a hire actually ship. The vocabulary changes every project; the underlying operational questions rarely do.

Conecto creativos, agencias y tech. That sentence is shorthand for the work I do best: translate between a director who knows exactly what they want on screen, an agency lead who knows what fits the budget, and an engineering team that has to ship the thing. Each side operates from a different mental model of the same production.

When I take a brief, I read for the underlying production before I read for the surface. The questions I ask are about ownership, success, failure modes, and the path forward when the first attempt doesn't land — the same questions I ask on an infrastructure engagement, just dressed up differently.