Developer checklist

This page describes the main points that developers should be sure to include in their implementations. Links go to the relevant section of our documentation.

Image size¶

Requirements listed here for size and compression.

Image requirements¶

Requirements listed here.

Pipeline selection¶

Pipeline selection controls the attack vector being queried. If you are calling one attack vector at a time via /check_liveness then you will need to specify the pipeline. The Screen Replay attack vector is used by default.

Pipeline naming¶

• All pipelines are named following the next naming convention: attack-vector_yyyy-mm.

Hardware recommendations¶

We recommend that integrators proceed with the c5.4xlarge in AWS or equivalent hardware from another cloud provider. Integrators can proceed with the c5.xlarge or equivalent as a low-throughput configuration. High throughput configurations are likely to benefit the most in cost-benefit by using an instance equipped with a GPU, such as the g4dn.xlarge or equivalent.

Licensing¶

IDLive Doc operates with a license using a time-based cutoff. EVAL software is designed to cease operation 90 days from release, and PROD software has a 365 day limit. The expiration time can be queried using the API.

Developers and Product teams should plan on updating at minimum once a year to take advantage of the significant algorithm performance updates and security improvements.