> 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-updates-faq.md).

# On-Premise updates FAQ

Update your instance on your own schedule, no automatic delivery. Major versions every 2–4 months; minor versions released frequently with fixes

## How often does my platform get updated?

Navixy platform does not have automatic update delivery functionality. All updates are performed only on the owner's initiative. The number of updates isn't limited. You can perform this procedure at any suitable time.

## How often are new versions released?

Navixy doesn't have a strict release cycle. Major builds of the platform containing significant changes and bringing new functionality are released every 2-4 months. Minor versions, bringing mainly fixes and improvements to the current functionality, are released up to several times a month.

## Do I need to install each new update?

We recommend keeping the platform updated to receive all updates and fixes in time.

However, some of our clients prefer to update less frequently and settle for basic functionality. The decision is yours. An non-updated version of the platform doesn't lose its functionality.


---

# 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-updates-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.