Founder at Sequel · Mexicali, MX · AI systems · ticketing infrastructure · Java/Spring + TypeScript

I build production software end to end: backend architecture, frontend, infrastructure, billing, deployment, and the unglamorous parts that keep systems alive after launch.

I'm the founder of Sequel, a software studio in Mexico building AI agents, venue operations software, and developer infrastructure. I was selected in the top 4% of 13,000 applicants at the Anthropic Claude Code Hackathon with Ehrlich.

• AI orchestration — Kiln, a domain-agnostic engine for multi-channel agents, LLM providers, tools, RAG, and safety pipelines.
• Developer infrastructure — Mortar, Java-first query infrastructure, and Vigil, secure JWT authentication for Spring Boot.
• Venue operations — Admit / SHRAD, ticketing and cinema operations software running in production in Mexico.
• AI agent SaaS — Kilvo, a multi-channel agent platform for SMBs built on top of Kiln.

• mortar — Java-first query infrastructure for Spring + PostgreSQL.
• vigil — Secure JWT authentication starter for Spring Boot, with RS256/JWKS, refresh rotation, cookie profiles, and revocation.
• sequel-backend-demo — Public Spring Boot demo for Sequel libraries.
• kiln — Open-source AI orchestration engine.
• kiln-integrations — Official integration adapters for Kiln.
• ehrlich — AI scientific discovery engine from the Claude Code Hackathon.

• Admit has processed 18,600+ tickets and roughly $572K MXN in revenue since October 2025.
• My usual backend stack is Java 21, Spring Boot, PostgreSQL, Gradle, JUnit, Mockito, and Testcontainers.
• My usual frontend stack is React, TypeScript, Vite, Bun, TanStack, Tailwind, and Electron when desktop matters.
• I care about DDD, clean architecture, explicit boundaries, test coverage, and software that can survive real operators.

• Ship the smallest coherent system that can be used by real people.
• Keep architecture boring enough to maintain and strict enough to scale.
• Write tests before calling something done.
• Prefer clear contracts, explicit imports, and code that fails fast.
• Build it, run it, learn from it, then make the next version cleaner.