> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/on-premise/on-premise-licensing-faq.md).

# On-Premise licensing FAQ

Navixy On-Premise license authorizes one platform instance; request additional instances from sales and understand how the license key is validated

## What is Navixy On-Premise license?

This is an authorization to use Navixy platform instance according to contract. On the information systems side, it is a unique key that corresponds to the ID of your instance in the Navixy system. It is issued by the Navixy technical team and entered into the database of your instance.

## How many Navixy On-Premise instances can I have?

One instance per license. You can have unlimited Navixy instances based on your requirements.

## What should I do to have an additional Navixy instance?

Contact Navixy sales team or your account manager to discuss the details.

## How is the license checked?

Your Navixy instance communicates with the authentication server and transmits the current license key and current statistics. In response, the instance receives a new key, which tells it that the license is up to date and it can continue working.


---

# 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://navixy.com/docs/qna/on-premise/on-premise-licensing-faq.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.