Systems & APIs
Back-end, dashboards and REST APIs — from database modeling to deploy.
I build complete applications: authentication, CRUD, dashboards, reports and REST APIs on relational databases. I model the data, write the business logic and expose secure, well-documented endpoints — from management and scheduling systems to an offline-capable POS, plus Python automations.
Where I add the most value: products that need a reliable back-end and a tailor-made admin panel, integrated with the front-end.
- Node.js
- PHP
- MySQL
- PostgreSQL
- Prisma
- REST APIs
- Full-stack
database, API and UI in one flow
- Offline-first
PWA with service worker and sync
- Auth + RBAC
login, sessions and role-based permissions
Come funziona
- 01
Mapping
I map the current workflow, who uses the system and what can be automated or centralized.
- 02
Modeling
I model the database (Prisma/SQL), business rules, access roles and the API contract — validated with Zod.
- 03
Build
I build the API and the dashboard: authentication, CRUD, reports, uploads, notifications and the integrations the operation needs.
- 04
Ship & operate
Tests, CI (GitHub Actions), deploy with backups and monitoring, and follow-up so it runs smoothly day to day.
Cosa è incluso
Relational database modeling (PostgreSQL/MySQL)
REST API with data validation (Zod)
Login, sessions and role-based permissions
Admin dashboard with full CRUD
Reports, tables and charts
Scheduling, notifications and transactional emails
File and image uploads
PWA that works offline
Automations and scripts (Python)
Tests, CI and deploy (VPS, PM2, Supabase)
Stack I use
Where I've done this
FAQ
Can we start small?
Yes — and it's recommended. We start with an MVP covering the main flow and grow it module by module based on real usage.
Can the system work offline?
When it makes sense, yes. In Sistema UP, for example, the POS keeps selling offline and syncs once the connection is back.
What about data security?
Hashed passwords, secure sessions, validation on every input, role-based permissions and credentials kept out of the code. Backups are part of the deploy plan.