SAAR Attendance is a ZKTeco ADMS server. Each machine pushes its punches out to us on a schedule you set, so a branch needs nothing more than a working internet connection — no port forwarding, no static IP, no VPN, no PC left switched on.
The machine opens the connection to a single fixed hostname on a schedule. Nothing is exposed on your side, which is what removes the static IP and the VPN from the job.
A machine that has never been seen lands in a pending list instead of attaching itself to somebody’s data. You claim it by serial number, give it a name and a branch, and only then does it belong to you.
Add a person, set a fingerprint or face PIN, and the instruction is queued for the device to pick up on its next call. The queue records when it was sent and what the device answered.
One bearer key per organisation, per consuming product, with cursor pagination on the time we received a punch rather than when it happened — so a device that was offline for three weeks still hands over everything it was holding.
Set the machine’s server address to the attendance host. That is the whole network change.
The unknown serial appears as a pending device. Claim it to your organisation and name it — main gate, factory floor, back office.
Add a person with the PIN the device knows them by; the enrolment is queued and collected on the next call-in.
Watch them arrive, filter and report on them in the browser, or pull them over the API into another system.
ZKTeco machines that speak the ADMS push protocol, fingerprint and face alike. The device URLs are a hardware contract and are kept byte for byte as the machines expect them.
No. The connection is made by the device, outward, to one fixed hostname. A branch needs working internet and nothing else.
The device holds its punches and pushes them when it reconnects. Consumers read the queue by when we received a row, not when the punch happened, so nothing is skipped.
Neither in particular. A school, a factory, an office and a hospital all use the same thing; nothing in the product assumes an industry.
One device server, one hostname, and machines that report in on their own.
SAAR Attendance