SaaS & AIPrimary engineer · Cloudpacer

Cloudpacer HRMS

One HR platform in place of spreadsheets: attendance, leave, payroll and reviews, with 240+ test files gating every deploy.

Built by Talha Saleem

100+

data models

220+

API routes

240+

test files

system architecture
SYSTEM ARCHITECTUREdata flowconfig / CIOFFICE LANNEXT.JS 16 · APP ROUTERDATA & DELIVERYCI / CDpushpulldeployBiometric devicesZKTeco terminalsLAN agentpulls punchesPeople & HRrole-based accessADMS endpointdevice pushAPI routes220+ · NextAuth RBACWeb app80+ pagesPayroll engineidempotent pay runsnode-cron jobsmonthly runs · syncsPunch logappend-onlyPostgreSQLPrisma · 100+ modelsSlack · Web PushnotificationsExcel / PDFfinance exportsGitHub Actions240+ test files gateAWSblue-green via SSM

01The problem

Cloudpacer ran HR across spreadsheets and separate tools. Attendance was exported from biometric devices, payroll was rebuilt by hand every month, and leave, reviews and helpdesk requests lived somewhere else. None of it was connected or auditable.

02My contribution

Designed and built the complete HRMS as primary engineer (430+ of 475 commits) on Next.js, Prisma and PostgreSQL. Attendance flows in from biometric devices into an append-only punch log, the payroll engine reproduces the finance team's salary sheet, and module-level permissions cover every role from Employee to Super Admin.

  • Employee records, attendance and shifts, leave, overtime, payroll, performance reviews, training, letter and asset requests, announcements and audit logs.
  • Biometric devices push punches to an ADMS endpoint or are pulled by a LAN agent; raw punches are never overwritten.
  • Payroll matches the finance team's sheet for tax withholding and day-rate rules, and marking a run as paid is idempotent.
  • Slack and web-push notifications, Excel and PDF exports for finance.
  • Blue-green releases to AWS via SSM, gated by unit, integration and end-to-end tests.

03Outcome

The whole employee lifecycle in one system: 100+ data models, 220+ API routes and 80+ pages. 240+ test files, including integration suites against a real Postgres, gate every deploy, and CI ships blue-green releases to AWS.

04Product screens

Attendance analytics across the organisation, fed by the biometric devices
Attendance analytics across the organisation, fed by the biometric devices
Role permissions: every module switched on or off per role, with defaults and approval rules
Role permissions: every module switched on or off per role, with defaults and approval rules
Admin settings: payroll rules, leave types, attendance sync, integrations and the audit log
Admin settings: payroll rules, leave types, attendance sync, integrations and the audit log
A built-in, role-aware user guide covering 56 screens
A built-in, role-aware user guide covering 56 screens

05Engineering note

Payroll is only as trustworthy as its inputs. Attendance devices go offline and re-send punches, so every raw punch is kept in an append-only log and attendance is derived from it. A rule can be fixed and a whole month of payroll recomputed without losing the source of truth.

06Tech stack

  • Next.js 16
  • TypeScript
  • Prisma
  • PostgreSQL
  • NextAuth
  • node-cron
  • Vitest
  • GitHub Actions
  • AWS
  • ZKTeco ADMS
Talha Saleem

Built by Talha Saleem

Want something like this built for you?

Let's Work TogetherWhatsApp

Next project

CloudPacer Knowledge Base

An internal knowledge base and lead CRM that finds the agency's most relevant past work for each job post and drafts a grounded proposal with Claude.