
AionHRMS customer with factory and office staff in Sahibabad, Ghaziabad.
Fit24 Fitness
Gym equipment manufacturer · Sahibabad, Ghaziabad (Delhi NCR)
Biometric machines, installation, online attendance software and shift-wise payroll — one system, one quote, through dealers across India. Built on the attendance platform behind 1,000+ locations, and it runs on the eSSL, ZKTeco and Realtime terminals you already own.
San Ramon, California · Noida, India
End to end
Most biometric purchases are three vendors pointing at each other: a hardware dealer, a software company and whoever does payroll. Here it is one chain with one party answerable at every link.
A fingerprint, face or RFID terminal supplied by an authorised dealer near you — or the eSSL, ZKTeco or Realtime machine already on your wall, repointed instead of replaced.
Choosing a machineMounting, wiring, power and network are handled by a local dealer under the visit terms written into your quote.
Our dealer networkThe terminal pushes each punch to AionHRMS. Create employee profiles in the browser, use model-compatible enrolment workflows, control access, and read the register from anywhere.
The softwareThe same punches compute the salary: per-employee shifts, grace periods, late penalties, paid leave and advances — a figure, not an export.
Attendance to salaryOne quote and one responsible dealer for the hardware, with the software engineered and supported by AIONDATA's team in Noida. No vendor triangle when something breaks.
Talk to usSolutions
Attendance, access, payroll and the machines themselves — plus the API that lets the rest of your stack use all of it. One platform, one register, one accountable vendor.
Punches from confirmed eSSL, ZKTeco and Realtime models in one live browser register.
ExploreFingerprint, face and RFID terminals supplied and installed through local dealers.
ExploreThe same terminal guards the door: block, unblock and release remotely, denied attempts logged.
ExploreShifts, grace periods, late penalties, paid leave and advances — salary computed, not exported.
ExploreA live scoped API for your ERP, CRM and BI — with an MCP server for AI agents in development.
ExploreEvery branch, plant and campus in one register, with per-site administrators.
Explore2
push protocols covering eSSL, ZKTeco and Realtime terminals
4
verification methods — face, finger, RFID card, PIN
2
shifts per employee, each with its own salary
1
register across every branch and confirmed device
Vendor-independent
Hardware gets bought over years, from whichever dealer was nearest. Manufacturer clouds treat a mixed estate as unsupported. We treat it as the normal case.
iClock / ADMS
eSSL, ZKTeco and other standard ADMS terminals
Realtime
Realtime Biometrics native protocol
Attendance
Supported iClock/ADMS terminals from eSSL, ZKTeco and other vendors, plus supported Realtime terminals using its native protocol, can report into the same attendance register. Compatibility is confirmed by exact model, protocol and firmware before deployment.
Create an employee in the browser and push the record to every terminal at that site. No keypad entry at the machine.
Employee profiles can be pushed from the browser. Biometric reuse depends on format: compatible iClock templates can be re-pushed to compatible iClock terminals, TIMY face photos sync only within TIMY, and Realtime devices require device-side biometric enrolment. The exact workflow is confirmed per model and firmware.
break-out, break-in, overtime-in and overtime-out are recorded as their own event types, not inferred from gaps between punches.
Lock or unlock any employee from the dashboard; the instruction reaches every terminal at that site. Denied attempts are recorded. Doors can be released remotely.
Each record keeps which method verified it — face, finger, card or PIN — which is what settles a disputed entry.
Payroll
Most attendance products stop at a report and leave you to re-key it into a spreadsheet. The punch that opened the gate is the same punch that decides the salary — no export, no reconciliation, no second version of the truth.
Each person has their own duty times. Punches are bucketed to the correct shift automatically, and a double-shift employee can carry a separate salary for each shift.
A configurable grace window decides what counts as late. Late marking is disabled entirely for staff with no saved duty time, so nobody is penalised against a default they never agreed to.
Set how many lates trigger a penalty, and whether the penalty is a flat fine or a fraction of a shift's pay. Below the threshold, nothing is deducted.
Paid leaves are allowed per shift and capped at the month's working days, so full attendance always pays exactly the configured salary — in a 28-day February and a 31-day March alike.
Gross is derived from shift units present, then late deductions are applied, giving a calculated amount per employee per month. The breakdown is itemised rather than a single number.
Record a salary advance, see the outstanding balance, and settle it against a future payment. The advance is booked to expenses at the same time.
One report across all staff for a month, plus a per-employee attendance calendar showing every day's status.
Once a company switches them on, payroll splits basic salary, works out employee and employer PF (wage ceiling applied by default) and new-regime TDS, and shows both on the payslip. Returns are not filed by the software, and ESI is not computed.
Working a weekly off or a holiday can be claimed back as a comp-off day, once the company switches comp-off on. Weekly offs, holidays and leave quotas can follow the company, a department or one employee.
In practice
Feature lists all read the same. Here is what actually happens on the days that test an attendance system.
The dealer mounts the terminal and points it at our server from its own menu. You import the staff list in the browser and push it to the device. Enrolment runs at the gate; by evening the register is live.
Face and fingerprint matching happens on the terminal; throughput depends on the selected model, firmware and entrance conditions. HR watches accepted punches land in the register from a browser, at the site or three cities away.
HR blocks the employee from the dashboard. Every terminal at the site gets the instruction — by the time the paperwork is filed, the door no longer opens for them. Their attendance history stays intact.
Punches are already bucketed to each person's shifts, grace periods applied, late penalties counted. Payroll is a computed figure per employee with paid leave and advances settled — reviewed, not rebuilt.
The officer asks for March. You produce the daily register in the browser — every entry carrying its terminal, timestamp and verification method. The conversation is about facts, not about the software.
The dealer swaps the unit; you register the replacement and push the employee list. Compatible iClock enrolment data may be reusable on a compatible replacement; other formats, including Realtime biometrics, can require device-side re-enrolment. Confirm this before selecting the replacement.
Clients
From factory staff to office and clinic teams, meet some of the businesses using our platform.


