> 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/prerequisites.md).

# What do I need to have my own Navixy instance?

Provision a server, obtain a license, assemble a technician team, register domain names. Optional: SSL certificates and SMS/email gateways

## Question

I want my own hosted Navixy instance. What do I need?

## Answer

You'll need the following:

* Ready-to-use **server** to install the Navixy On-Premise solution on. This can be a physical or virtual server, either deployed locally in your data center or running in a cloud provider (Amazon Web Services, MS Azure, GCP, etc.). The server must meet the technical requirements published on Navixy website.
* **License** to use Navixy On-Premise solution. You will need to contact the Navixy sales team to request the license.
* Competent **technician team** to maintain your server and infrastructure. Although Navixy guarantees reliability of its software, with local hosting, you assume all risks associated with server and third-party applications.
* Registered **domain name or names**. Unlike Navixy PaaS, the On-Premise solution does not have any "basic" domain setting, and without a proper DNS record, your platform is accessible only via an IP address.

Other options are not mandatory, but highly recommended for the best customer experience. These are:

* SSL certificates for your domain security.
* Email and SMS gateways for message exchange and notification delivery.

## Links

* [Requirements](/docs/on-premise/on-premise/how-to-guide/requirements.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/prerequisites.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.