⚡ Hardware Integration Manual

eSSL Biometric Attendance Machine Cloud Sync Guide

How to push fingerprint & facial punches directly from eSSL hardware to the cloud in real-time without crashing desktop background utilities.

1. The Desktop Sync Flaw in Traditional HR Software

Most legacy HR systems force businesses to install a local Windows background executable (.exe) on an office PC. This introduces multiple points of failure:

  • Office desktop shuts down, sleeps, or runs mandatory Windows updates.
  • Antivirus software blocks local socket port 4370.
  • Punches fail to sync, causing disputed loss of pay (LOP) during month-end payroll lock.

2. Modern Architecture: Direct HTTP Cloud Push (ADMS Protocol)

MicroPlesk utilizes native ADMS / Cloud Push protocol embedded in modern eSSL (SilkBio, K30, UFace, e990) and ZKTeco hardware:

[Biometric Hardware] --(Direct HTTP POST on Swipe)--> [MicroPlesk Cloud Ingestion]
✓ Zero local PC needed • Synced in under 500ms • Multi-branch support

Whenever a factory or office employee scans their fingerprint or face, the device immediately dispatches an encrypted HTTPS payload containing the employee card ID, timestamp, and device identifier directly to your tenant database.

3. Compatible Hardware Models

eSSL K30 Pro / K90
eSSL SilkBio-101TC
eSSL uFace 202 / 302
ZKTeco MB20 / MB360
Realtime RS-10 / RS-20
Matrix COSEC Vega

Need Help Connecting Your Biometric Machines?

Our hardware engineers configure your devices over AnyDesk / TeamViewer in less than 30 minutes for free during onboarding.