Run passive face liveness detection in a single Docker container on your own Linux server, exposed as a local REST API. No images or liveness results ever leave your infrastructure.
These are the exact minimum and recommended requirements published in the FaceLivenessDetection-Docker repository — check the repo directly for the latest version, since SDK requirements can change between releases.
Install the SDK, then activate it with a license key before calling any liveness function – every platform follows this same activate-then-initialize pattern.
docker pull faceplugin/face-liveness:latest.GET /api/health to confirm the container is up.POST /api/activate and your license key.# Health check
curl -s http://127.0.0.1:8084/api/health
# Activate with your license key
curl -s -X POST http://127.0.0.1:8084/api/activate \
-H "Content-Type: text/plain" \
--data-binary @license.txt
# Run a liveness check
curl -s -X POST http://127.0.0.1:8084/api/liveness \
-H "Content-Type: application/json" \
-d '{"image": "<base64-jpeg>"}'
Licenses are offline and bound to a machine code. The API starts even before activation, but liveness checks stay restricted until you activate with a key tied to that machine code – Docker and local-host installs get different machine codes, so request a key for whichever environment runs in production.
No. Every liveness check runs on your own server or directly on the device, depending on the platform – images never leave an environment you control.
Licenses are offline and bound to a machine code, application ID, or bundle ID depending on the platform. Contact FacePlugin with that identifier to receive a license key – there are no per-call or per-check fees once licensed.
The Linux integration is maintained publicly on GitHub at github.com/Faceplugin-ltd, where you can browse the code, file issues, and track releases.
Talk to our team to get a license key and a 15-day evaluation period started.