ProjectsGasendra HRIS2023 — 2025
Gasendra HRIS

Gasendra HRIS

Most HR software assumes everyone sits at a desk. Gasendra puts the employee side on a phone — clock in, file cuti or overtime, check your own payslip — and leaves payroll, tax and administration to the web portal, both reading the same records so the two never disagree.

What it does

  • Employee Android app for attendance and requests, alongside the HR web portal.
  • Time off and overtime with approval paths, feeding attendance records directly.
  • Payroll, income tax and payslips run from the approved attendance data.
  • Employee records, structure and roles administered from one portal.
  • One API serving both surfaces, so mobile and web never drift apart.
  • Part of a 35% cut in system response time across the Krida product line.

How it fits together

  1. Step 1EmployeeClocks in and files requests from the app
  2. Step 2ApprovalHR reviews cuti, izin and overtime
  3. Step 3PayrollRun against approved records
  4. Step 4PayslipTax applied, slip published to the employee

Diagrams

How the product behaves, and how the pieces behind it talk to each other.

Business flow
Business flow diagram for Gasendra HRIS
System flow
System flow diagram for Gasendra HRIS

Stack

Services
PythonBottleMicroservices
Mobile
Flutter
Web
Server-rendered web app
Data
Relational database

Worth noting

  • Mobile clients age slowly: the API has to stay backward compatible far longer than a web app would need.
  • Both surfaces read the same records, so HR and the employee never see different numbers.
Generating0%