Cloud biometric attendance, with your devices kept inside your office
Connect the biometric attendance devices in your locations to SaudHR without exposing any device to the internet. A small agent on an office PC reads and sends; SaudHR handles attendance and reports.
Architecture designed to support compatible biometric attendance devices. We confirm your device model's compatibility during onboarding.
- Biometric device Inside your office network
- SaudHR Agent On a PC in the office
- Secure connection Encrypted HTTPS, started by the agent
- SaudHR Attendance Records ready for reports
How it works
-
Install the agent
Install the SaudHR Attendance Agent on a Windows PC in the office. It runs as a background service.
-
Activate it with a one-time code
Create the agent in the admin screen and get an activation code that works once, for a short time.
-
Add your devices
Add your attendance devices, assign them to the agent, and test the connection to each one from the admin screen.
-
Punches arrive automatically
The agent reads new punches and sends them in batches; they appear in attendance once device users are mapped to employees.
Security by design
Devices are never exposed
The agent connects out to the cloud; the cloud never connects into your network.
No open ports
No static IP and no port forwarding on your router.
Encrypted connection
Everything between the agent and SaudHR travels over HTTPS.
One-time activation code
It expires after a short time and cannot be used twice.
Stop it instantly
Revoking the agent in the admin screen stops its data being accepted at once, and its credential can be renewed.
Device keys encrypted
A device's communication key is stored encrypted and never shown again after it is saved.
Device and location management
One screen, in Arabic and English, for agents and devices: name, location, connectivity, last contact and last successful sync — with a one-click connection test for each device.
Map device users to employees
Each user ID on the biometric device is mapped to an employee — by ID, never by name. Punches from unmapped users are kept, not discarded, and listed separately until they are mapped.
| Devices | Agent | Connectivity | Last sync |
|---|---|---|---|
| Head office gate | Reception PC | Online | 2 minutes ago |
| Warehouse gate | Reception PC | Online | 2 minutes ago |
| Device user ID | Employee | |
|---|---|---|
| 1052 | Sarah Alotaibi | Mapped |
| 1087 | — | Unmapped |
Keeps working through internet outages
If the connection drops, the agent keeps punches on the PC and sends them automatically when it returns — without duplicating a single record.
Sync monitoring for every device
For each device: records received, duplicates and rejections, unmapped punches, the last sync time and the last error.
Integration with each device model is enabled once it has been validated on that model. Contact us to check the status of your device model.
Questions about biometric integration
Do I need a static IP or open ports on my router?
No. The agent connects to SaudHR from inside your network over an encrypted outbound connection, so your device never needs to be visible on the internet.
Which biometric devices are supported?
The architecture is designed to support compatible biometric attendance devices. We confirm your device model's compatibility during onboarding, and integration with each model is enabled once it has been validated on that model.
What happens if the internet goes down?
The agent keeps the punches and sends them when the connection returns, with no duplicate records.
Can I connect more than one location?
Yes. You can install an agent at each location and assign several devices to each agent.
What does the agent need to run?
A Windows PC in the office on the same network as the biometric device, with an internet connection.
Can the agent be stopped?
Yes. Revoking it in the admin screen stops its data being accepted immediately.
Ready to see SaudHR?
Request a demo and we will show you how the system works for your company.