> 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/integration/deploy-and-host.md).

# Deploy and host

Deploy and host Faceplugin server SDKs. Architecture, hosting requirements, and production checklist for Linux, Docker, and Windows.

Use this section when you put Faceplugin on **your** servers. Faceplugin does not host inference for you after you activate a license.

| Page                                                                           | Read it when you need to                                     |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------ |
| [Architecture](/integration/deploy-and-host/architecture.md)                   | Combine products, choose HTTP vs `sdk.py`, know what you own |
| [Hosting requirements](/integration/deploy-and-host/hosting-requirements.md)   | Size CPU, RAM, disk, ports, and Docker flags                 |
| [Production deployment](/integration/deploy-and-host/production-deployment.md) | Harden a first-run install for production                    |

For eKYC servers, prefer [Face Recognition + Liveness](/products/face-recognition-sdk/recognition-and-liveness.md) and [Document Recognition + Liveness](/products/id-document-recognition-sdk/recognition-and-liveness.md) instead of separate recognition-only and liveness-only containers. Start with a platform page for install steps, then use this section for topology and ops.

### Related documentation

* [HTTP API](/integration/http-api.md) · [Choose a product](/getting-started/choose-a-product.md) · [Request a License](/help/request-a-license-and-support.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/integration/deploy-and-host.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.