> 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/what-hardware-to-use.md).

# What hardware to use?

## Do I need a physical server, or can I use a virtual machine?

For Navixy platform to work, it doesn't matter whether you are using a physical or virtual server. Either type of server is appropriate as long as it shows sufficient performance and reliability.

Most current customers use virtual servers, both in cloud and on-premises data centers, as it gives more flexibility in administration and resource management. However, running the platform on a physical local server is also possible and is not associated with any extra difficulties.

## What are the minimum hardware requirements for running Navixy On-Premise?

The amount of resources directly depends on the intensity of Navixy platform usage, mainly on the number of tracked objects.

The minimum requirements are as follows:

* Processor (CPU): 4 cores (Intel/AMD 64-bit architecture)
* Memory (RAM): 8 GB
* Storage (Disk Space): At least 500 GB of free space, SSD recommended for faster performance.

As the number of tracked assets grows, so does the consumption of resources, so you need to allocate them accordingly.

## Should I use a dedicated server to store the database?

This is not a strict recommendation, but a best practice for large size instances with more than 5000 simultaneously active tracking devices. This way, you can distribute the resources more efficiently.

## Links

* [Server hardware](/docs/on-premise/on-premise/how-to-guide/requirements/server-hardware.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 dynamically by asking a question.

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

```
GET https://navixy.com/docs/qna/on-premise/deployment-overview/what-hardware-to-use.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.