> 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/request-a-license-and-support.md).

# Request a License & Support

Request a Faceplugin offline license. Mobile FP1 keys bind to app id. Server FPMC1 machine codes from GET /api/machinecode. Docker and host codes differ. On-premise, no per-call cloud.

Faceplugin licenses are **offline**. After activation, face matching, liveness, and document OCR do **not** need the internet.

In short: **mobile** keys (`FP1.…`) bind to your app id; **server** keys start from a **machine code** (`FPMC1.…`) from the host or Docker you will run in production. Definitions: [Glossary](/resources/glossary.md).

### Need a license?

* **Mobile SDK:** contact us via WhatsApp, Telegram, or email. Demo `FP1.…` keys are bound to the **sample application id / bundle id** on each platform page. Request a new `FP1.…` if you use your own app.
* **Server SDK (Linux / Windows / Docker):** start the API once, copy `FPMC1.…` from logs or `GET /api/machinecode`, and send that code. Docker and a native host have **different** machine codes. Use the code from the environment you will run in production.

Do not paste demo `FP1.…` keys into your production app.

### FAQ

**Can Faceplugin run completely offline?** Yes, after the key is issued and activated.

**Why is my Docker machine code different from the host?** The fingerprint includes Docker. License the environment you ship.

**Status codes 1–4 on mobile?** See [Status codes](/resources/status-codes.md).

### Need support?

Faceplugin provides integration help for licensed SDKs, plus ongoing support after you go live. Email, WhatsApp, or Telegram with your OS, GitHub repo name, activate/init result codes, and whether you use Docker or a native Google Drive runtime.

### Contact us

* Email : <info@faceplugin.com>
* WhatsApp : [+1 (469) 278-4822](https://wa.me/+14692784822)
* Telegram : [@faceplugin](https://t.me/faceplugin)

### Related documentation

* [Try it](/try-it.md) · [FAQ](/resources/faq.md) · [Glossary](/resources/glossary.md) · [Troubleshooting](/resources/troubleshooting.md)
* [Choose a product](/choose-a-product.md) · [Changelog](/resources/changelog.md)

{% hint style="info" %}
GitBook admin (not this markdown): custom domain, Open Graph image, sitemap, and **Google Search Console** on the docs hostname.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.faceplugin.com/request-a-license-and-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.