Face Recognition & Liveness SDK

Register an email address, receive an activation key, and run one Docker command. Free for 14 days, limited to 100 enrolled identities and 50 API calls per hour. Every capability is the full product, 1:N identification, 1:1 verification, passive and active liveness, face analytics, the dashboard, and the sandbox.

Yes, and this is the one place the demo and the licensed product differ. The demo validates its activation key with us, so it needs an internet connection for the 14 days it runs and will stop working without one. Face images, templates, and match results are still processed entirely on your machine and are never transmitted.

The licensed product makes no such call. No activation check, no outbound connection at inference time, no telemetry. If your evaluation has to happen inside an isolated network, ask us for an offline evaluation licence.

Passive analyses a single image for the signals that distinguish a live face from a photograph or a screen. It requires no user action and takes a few hundred milliseconds. Active issues a randomised head-movement sequence, records the user performing it, and verifies both the order of the movements and the anti-spoof result across the video. Active is stronger; passive is invisible. Both are included in every licence.

Yes. submit_and_recognize returns the liveness verdict and the identity together, matching across every frontal frame in the video rather than a single still. Recognition is skipped entirely when liveness fails, so a spoofed submission is never identified.

The SDK ships its own dashboard on the same port as the API: an interactive sandbox, request logs, API-key management, and a live OpenAPI reference. No second service to deploy.

Method, endpoint, status code, latency, masked API key, and client IP. Request and response bodies are never persisted, so biometric payloads do not reach the log store.

Each API key is its own isolated tenant with its own face database namespace. Identities enrolled under one key are invisible to every other key on the same instance. Note that this makes the key a long-lived credential, deleting or rotating it makes the identities enrolled under it unreachable, so plan re-enrolment before any rotation.

Developer is limited to 1,000 enrolled identities on one machine and is intended for integration work and small production deployments. Node-locked removes the identity limit and adds a contracted support term on the same single machine. Neither has the demo’s time limit, rate limit, or connectivity requirement.

By email after purchase: the container image reference, your licence file, and installation instructions.

Provisioning, monitoring, patching, backups, and support on a single-tenant instance in a region you choose, European Union, United States, or Asia-Pacific. Your face database is never co-located with another customer’s. From $590 per month on a 12-month minimum term.

No. The instance is single-tenant and enrolled data is yours. ARSA operates the infrastructure and does not access the contents of the face database.

Yes. There is no outbound call at inference time and no telemetry. Licence activation and model updates are both supported offline. This applies to the licensed product only, the 14-day demo requires connectivity.

Terminate TLS at a reverse proxy, restrict CORS, add rate limiting at the proxy layer, and change the default administrator credentials and signing key. The service is built to sit behind your own infrastructure, not directly on the internet. Full deployment requirements are in the system requirements section above.