I'm a full-stack developer from São Paulo. I got into tech through IT support: help desk, servers, backups, the company ERP. I kept writing scripts to get rid of the repetitive work, and at some point I was building the systems instead of just keeping them running.

Today I work as an IT analyst at a produce distributor, I'm in my last semester of Computer Science, and on the side I'm building PizzaFlow, a system for pizzerias.

PizzaFlow · LinkedIn · Email · open to freelance and full-time work

PizzaFlow (overview and architecture)
My own product. Customers order from a menu link, no app to install, pay with Pix straight to the store, and can collect stamps on a loyalty card that is just their phone number. Behind the counter, the team runs the cash register, a kitchen screen you drive with the number pad, table orders by QR code and delivery routes that go to the driver's WhatsApp. There are also reports and a customer list that fills itself in. Each store pays a monthly fee, there's no cut per order, and every pizzeria only sees its own data. I do all of it, from the database to the screens.
_{Next.js · TypeScript · PostgreSQL · Drizzle · better-auth · Stripe · Vercel
3,500+ automated tests · 50+ tables · 45+ migrations · 240+ commits since July 2026}

At work
I built the sales app the company uses today, and now I'm on the crate tracker: drivers log every drop-off and pickup with a photo, and we follow the route while they're out.

I also work on a WhatsApp sales platform for produce sellers. Customers order by chatting with a bot that has AI help, and the team handles picking and delivery from an admin panel.
_{TypeScript · Node.js · LLMs}

Most of this code is private, since it's either my product or the company's. One thing I did open up is multi-tenant-rls, a small example of keeping tenants apart with Postgres row-level security, with tests that try to break it. If you want to see more, send me a message and I'll walk you through it.

• Working in support taught me to think about the person using the screen, and about what happens when something breaks in the middle of a busy shift. Most of what I build is used by drivers, warehouse staff and store owners.
• I care a lot about each customer's data staying in its own place. Every query is filtered by account and store, and there are tests that fail if one of them loses that filter.
• I like billing to just work: subscriptions, webhooks that can arrive twice without breaking anything, plan changes nobody has to think about.
• I use Claude every day. I know my stack well and I review what it writes, it just gets me from the first version to production faster.