HRMSAvailable

HRMS

EzyHRM runs payroll, attendance, leave, and BPJS for Indonesian small and medium businesses, with a companion mobile app for employee self-service.

Book a Demo Open EzyHRM

At a glance

A complete HRIS for Indonesian SMBs — payroll, attendance, leave, and BPJS.

What it does

Built for the work, end to end

Payroll

Run monthly payroll for Indonesian SMBs with configurable pay components. Confirm BPJS and PPh 21 handling against your own payroll in the review — we will not claim statutory coverage we have not shown you.

Attendance

Employee attendance check-in, with the companion mobile app for on-the-go capture.

Leave Management

Leave requests and approvals routed to managers from the employee self-service app.

Reimbursement

Employees submit reimbursement claims; managers approve from their dashboard.

Payslips

Generated payslips available to employees through self-service.

Manager Approvals

A manager-approval dashboard for attendance, leave, and reimbursement workflows.

How it works

From kick-off to day-to-day

Onboard your team

Add employees and configure pay components, BPJS, and leave policies.

Run HR day-to-day

Staff check in, request leave, and submit reimbursements from the mobile app; managers approve.

Close the month

Run payroll and publish payslips — attendance and leave feed straight in.

How it compares

EzyHRM vs Talenta, Gadjian, and LinovHR

Indonesian HR software is a crowded, mature category, and on the statutory basics EzyHRM is at parity rather than ahead — Talenta, Gadjian, and LinovHR all handle BPJS and Indonesian payroll properly, and any vendor claiming otherwise is selling. The honest difference is commercial and architectural: every mainstream option bills you per employee per month, so your HR bill tracks headcount forever, and each one is a point solution that stops at the edge of HR. EzyHRM is one line of a single Straventa estate — payments, back-office ops, project management, and construction from the same Jakarta team, on one contract, behind one identity plane. Where our data does not support a claim, this table says so.

EzyHRM vs Talenta, Gadjian, and LinovHR
Criterion	EzyHRM (Straventa HRMS)	Talenta by Mekari	Gadjian	LinovHR	Spreadsheets + manual BPJS
Deployment model	Straventa-hosted at ezyhrm.com, built and operated by the team that writes it. On-premise deployment is not claimed as shipped for HRMS — ask in the review rather than assume it.	Cloud SaaS only.	Cloud SaaS only.	Publicly offers a cloud option and an on-premise option.	A file on someone's laptop and a shared drive.
Where employee and payroll data lives	Infrastructure operated by Straventa's Jakarta team. The hosting region and retention terms are put in writing during the review — we will not assert a residency claim we have not contracted.	Mekari's cloud, under their published terms.	Gadjian's cloud, under their published terms.	Their cloud, or your own servers on the on-premise option.	Email attachments, WhatsApp, and personal drives — the least controlled option on this table.
Pricing model	On request. HRMS is not in the published price catalogue on /pricing — that catalogue covers the Payops modules only — so no figure is quoted here rather than an invented one.	Per employee, per month, on published tiered plans.	Per employee, per month, on published tiered plans; attendance is sold as the separate Hadirr product.	Quote-based, scoped by module and headcount.	Free, until the first mis-deducted BPJS line or a late statutory filing.
Indonesian statutory payroll	Monthly payroll runs with configurable pay components. The other vendors in this row have genuine native BPJS and PPh 21 handling; confirm ours against your own payroll before you treat this row as parity.	Built for Indonesian payroll — BPJS and PPh 21 handled natively.	Built for Indonesian payroll — BPJS and PPh 21 calculators are core to the product.	Indonesian payroll including BPJS and PPh 21.	A formula somebody wrote years ago, plus a manual upload to each BPJS portal every month.
Employee self-service mobile app	Yes — a companion mobile app for attendance check-in, leave requests, reimbursement claims, and payslips.	Yes — the Talenta employee mobile app.	Self-service and attendance run through the separate Hadirr app.	Yes — an employee mobile app.	A WhatsApp message to HR, then a wait.
Manager approvals in one place	One manager dashboard covering attendance, leave, and reimbursement approvals — the three things a line manager actually gets asked to sign off.	Approvals in-app across its HR modules.	Approvals in-app; attendance approvals sit in Hadirr.	Approvals in-app across its modules.	Email threads, chat, and printed forms.
Single sign-on with your other systems	Straventa Accounts is the estate's self-hosted OpenID Connect provider — Payops and the Ops platform authenticate against it today, and your own applications join as plain OIDC relying parties. EzyHRM's SSO scope is set per deployment, so confirm it in the review.	Single sign-on within Mekari's own suite; anything outside it is an integration project.	Its own login; sign-on with your other systems is an integration project.	Its own login.	None.
What else the same vendor already runs	One estate, one vendor: the 15-module Payops payments and compliance platform, the Ops back-office engine (helpdesk, SLAs, inbound email), self-hosted project management on Plane, and Interlude for construction sites.	Mekari's own adjacent products — accounting, CRM, and signing.	Gadjian plus Hadirr.	HR modules only.	Nothing — every other system is a separate purchase and a separate export.
Who answers when payroll is due	A Jakarta engineering team that builds the product, on response terms set in your contract.	Vendor support, on the tier you purchased.	Vendor support, on the tier you purchased.	Vendor support, plus your own administrators on the on-premise option.	Whoever built the spreadsheet — if they still work there.

Competitor rows describe each vendor’s publicly documented model at time of writing; confirm current terms with the vendor before making a decision.

How it is priced

Every mainstream Indonesian HRIS bills per employee per month, so hiring raises the invoice for software you already had; EzyHRM is quoted directly, and no number goes on the page that the repo's price catalogue cannot back.

Billing model

On request — HRMS is not in the published price catalogue

src/lib/data/pricing.ts contains no HRMS entry. The catalogue is the Payops modules only — KYC, fraud, AML, POS, marketplace, gateway, reconciliation, plus the eight coming-soon products. Publishing an EzyHRM price would mean inventing one, so the page must say 'on request'.
The pattern that catalogue does establish for the estate: flat monthly tiers for software modules, and 'Contact us' on every on-premise line. The only on-prem figure published anywhere on the site is the Payops Platform Bundle at from Rp 180.000.000/yr — that is a Payops number and must never be presented as an HRMS price.
Competitor contrast is the argument, and it is sourceable: Talenta and Gadjian both publish per-employee, per-month plans, and Gadjian sells attendance as the separate Hadirr product, so the true per-head cost is two line items. LinovHR quotes by module and headcount.
Sell headcount-independence and one contract across the estate — HR, payments, back-office ops, project management, construction from one Jakarta vendor — and let the architecture review produce the number.
Site-wide caveat from pricing.ts: prices are directional and billing is disabled until merchant onboarding completes. HRMS copy must not imply a live subscription checkout or a self-serve price.

See the full price list

Want HRMS for your team?

Bring your rails, controls, and deployment constraints. We will show where the platform fits and where it does not.

Book a Demo Talk to Sales