Questions, answered plainly

HumanR is the people platform for workforces that live where they work — an HRMS that runs the permit, the bed, the shift, the payslip and the ledger from one roster, instead of one workbook.

Within minutes. Request a demo and we email you a personal login to a fully loaded demo company with realistic data — no credit card, no sales call required first.

HumanR was built inside a Maldives-based multi-site operation, but it's built for any operation that looks like that one — distributed sites, cross-border hires, permits with hard expiry dates, payroll split across currencies — wherever in the world it runs.

It chases them. A nightly check walks every passport, visa, work permit, contract and probation and alerts at 90, 60, 30 and 7 days out, then again on the day one lapses — each rung once, so nothing nags. Everything found in one night arrives as a single digest rather than a pile of separate pings: in the bell, by email for whoever wants it there, and as an event into Slack, Teams or your own systems if you've pointed a webhook at them.

We handle it for you. Migration is part of initial setup, not an afterthought: our team's battle-tested importer reads your existing registers, salary sheets and trackers, and you get a validation report showing exactly what was imported, matched and flagged. Typical migrations take days, and you can keep the workbook alive in parallel while the team switches over.

You do. Every list in the system exports to a file, and if you ever leave you leave with your data. See the security page for how access to it is controlled while it's in the system.

The things a distributed operation actually runs on. Attendance comes in from ZKTeco biometric terminals over the iClock/ADMS push protocol. Your existing Excel workbooks are brought across for you during initial setup. Payroll goes out as transfer-ready bank files per currency, and as a balanced GL journal for your finance system — QuickBooks Online is posted to directly over its API, while SUN Systems, SAP, iScala, Microsoft Dynamics NAV and Sage 300 each get an import file in their own format. Beyond payroll, HumanR streams its own events — a run finalizing, an approval decided, a permit about to expire — to Slack, Teams or your own systems over signed webhooks. Your own code can go the other way too: a versioned REST API reads employees, attendance, leave and performance data under a scoped bearer token, and accepts attendance punches from a system that speaks nothing but HTTP. And every list in the system exports to CSV or Excel.

Our cloud runs on AWS in the Asia Pacific (Singapore) region, encrypted in transit and at rest, with a nightly database backup kept off the application server. Or you run HumanR on your own servers — the same build, not a cut-down on-premise edition — and the data never leaves your building. The security page has the full answer, including what we don't have yet.

Every major screen ships with an in-app how-to guide, and a built-in support desk lets your team raise tickets — screenshots attached — without leaving the app. Tickets are answered by the people who built the product.

Because two operations with the same headcount rarely cost the same to run — sites, biometric devices and migration scope all differ. Tell us your headcount and how many sites you run, and you'll get a written quote within one working day. A quote here is a number in an email, not a meeting you have to sit through.

Different category. The global enterprise suites are typically quoted at around $28–38 per employee per month for a full suite, implemented by a third-party firm over six to eighteen months at a one-time fee of roughly the annual subscription again — and most of them have no payroll localization for this part of the world at the end of it. We're a fraction of that, live in weeks, and we run the payroll. Our comparison page for that category lays out both sides properly, including the several things the suite does better than we do.

No. New releases, statutory rule changes and the features we ship inside your tier arrive as part of the subscription. Moving up a tier is the only change that moves the price.

Plans are sized to your active headcount, and the tier decides which modules are switched on. You pick the tier that matches how much of the operation you want on the system — registry only, payroll end to end, or the full distributed operation.

It can be. Migration is a proper process, not a free add-on: we start with a gap analysis of your existing workbook and data, scope what it actually takes to bring across, and quote that separately. Straightforward workbooks are quick and priced accordingly; complex ones the gap analysis surfaces upfront — so the number is known before we start, never a surprise invoice afterwards.

Yes. Tiers map to modules, so moving up is switching things on — your data is already there. Many teams start with Foundation during migration and turn on Payday once the first parallel payroll run checks out.

Please do — that's how we prefer it. Request a demo and you'll get a personal login to a fully loaded demo company within minutes. No credit card, no sales call required.