Let's start a conversation
Whether you need a demo, have a support question, or want to discuss enterprise requirements — we're here to help.
HR & Biometrics
ML Kit Face Verification, Liveness, GPS Bounds & Corrections.
Work Hub & Tasks
Timesheets session tracking, Helpdesk Tickets & Maintenance.
Fleet & Fuel Logs
Vehicle trip odometers, Fuel OCR Scanner & Service Orders.
Odoo ERP & API
30s Heartbeat Loop, REST API Sync & OpenHRMS Connectors.
Direct Access & Support
System & Hardware Rules
Our mobile and web ecosystem coordinates directly with Odoo backends, enforcing real-time compliance safeguards:
Send us a message
Fill out the form below to receive a custom solution proposal and schedule a technical walkthrough.
Frequently Asked Architecture Questions
Q: How does the 30-second Heartbeat Engine operate?
When logged in, the mobile client runs a background timer pinging /secure_api/ping every 30 seconds with GPS coordinates, hardware tokens, and active session hashes to enforce session security and active keep-alive.
Q: What is the difference between Mobile and Web Face Scanners?
Mobile clients harness Google ML Kit for real-time client-side liveness detection, eye openness verification, and face crop bounds. Web clients stream video canvas feeds with manual snapshot triggers to optimize browser resources.
Q: How does Smart Worker synchronize with Odoo ERP?
Smart Worker features dedicated REST endpoints mapping directly to Odoo modules (HR Attendance, Timesheets, Helpdesk, Fleet, Expenses, and OpenHRMS). Data posts real-time with automated ledger reconciliation.
Q: How are offline regions and connectivity drops handled?
The client uses 14 active state providers backed by local SQLite storage. Clock-ins, odometer logs, and receipt captures queue locally and flush automatically when network connectivity restores.