HR and payroll platform built for Bangladeshi companies — payroll with TDS, provident fund and gratuity, attendance, leave, approvals and salary disbursement over bank, BEFTN, bKash and Nagad, in Bangla and English.
Paylio is Serviq's HR and payroll product for Bangladeshi companies: one platform for employees, attendance, leave, approvals, payroll, tax and salary disbursement. I am the founding engineer and have built it end to end — architecture, backend, frontend, deployment and operations. Payroll in Bangladesh is not a generic payroll with a currency swapped in: TDS and Form 108, provident fund, gratuity under the Labour Act, festival bonuses, arrears, and salaries paid over bank, BEFTN, bKash or Nagad all have to come out right on every run, for many companies on one system without one ever seeing another's data.
- Role
- Founding engineer
- Type
- Product · Serviq
- Year
- 2026
- Stack
- Next.js · FastAPI · PostgreSQL · Redis · Dramatiq
- Result
- Early access at mypaylio.com · 2,500+ PRs merged · Bangla & English
(By the numbers)
- pull requests merged since April 2026
- 2,500+
- API routes behind 139 permissions
- ~1,200
- automatic backend tests
- ~4,900
- CPU per request, tested with 10,000 employees
- −36%
Load test on one API core with 10,000 seeded employees and 420,000 attendance records, 0 errors — Nov 2026.
(What I built)
- 01Payroll runs that calculate, review and disburse — TDS, provident fund, gratuity, WPPF, arrears, festival bonuses and off-cycle runs, with payslip PDFs
- 02Salary disbursement over bank transfer, BEFTN, bKash and Nagad from the same approved payroll
- 03Attendance with geofenced check-in, approved devices, shifts, rosters, overtime, regularisation and work-from-home
- 04One approvals inbox across leave, regularisation, work from home, overtime, expenses, travel, loans, assets and comp-off, with delegation and an audit log
- 05Leave policies, balances, encashment and year-end reset configured around the Bangladesh Labour Act
- 06Employee lifecycle — onboarding, documents, change requests, resignation, offboarding and full-and-final settlement
Show 3 moreShow less
- 07Role-based access: 139 permissions, 7 built-in roles and custom roles each company defines for itself
- 08Statutory reports and exports — PF, eTDS, Forms XI and XII — plus an AI assistant, e-signatures and real-time notifications
- 09Bangla and English throughout the employee experience
Process
(Problem → what I did)- 01
Problem
Many companies share one database, so a single missed filter would show one company's salaries to another.
What I did
- Every service method touching company data filters by the caller's organisation, and every action re-checks permissions on the server.
- Layered the backend — router, service, repository — so data access lives in one place that can be reviewed.
- 02
Problem
Payroll has to be exact to the poisha across TDS, provident fund, gratuity and bonuses, and a retried job must never pay anyone twice.
What I did
- Stored all money as integer paisa or Decimal, never floating point.
- Made every background worker idempotent: a stable job ID and an atomic status transition, with scheduled jobs on one Redis-elected leader.
- 03
Problem
Employee NID, bank, TIN and salary data must stay protected and never leak into logs.
What I did
- Encrypted personal data at rest with blind indexes for search, and kept it out of logs, traces and commits.
Show all 5 stepsShow less
- 04
Problem
Around 1,200 routes shipped daily by a small team, without the frontend and backend drifting apart.
What I did
- Generated TypeScript types from the backend's OpenAPI schema, so a changed response breaks the build instead of production.
- Test-first, with about 4,900 backend tests and a local merge gate that runs the full suite before staging.
- 05
Problem
Knowing how far one server goes before a large company signs up, not after.
What I did
- Built a load-test harness with 10,000 seeded employees, profiled the hot paths and cut CPU per request by 36%.
How it's built
The moving parts, from the people using it down to the data.
HR, finance & employees
Next.js app
App Router · Bangla & English
Supabase Auth
sign-in and JWTs
API
FastAPI
router → service → repository · ~1,200 routes · 139 permissions
Background work
4 Dramatiq workers
payroll · exports · notifications · compliance
29 scheduled jobs
one Redis-elected leader
Data
PostgreSQL
~200 tables · PgBouncer · encrypted PII
Redis
broker & locks
S3 storage
documents, exports, payslips
The product
7 screens from the real product. Click any screen to see it full size.
(Shipped)
Paylio is deployed at mypaylio.com and open for early access, with every change going through a staging copy first.
Over 2,500 pull requests have been merged since the codebase started in April 2026. The bank-routing defects found in its payroll data became BD Bank Routing, the open dataset in this portfolio.

