SaaS built in public
Small SaaS products built and shared step by step: technical choices, mistakes, iterations.
Build in Public · SaaS · AI Engineering
I study Computer Engineering and turn warehouse, production and everyday work problems into software prototypes, automations and connected systems.

What I Build
Three areas, three different ways of solving problems with code.
Small SaaS products built and shared step by step: technical choices, mistakes, iterations.
Simple tools for warehouse, production, QR and tracking — software that removes manual steps.
Arduino, ESP32 and embedded systems: code that talks to sensors and problems outside the screen.
How I Work
Fewer claims, more practice: I'm learning seriously by building in public.
I do not use complexity to impress. I remove it until the project breathes better.
I'd rather show real progress and prototypes than call myself an expert in things I'm still learning.
I choose tools I understand and can maintain. I add complexity only when it's actually needed.
Where software, automation and physical systems meet: warehouse, production, small daily inefficiencies.
Selected Projects
A few projects, chosen carefully: product, automation, real systems.
I'd rather show a few real projects than a portfolio full of disconnected experiments.
SaaS · automation · AI/LLM tooling · operational software
Technical Focus
The areas I'm using and consolidating in real projects — no stack flexing.
Backend apps with Flask and Quart, plus simple, maintainable HTML/CSS interfaces
C, systems fundamentals, data structures, application logic, disciplined code reading
AI/LLM tooling, API automations, small agents, assisted workflows
Arduino, ESP32, Raspberry Pi, sensors, QR workflows, basic embedded prototypes
Let's talk
Small SaaS, a real operational problem, automation or AI — send me a message.