Keep your eSSL machines. Connect them to the cloud.

eSSL machines are in offices, schools and factories all over India, often wired to eTimeTrackLite on one office PC. Here is how to move those punches to the cloud and into your HR or payroll software, keeping the machines you paid for.

Today

How eSSL machines usually run

The classic eSSL setup is a machine on the office network and eTimeTrackLite on a desktop that collects the punches. At month end someone exports a report and keys it into payroll, or imports it into the HR system. It works until the PC fails, a branch opens in another city, or the company moves to Zoho People, Keka or greytHR and wants punches there every day.

Many eSSL models can push their punches to a server over the internet, often labelled ADMS in the machine's menu. That is what lets them report to a cloud service directly, with no PC in between. Models without it can still be read on the local network by a small connector.

What stays the same

  • The terminals on the wall and their wiring
  • Enrolled users and how people punch
  • Card and PIN options already set up

What goes away

  • The office PC that has to stay switched on
  • Monthly exports and re-typing into payroll
  • One separate system per branch

Ways to connect

Connecting eSSL machines: the options

Which one applies depends on the model. The free model check tells you.

RouteHow it worksDetails on camsbiometrics.com
Direct to the cloudVerified models send every punch to the Cams cloud over the internet by themselves: no PC, real-time, and users can be enrolled and synced from the cloud. Models that need a little help connect as a Cams Open Terminal.Cams Open Terminal
Cams Open TerminalFor any other terminal, including older and LAN-only machines. You pick the terminal type, enter its serial and test it free in the sandbox with a few users before you buy. The punches reach the Cams cloud from the machine's own cloud, from a Cams Bridge on site (SDK or attendance database), or from the Cams Crew Mobile app.Cams Open Terminal
On your own serverProtocol Engine Lite runs on your server, on Windows or Linux, for networks that must stay closed or cannot reach the internet. Terminals talk to your server instead of the Cams cloud.Protocol Engine Lite for ZKTeco and eSSL

Step one

Check your model before anything else

Describe the machine

Enter its brand, model and how it connects on developer.camsbiometrics.com. It is free and needs no purchase.

Connect it for a test

Follow the setup steps shown for your model to connect the machine to the test system.

Run the guided checks

Register a user, record a punch, delete a user: the test confirms which operations your machine supports and which route it needs.

Once connected

What your eSSL machines can do next

  • Feed your HR, payroll or ERP software through ready-made integrations, punch by punch.
  • Run every branch from one account, with each terminal labelled by site.
  • Enrol and sync users from the cloud on models connected directly.
  • Work with AI assistants and automations through the Cams API and MCP server.

Connect eSSL machines with Cams

Cams connects ZKTeco, eSSL, Hikvision and 90+ other brands to its cloud, directly, through a Cams Open Terminal, or with Protocol Engine Lite on your own server.

FAQ

eSSL machines and the cloud: questions

Can we stop using eTimeTrackLite?

Yes, once punches reach your HR or payroll software through the cloud. Keep a copy of its data for your records, and choose a changeover date, usually the first day of a payroll month.

Do eSSL machines work with Zoho People, Keka and greytHR?

Yes. Once connected to the Cams cloud, an eSSL machine feeds the same ready-made integrations as any other terminal: see Zoho People, Keka and greytHR.

Which eSSL models connect directly?

Check your model for free at developer.camsbiometrics.com. It tells you whether the machine connects directly, or is added as a Cams Open Terminal.

What if my eSSL machine has no internet option?

Add it as a Cams Open Terminal. A Cams Bridge on the local network reads it through its SDK or its attendance database and passes the punches to the cloud. The machine itself does not change.

What does it cost?

Each connected terminal needs a Cams API licence: a one-time activation plus a yearly fee, with no per-employee charge. Terminals that cannot connect directly are added as a Cams Open Terminal, which you can test free in the sandbox before you buy. Current ranges are on the Cams pricing section.