> For the complete documentation index, see [llms.txt](https://doc.faceplugin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.faceplugin.com/help/comparisons.md).

# SDK comparison

On-premise face recognition and liveness SDK comparison. Faceplugin versus 3DiVi, FaceTec, and Luxand. Criteria from public vendor docs, not guessed checkmarks.

This section compares **Faceplugin** to vendors people often evaluate for on-premise face matching, anti-spoofing (liveness), and ID reading. Tables use **public vendor documentation**. Where a fact is not stated on that vendor’s site, the cell is **Check vendor**.

Faceplugin facts below match the products in these docs: on-premise/offline after license activation; Android, iOS, Flutter, React Native, Ionic, Windows, and Linux Docker; **passive** face anti-spoofing; passport OCR / ID card APIs (**16,900** templates / **255** countries — [catalog PDF](/products/id-document-recognition-sdk/capabilities.md#document-type-classification--worldwide-coverage)); document liveness on Linux; NIST FRVT **evaluated** matching. These docs do **not** claim iBeta certification for Face Liveness. Ask Faceplugin if you need a certification statement.

Capability overviews: [ID Document SDK](/products/id-document-recognition-sdk/capabilities.md) · [Face SDK](/products/face-recognition-sdk/capabilities.md).

| Page                                                     | When to read it                                       |
| -------------------------------------------------------- | ----------------------------------------------------- |
| [Faceplugin vs 3DiVi](/help/comparisons/vs-3divi.md)     | Cross-platform face SDK, C++ core, liveness estimator |
| [Faceplugin vs FaceTec](/help/comparisons/vs-facetec.md) | 3D liveness / FaceMap KYC vs 2D on-prem SDK suite     |
| [Faceplugin vs Luxand](/help/comparisons/vs-luxand.md)   | Classic FaceSDK vs Faceplugin + document products     |

Then integrate: [Document capabilities](/products/id-document-recognition-sdk/capabilities.md) · [Face Recognition Android](/products/face-recognition-sdk/recognition-and-liveness/mobile-sdk/face-recognition-android-sdk.md) · [Liveness Linux](/products/face-recognition-sdk/liveness-detection-sdk/server-sdk/liveness-detection-linux-sdk.md) · [Document Linux](/products/id-document-recognition-sdk/recognition-and-liveness/server-sdk/id-document-recognition-linux-sdk.md)

### Related documentation

* [Choose a product](/getting-started/choose-a-product.md) · [FAQ](/help/resources/faq.md) · [Glossary](/help/resources/glossary.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.faceplugin.com/help/comparisons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.