Skip to content
All work

Web · API · Admin

PeopleFlowHub

Multi-tenant, white-label HR SaaS platform

Built an all-in-one HR SaaS platform combining employee management, payroll, attendance, leave, recruitment, documents and SaaS operations. The platform was designed around tenant-specific configuration and white-label delivery, allowing different businesses to run their own HR environment from the same application.

Role
Full-Stack Developer
Timeline
2024 — Present
Platforms
Web, API, Admin
Status
Shipped

Why it was built

Most HR systems solve individual parts of the employee lifecycle, but the workflows still end up split across different tools. PeopleFlowHub was built as a single multi-tenant platform covering hiring, onboarding, attendance, leave, payroll, documents and offboarding, while also giving businesses the ability to run the system under their own branding.

What went into it

01

Built a multi-tenant payroll engine handling percentage and fixed salary components, bulk payslip generation, termination checks, salary revisions and tenant-specific PDF output.

02

Unified manual, IP-restricted and biometric attendance workflows with automatic late, early and overtime calculations, including ZKTeco synchronization and payroll integration.

03

Built the recruitment workflow from job creation and Kanban stages through custom application questions, interview scheduling, candidate evaluation and one-click conversion into an employee.

04

Built HR document generation for offer, joining, experience and NOC letters and contracts, with merge fields, multilingual templates, PDF/DOC generation and e-signature support.

05

Implemented the SaaS layer around the HR application, including tenant plans, usage limits, payment gateways, coupons, referrals and configurable white-label landing pages.

06

Extended the platform's tenant-scoped permissions and settings so each company could manage its own roles, integrations, storage, email configuration, templates and branding from the application.

Technical decisions

  • 01

    Used shared-database multi-tenancy with a central creatorId() resolution instead of introducing a separate database for every company. Tenant ownership stays explicit across application data while keeping the deployment model relatively simple.

  • 02

    Kept flexible structures such as payroll breakdowns and recruitment questions in JSON where their shape was expected to vary, instead of creating additional relational tables for every variation.

  • 03

    Stored tenant-level configuration in the database rather than relying on environment configuration, allowing companies to change SMTP, storage, integrations, templates and branding without redeploying the application.

  • 04

    Kept payment gateway integrations isolated by provider so each gateway could handle its own callbacks and payment flow without turning one integration into a dependency for all the others.

  • 05

    Chose a pragmatic controller-heavy architecture to move quickly with a small team, accepting that the approach creates refactoring work as the platform grows.

Outcome

The result is a single HR SaaS platform that brings employee management, payroll, attendance, leave, recruitment, documents, permissions and billing into one tenant-aware application. The same underlying system can be configured differently for each company, including its workflows, integrations, storage, templates and branding.

Demo access

Company

Email

company@example.com

Password

••••••••

Built with

LaravelPHPMySQLJavaScriptREST APISpatieGoogle CalendarZoomZKTeco
Available for new work

Have something you need built?

Whether you're starting something new or need help with an existing application, tell me what you're trying to build and where things currently stand.