> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/installation-setup.md).

# On-Site Setup

ngSurvey can be installed on-premise on your own servers or on your own infrastructure. This way all the important data that you collect using your surveys or forms remains exclusively within your company boundaries on your own servers.

ngSurvey can be installed in just a few minutes on any kind of platform ranging from Linux, Docker containers or Windows based servers.

* [**Enterprise Edition**](/installation-setup/installation.md) provides an advanced version that will meet all enterprise related needs.

Requirements to run ngSurvey locally on your own infrastructure are 

* Windows Server 2016+ or Linux or Azure or AWS or any host able to run a Docker image.
* SQL Server 2016+ or SQL Server Express or Oracle MySQL or PostgreSQL to host the database.
* .NET 10

{% hint style="info" %}
To learn more about the difference of both versions you may check online our full [feature list](https://www.ngsurvey.com/home/features).
{% endhint %}


---

# 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://docs.ngsurvey.com/installation-setup.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.