Systems that keep working when nobody is watching

Four systems, explained from the inside

Not screenshots with adjectives: what the problem was, which decisions it forced and what the result looks like.

• Embedded systems Live video from vessels that lose their link — cameras on board, a satellite link that drops several times a day, and video in a browser on shore. With an animated diagram of the signal's path.
• Own product Define a field and the form is already there — a platform where you declare modules and fields from the interface and a generic engine renders, validates and stores. Open demo.
• Custom system Twenty modules around the daily schedule — a therapy centre: patients, sessions, specialists, electronic invoices and staff.
• Field operations Who is on board right now — technicians clocking in with their position, work orders closed in the field and man-hours that add up on their own.

Demos you can open

Four systems of mine running on Google Cloud Run. They sleep when nobody is using them, so the first load after a while takes a few seconds. Their interfaces are in Spanish.

• HR system · NestJS · Prisma · PostgreSQL · ReactSysRRHH — sign in as admin@demo.local / Demo1234!
• No-code platform · Hono · Drizzle · PostgreSQLKUIDY-CORE — sign in as owner@kuidy.demo / Demo1234!
• Technical documentation API · Java 21 · Spring BootTechDocAPI — no sign-in, browse it from Swagger
• Reactive financial API · Java 21 · WebFlux · R2DBCFinancial API — no sign-in, the home page carries ready-made codes

What I am good at

Systems that live far from the office and cannot lose data: devices in the field, links that drop, queues that hold what could not be sent. Management systems that survive daily use, with the boring parts done properly — permissions, valid invoices, figures that reconcile. And interfaces for looking at live data without the screen turning into a Christmas tree.