Washuvi

AionHRMS customer with factory and office staff in Sahibabad, Ghaziabad.
Fit24 Fitness
Gym equipment manufacturer · Sahibabad, Ghaziabad (Delhi NCR)

AIONDATA's gym-management product uses the same underlying attendance platform.
AdviceFit
Gym management platform · 1,000+ gyms & studios across India
AdviceFit is an AIONDATA product — AionHRMS runs on the platform proven there.

AutoYU's website credits AionHRMS for its team attendance.
Feedback summary
AutoYU highlighted employee attendance, leave management and geofencing as features its team particularly liked.
Auto YU
Pankaj Gupta · CEO
Car electronics & accessories · e-commerce, India
An AionHRMS customer in investor relations and financial advisory.

An AionHRMS customer operating hair restoration clinics in Delhi and Jaipur.
Reliability
"Reliable" is an adjective every vendor uses, so here it is as mechanisms instead — what actually happens when the internet drops, a machine dies or somebody disputes a late mark.
Verification happens on the terminal itself. During a network interruption, a supported device can keep matching locally and buffer punches for upload when connectivity returns. A power cut still requires backup power for the terminal and network equipment.
Employee profiles and supported enrolment payloads are held centrally. Compatible iClock templates can be restored to compatible iClock devices; other replacements can require biometric re-enrolment. The model-specific recovery plan is confirmed before rollout.
The classic failure of Indian attendance systems is the accountant's desktop dying with the history and enrolments on it. Here there is no desktop software and no local database — nothing at your site holds the only copy of anything.
Each record keeps its timestamp, its terminal and the method that verified it — face, finger, card or PIN. Nothing is silently rounded or corrected, which is what settles a disputed late mark.
The engine underneath has processed attendance continuously for over ten years across 1,000+ locations — through festival-season load, monsoon outages and every firmware quirk the Indian market ships.
Attendance and templates are stored on infrastructure in India, run by the company that writes the software — not resold through a chain of white labels.
Scale figures are for AIONDATA's attendance platform — the same engine, database and device protocols that power AionHRMS — accumulated across AIONDATA products including AdviceFit since the platform first went live.
Security
Employees hear "fingerprint database" and imagine the worst. Here is the actual design — precise enough to show the staff who ask.
Fingerprint devices use mathematical templates. Some supported face-terminal workflows also use a face or profile photo for enrolment and cross-device sync. Neither is included in ordinary attendance exports or the partner API.
By default attendance and templates live on infrastructure in India (Europe for EU/UK customers where compliance requires it), run by the company that writes the software.
Role-based access for people; API keys scoped read/write, stored only as SHA-256 hashes, rate-limited and fully logged.
No Aadhaar data is ever touched, and your register is processed to run your service — never sold, shared or mined.
Open by design
The console you see is a client of the same backend you can integrate with. Scoped, rate-limited keys pull attendance into the systems where it is used — and push actions back: block a leaver from your HR system, enrol from your onboarding flow, feed the month straight into your payroll journal.
Partner API — live
People, attendance and payments scopes; keys hashed, quota'd and fully logged.
ERP, CRM & BI sync
Pull by date range on your schedule; write back the actions your systems own.
MCP for AI agents — in development
Agents will query attendance and act within scoped permissions. Early access is open.
# pull yesterday's attendance, org-wide
GET /api/v1/attendance?from=2026-08-24&to=2026-08-24
Authorization: Bearer af_live_9f3c21ab_•••
# a punch, as your systems see it
{
"person": { "code": "EMP-0412", "name": "R. Sharma" },
"time": "2026-08-24T09:02:11+05:30",
"terminal": "Gate 1 · eSSL", "method": "face"
}
# leaver processed in your HRMS? close the door
POST /api/v1/members/EMP-0412/block
A plant gate, a school staff room and a three-branch office have genuinely different attendance problems. Each has its own page.
Gate attendance, shifts and contract labour in muster-roll shape.
Learn moreIn/out, breaks, overtime and late marks across branches.
Learn moreTeaching and support staff registers across campuses.
Learn moreRound-the-clock rosters and double-shift staff.
Learn moreSite-wise labour attendance with high turnover.
Learn moreStore-level attendance for distributed teams.
Learn moreCredentials
AionHRMS is built by AIONDATA — an engineering company working with healthcare, insurance, financial services and government clients across three countries, with its headquarters in California and its engineering office in India.
Quality management system certification held by AIONDATA, the company behind AionHRMS.
Capability Maturity Model Integration appraised at Level 3 — a defined, documented engineering process rather than an ad-hoc one.
Controls prepared for SOC 2 Type II, alongside GDPR and HIPAA readiness. Stated as readiness — not as an issued attestation.
Member of NVIDIA's Inception programme for companies building on accelerated computing.
Certifications and programme memberships listed above are held by AIONDATA Private Limited. SOC 2 Type II, GDPR and HIPAA are stated as readiness rather than issued attestations.
Stated here rather than discovered three weeks into a rollout.
Tell us what is on your wall — or that nothing is yet — and we will put biometric attendance and the payroll behind it live, through a dealer near you.