> 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/on-premise/how-to-guide/requirements/server-software.md).

# Server software

Install required software for Navixy on-premise: Ubuntu 20+ or Windows Server 2016+, Java JDK 21, MySQL 8.0, and Nginx. Covers all environment prerequisites.

## Operating systems

Navixy's backend services are developed using Java programming language, while the frontend is built with pure Javascript. As a result, the software is cross-platform compatible, which means it can run on various operating systems. However, for optimal performance and compatibility, we recommend using the following operating systems:

* Linux: Ubuntu 20 or newer, 64 bit
* Windows Server 2016 or newer, 64 bit

These operating systems have been extensively tested and optimized for use with Navixy, ensuring a seamless user experience and minimal technical issues.

## Environment requirements

Additionally, to install and run Navixy On-Premise edition, you will require the following environment. It is all provided under GNU or similar licenses, and there is no need to spend any money on it.

* ﻿[**Java SE Development Kit (JDK) 21**](https://www.oracle.com/java/technologies/downloads/#java21) by Oracle or **openjdk-21-jre-headless** from repos. All the other JDK 21 based distributions are also compatible.
* [**MySQL Server 8.0**](https://dev.mysql.com/downloads/mysql/8.0.html)**.** The platform does not feature support for other DBMS, including PostgreSQL and MariaDB.
* [**NGINX**](https://nginx.org/en/download.html) of any actual version - **1.2** or newer (If you wish to use image previews in task forms, nginx must have [image filter](http://nginx.org/en/docs/http/ngx_http_image_filter_module.html) module)

{% hint style="info" %}
Automatic platform installation scripts for Linux install the above software if it is not found on the server.
{% endhint %}

* Servers (except MySQL server) must have access to the Internet and have static IP address.
* Installation process requires root access (Unix systems) or administrative user (Windows). During the installation of databases engines you need to be granted with MySQL's root access.
* For HTTP services we recommend to use domain names, e.g. for API – api.domain.tld, for User interface – my.domain.tld and panel.domain.tld for Admin panel. TLD means any top level domain (com, net, edu, etc).
* High-speed and reliable internet connection at least 10 Mbit/s
* Monitoring system that you like. It is not required but recommended
* Recommended filesystem is ext4
* For sending email from localhost you should have got an configured MTA (Mail transfer agent), e.g. Postfix
  * It is also possible to send email through another services, e.g. gmail, but in that case email "from" field substitution won't work


---

# 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/on-premise/how-to-guide/requirements/server-software.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.
