Building
Focused on two projects that are identical under the hood and very different on the outside: Neuvora, for businesses, and StudyFlow, for students. Same stack, same architecture — different customer.
Agentic OS developer
Advanced AI user · building agentic operating systems already in use at small businesses.
Updated Nov 2026
Focused on two projects that are identical under the hood and very different on the outside: Neuvora, for businesses, and StudyFlow, for students. Same stack, same architecture — different customer.
The problem I keep coming back to: making AI agents — whose outputs are inherently unpredictable — coexist with the traceability and rigor that a database, and every channel connected to it, demand. Around that core: fine-tuning open-source models, running agents inside Supabase Edge Functions, and strategies that let an AOS grow without turning into a chaotic pile of data.
I’d like to go to more events for founders and developers, where I can meet people who share my ambitions and interests.
Know a good one? Tell me about it.
What I run. Two ventures, one architecture. Both private — happy to show them live.
Agentic operating systems for real businesses.
I find businesses and analyze them as a full loop, end to end — from acquiring a customer to selling the product. I automate as much as possible, down to a few human supervision steps, and deliver the result as an application.
The university virtual classroom of the future.
A virtual classroom with AI built in natively. It goes deep on many fronts: handwriting, note-taking, exercise generation, precise progress tracking — and LITS, an agent that works as a personal tutor, reachable from several channels with instant access to all course material: notes, syllabi and exercises.
Small public repos: clone them, read the code, run them.
Regression tests for AI agents.
Change a prompt, a model or a tool and find out what you broke before your users do. Test cases live in a YAML file; every run is compared against a saved baseline, so you see what regressed and what got fixed — with an exit code your CI understands. It checks what the agent does (the tools it calls), not only what it says.
If you’ve made it this far, something caught your eye. Here’s the big picture: how an agentic operating system really works when it’s designed from day one to integrate AI natively.
First, you lay out on paper all the information you’ll handle — down to the least significant field. Separately, you list every process that people or programs do today and that AI can genuinely take over. With that, you can build the database tables and the agents that read from and write to them. That way, no matter how much the database grows or how much time passes, the agents leave a trace of their work, and the AI can understand where the business is heading — its strengths and its weak spots.
That’s why Neuvora and StudyFlow are technically the same thing: same stack, same structure, different customer. Neuvora is for business owners; StudyFlow is for students.
agents ⇄ database ⇄ control panel
Plan first, code second.
No agent ships to production until the traceability of its runs is verified.
Commit, commit, commit — never put off till tomorrow what you can commit today.
What I actually use, not everything I’ve touched.
Python (local agents) · TypeScript / JavaScript (Edge Functions & web) · SQL · R
Closed models via Vercel AI Gateway · open-source models with Ollama (Llama 3 8B, Qwen 8B) · fine-tuning open-source models · multi-agent orchestration · tool calling & MCP · guardrails & run traceability
Claude Code (daily driver) · Codex · Kimi Code · Hermes · OpenClaw · my own agents
PostgreSQL · Supabase · pandas · NumPy · R + Quarto · regression models · process optimization
Supabase Edge Functions · Vercel · Docker · Debian / Linux · systemd · Railway · Git & GitHub
n8n · Telegram bots · scraping · voice with Twilio, Deepgram & ElevenLabs
Next.js · React · HTML, CSS & JavaScript
I’m based in Madrid and study Data Science & Engineering at Universidad Rey Juan Carlos. I’m ambitious and hungry for new professional challenges.
I’m looking for people who want to build and sell — people ready to team up and go all in until the goals are met.
Beyond the technical side, I’d describe myself as honest, loyal to my friends, and serious — but fun when the moment calls for it.
If my work caught your interest and you have a technical profile with something to bring, write to me. I read every message.
I also take on quick, focused freelance work: small businesses or one well-defined idea.