Features
What the platform does
A complete HR system for organisations that need their own rules rather than someone else's defaults. Every item below links to the documentation for it, so you can check the detail before you commit.
Getting started
Set the platform up for your organisation, in the order that works.
People
Employee records, org structure and documents.
Attendance and time
Shifts, policies, biometric devices and corrections.
Shifts, including night shifts
Define when work happens, and let the platform handle midnight properly.
Attendance policies
Grace periods, half-day thresholds, late marks and what a missing punch means.
Connecting biometric devices
Three ways to get punches in, including from devices with no internet access.
Attendance corrections
Let people fix a wrong day without giving them the ability to edit attendance.
Leave
Types, policies, balances and approvals.
Leave types and policies
Allocation, accrual, carry forward, and who approves what.
Weekends and holidays inside a leave request
The three counting modes, and why a request sometimes costs more days than expected.
Applying for and approving leave
What employees see, what approvers see, and what happens on approval.
Payroll
Components, structures and pay runs.
Administration
Users, roles, security, audit and billing.
Users, roles and permissions
Give people exactly the access they need, using roles you define.
Approval workflows
Multi-step approvals with conditions, escalation and delegation.
Audit trail and logs
What is recorded, how long it is kept, and how to search it.
Security settings
Password rules, sessions and the controls available to an account owner.
Plans, billing and limits
How pricing works, what counts, and what happens at a limit.
What makes it different
Four decisions that shape everything above.
The rules are yours
Grace periods, half-day thresholds, accrual rates, carry-forward caps and salary formulas are configuration. Changing how your organisation treats a late arrival is a setting, not a support request and not a release.
Every number can be explained
Attendance days, leave costs and payslip lines each carry the working behind them — which rule fired, on which input, producing which result. When someone disputes a figure, the answer is on screen.
Isolation you can describe to an auditor
Each tenant's data is separated at the data-access layer, not by a filter that a developer has to remember to add. A query without an authenticated tenant context fails rather than returning everything.
Nothing is silently discarded
Raw biometric events are kept alongside the attendance computed from them, so a mis-configured device can be remapped and reprocessed. Audit entries are append-only. Terminated employees keep their history.
Try it with your own policies
The trial is a full account, not a sandbox. Configure your real leave rules and see what the engine does with them.