> 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/deployment-overview/how-to-install-the-platform.md).

# How to install the platform?

Download and install via easy 3-command wizard or advanced Linux/Windows scripts. Docker or manual setup, scale from 500 to 5000+ assets

## Where can I download the installation package of Navixy On-Premise platform?

The latest build is available at:

* <https://get.navixy.com/latest>

For easy installation, a separate download is not required — it will be downloaded as part of the installation steps.

## How can I choose the platform features and modules I want?

Modules depend on your contract plan:

* Tracking
* Reports
* Field Service
* Fleet Management

## What installation methods are available? How hard are they?

* **Easy**: 3 shell commands + a wizard. Deploys as Docker images. Recommended for small and medium instances (up to \~5000 registered assets).
* **Advanced (Linux)**: automated install that can split the database onto a dedicated server. Recommended for larger instances (5000+ assets).
* **Advanced (Windows)**: fully manual installation. Recommended only for experienced administrators and Windows-only environments.

## Links

* [Easy installation](/docs/on-premise/on-premise/how-to-guide/installation/easy-installation.md)
* [Advanced installation](/docs/on-premise/on-premise/how-to-guide/installation/advanced-installation.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://navixy.com/docs/qna/on-premise/deployment-overview/how-to-install-the-platform.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.