Overview
A substantial product-engineering system for work-time records, attendance, leave and administration. It separates employee and management experiences from the API and operational infrastructure.
Problem
Fragmented time records, requests and reports create manual work, while a desktop client needs secure sessions and resilience when connectivity is intermittent.
Solution
Layered frontend and backend applications handle roles, tenants, time tracking, leave workflows, reporting and integrations. Desktop provides a dedicated work-tracking endpoint; document OCR is a planned module, not a completed claim.
My role
I worked across the end-to-end product architecture, API contracts, data model and tenant isolation, web/desktop experience, deployment environment and monitoring.
Architecture
Next.js and the desktop application communicate with a NestJS API. PostgreSQL holds domain data, Redis supports sessions and short-lived state, while Docker, Traefik, Prometheus, Grafana and Loki form the operational layer.
Engineering challenges
Important decisions include tenant isolation, authentication, time-record consistency, secure desktop session storage and offline queuing. The last two remain explicitly identified hardening work.
Results and current status
The repository verifies a broad product surface: web, API, desktop, reporting and observability. Development continues; no unverified user-count or business-impact metrics are claimed.