Trust & availability
Clear about the product. Clear about the limits.
Choosing software should not require guessing what happens behind a demo. Here is the current boundary for HRMS.
What the review established
The local review started the core platform with 24 seeded employees and 651 recorded events. It also exercised supporting AI, geolocation and document services. This is evidence of local evaluation, not a production customer result.
What the demo means
For evaluation with sample data. Production authentication and independent payroll-rule validation remain outstanding. Do not upload real employee or salary information to the demo.
What to verify before real use
The exact deployment, access controls, data handling, connected services and operating process need review for your use. A working local interface is one piece of evidence; it does not settle every live-use requirement.
A straightforward evaluation
Ask for a demonstration with sample records. Follow one record from beginning to end. Ask where information is stored, who can access it and which actions are simulated. Review open issues before deciding what comes next.
Capability status
What works today, by capability.
Status reflects the source review, not a later live deployment. Recheck it against the exact version being offered to you.
- Implemented in sourceEmployee central, departments, designations and organisation chart
- Implemented in sourceLeave policies, balances and requests
- Implemented in sourceHoliday calendars
- Implemented in sourceAttendance and regularisation
- Implemented in sourceNotices and acknowledgements
- Implemented in sourceReview cycles, performance and employee goals
- Implemented in sourceOnboarding cases and templates
- Implemented in sourceSalary structures, revisions, resizing and voiding
- Implemented in sourcePayroll run lifecycle: inputs, adjustments, opening balances, approval, locking
- Implemented in sourceEffective-dated rules with maker-checker approval
- Implemented in sourceIndia rule pack installation (not a statutory-correctness claim)
- Implemented in sourceAudit-history (hash-chain) check
- Implemented in sourcePayslip PDF rendering and twelve HR letter templates
- Implemented in sourceAdmin, employee portal and operator shells
- Implemented in sourceCompany registry and comparison
- Partly implementedPayroll engine rule trace
- Partly implementedPayslip views and core-backed payslip download
- Partly implementedPersonal-data vault and erasure
- Partly implementedGeofence events and live positions
- Partly implementedAI payslip explanations, diffs and anomaly checks
- Partly implementedEmployee assistant and policy knowledge base
- Partly implementedAI offer-letter generation
- Partly implementedAutomated onboarding workflow
- Partly implementedDocument service dashboard
- Partly implementedFlutter employee mobile client
- Partly implementedVoice interview logic
- SimulatedLogin: demo persona selector, not real authentication
- Feature-flaggedOperator console (behind a feature flag)
- Not availableReal-time voice transport
- Not availableStatutory filing
- Not availableBank salary disbursement
- Not availableProduction authentication and access enforcement
Claims we do not make
- 100% compliant payroll
- Certified immutable records
- Guaranteed salary accuracy
- Bank payments or statutory filing included
- Live voice recruitment
- Enterprise-ready authentication
If you see any of these said about HRMS, treat it as incorrect and ask us.
A closer look, without the sales theatre
See what is there. Ask what still needs work.
The local review started the core platform with 24 seeded employees and 651 recorded events. It also exercised supporting AI, geolocation and document services. This is evidence of local evaluation, not a production customer result.
Availability. For evaluation with sample data. Production authentication and independent payroll-rule validation remain outstanding. Do not upload real employee or salary information to the demo.
Next step
Ask the difficult question first.
A clear answer is more useful than a broad promise. Bring the question that would stop you from choosing HRMS.
Start with a question, not a commitment. Use sample or anonymised information.
