> 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/vs-3divi.md).

# vs 3DiVi

Faceplugin vs 3DiVi Face SDK. On-premise face recognition, platforms, liveness, and ID document products. Public 3DiVi docs versus Faceplugin products in these docs.

[3DiVi Face SDK](https://3divi.ai/products/software/face-sdk) is a C++ face recognition library with wrappers (C#, Java, Python, Swift, Flutter) for Windows, Linux, Android, and iOS. It documents on-prem / on-device / own-cloud deployment and a **2d\_liveness** estimator. 3DiVi also sells OMNI Platform (client-server video) and Image API (REST).

Faceplugin is an **on-premise SDK suite**: Face Recognition, standalone Face Liveness (passive anti-spoofing HTTP + mobile), ID Document Recognition (passport OCR / MRZ), and ID Document Liveness. **Server SDKs** are Docker Hub images licensed with a **machine code** (machine code).

| Criterion                                 | Faceplugin                                                              | 3DiVi                                                      |
| ----------------------------------------- | ----------------------------------------------------------------------- | ---------------------------------------------------------- |
| On-premise / offline after license        | Yes                                                                     | Yes (offline and online license modes documented)          |
| Android / iOS face SDK                    | Yes                                                                     | Yes                                                        |
| Flutter face                              | Yes (Face Recognition + Document)                                       | Yes (Face SDK docs list Flutter)                           |
| React Native / Ionic                      | Yes                                                                     | Check vendor                                               |
| Windows / Linux face                      | Yes (HTTP API + native)                                                 | Yes (C++/Python/C#)                                        |
| Linux Docker Hub HTTP API                 | Yes (`faceplugin/face-recognition`, `face-liveness`, `document-reader`) | Check vendor (local license server mentioned for Docker)   |
| Standalone face anti-spoofing product     | Yes (passive `POST /api/liveness`)                                      | Liveness as Face SDK estimator; BAF / other products exist |
| Passport OCR / ID card SDK                | Yes                                                                     | Check vendor (not the core Face SDK page)                  |
| Document liveness                         | Yes (Linux 8086)                                                        | Check vendor                                               |
| NIST FRVT (as claimed in Faceplugin docs) | Evaluated matching                                                      | Check vendor                                               |
| iBeta / PAD certification                 | No iBeta certification claimed in these docs — ask Faceplugin           | Check vendor                                               |
| License model                             | Offline license key / machine code                                      | Hardware, app id, USB token, online validation options     |

**Choose Faceplugin** when you want a **documented HTTP Docker API** plus **ID OCR and document liveness** in the same vendor docs, with mobile 1:N Identify demos.

**Look at 3DiVi** when you need their C++ Face SDK / OMNI video platform specifically. Confirm Flutter / React Native and document OCR on [3DiVi docs](https://docs.3divi.ai/face_sdk/).

Integrate Faceplugin: [Android Face Recognition](/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

* [SDK comparison index](/help/comparisons.md) · [Choose a product](/getting-started/choose-a-product.md) · [Glossary](/help/resources/glossary.md)
* [FAQ](/help/resources/faq.md) · [Try it](/getting-started/try-it.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/vs-3divi.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.