> 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/on-premise/qa/software-updates/current-version.md).

# Current version

Find the Navixy on-premise platform version number in the VERSION file on your server. Understand the major and minor build numbering scheme.

The information about the Navixy platform version deployed on your On-Premise instance can be found in the system files of the backend services.

To locate the version, navigate to the directory of any Java-service and look for the file named **VERSION**. Typically these folders are:

* Linux: `/home/java/api-server/VERSION`
* Windows: `C:\java\api-server\VERSION`

The VERSION file is a plain text file that can be opened and read with any text editor. In the file, you will find technical information, and at the end, there will be a line indicating the platform version. The line contains the following details:

**navixy-standalone-provider.2023.02.166**

* navixy-standalone – indicates that this is the On-Premise instance;
* provider or enterprise – package type;
* 2023 – the year of release;
* 02 – the major build version, which typically corresponds to the release month
* 166 - the minor build version, numbered consecutively

Major versions of the platform are released every 2-3 months and contain significant innovations and new features.

Minor versions can be released multiple times per month, and include small improvements and bug fixes that do not require significant changes to the platform's code.


---

# 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/on-premise/qa/software-updates/current-version.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.