Cams Protocol Engine

The Cams Protocol Engine manages data flow between cloud systems and biometric devices. The hosted version runs on the Cams Data Server, but a Lite version installs on your own server so attendance is delivered straight to your web API endpoints, including fully offline LAN deployments with no internet connectivity.

Get started Developer docs

Overview

Run the Cams biometric protocol on your own Windows, Linux, or Unix server so devices talk to your application directly — including fully offline LAN deployments.

The Protocol Engine sits between biometric devices and your application, buffering attendance when the cloud or a device is unavailable and reconciling once systems recover. The Lite (on-premise) engine installs on Windows, Linux, or Unix and triggers your web API endpoints automatically as punches arrive. Engine selection depends on hardware: the 1x/2x Protocol Engine for Cams RSP1x and R2x series, the 3x Protocol Engine for the Cams 3x series, and the ZKTeco API Engine for third-party devices such as ZKTeco, eSSL, BioMax, and Identix.

ENGINEHTTPOn-premise service (Windows/Linux/Unix)C++

Built for

Enterprises and integrators needing on-premise or offline biometric data handling, and those integrating third-party (ZKTeco/eSSL/BioMax/Identix) devices.

Cams Protocol EngineLite protocol engineOn-premise biometric engineZKTeco API engineeSSL API engineADMS server alternative1x 2x protocol engine3x protocol engine

Capabilities

What it does

On-Premise Hosting

Install the Lite engine on your own server to keep biometric data within your infrastructure.

Offline / LAN Operation

Operate entirely on a local network with no internet dependency.

Store-and-Forward

Holds attendance data during outages and updates downstream systems when they come back online.

Hardware-Matched Variants

Engine editions for Cams 1x/2x, Cams 3x, and third-party ZKTeco/eSSL/BioMax/Identix devices.

Features

Everything included

Lite engine deployable on your own Windows, Linux, or Unix server
Direct device-to-application data flow without the Cams Data Server in the middle
Supports fully offline / LAN-only deployments with no internet connectivity
Buffers attendance when the cloud or device is unavailable and reconciles on recovery
1x/2x Protocol Engine for Cams RSP1x and R2x series devices
3x Protocol Engine for Cams 3x series devices
ZKTeco API Engine for third-party devices (ZKTeco, eSSL, BioMax, Identix and more)

Build with Cams Protocol Engine

Grab a key, read the docs, and ship. Our team helps with your first integration.

Talk to an engineer WhatsApp

FAQ

Common questions

Can I receive biometric data without it passing through the Cams Data Server?

Yes. Install the Lite version of the Protocol Engine on your own Windows, Linux, or Unix server, and your web API endpoints are triggered automatically when attendance is registered at the device.

Which Protocol Engine do I need?

Cams RSP1x and R2x series use the 1x/2x engine; Cams 3x series use the 3x engine; third-party devices such as ZKTeco, eSSL, BioMax, and Identix use the ZKTeco API Engine.