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

# Overview

Find the general hardware and software requirements for the SonarQube Server 10.8 and database hosts for the Community, Developer, and Enterprise Editions.

{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.8 documentation. For a list of all 10.8 pages, see the [SonarQube Server 10.8 page index](https://312504542-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiJj3TXBdWssTGGg8qK5I%2Fuploads%2FmeJ1nVNGPezOurNrTy4A%2Fsonarqube-server-10.8-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.8 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}

This section describes general hardware and software requirements and database hosts for the SonarQube Server and SonarQube Community Build.

For the requirements regarding the Data Center Edition, see [Data Center Edition (DCE)](/sonarqube-server/10.8/setup-and-upgrade/install-the-server-as-a-cluster.md).

{% hint style="info" %}
We recommend that for production installation, the database used by SonarQube Server is hosted on a machine that is physically separate from the SonarQube Server host, with low latency between both hosts.
{% endhint %}

{% hint style="warning" %}
You cannot deploy SonarQube Server with Azure App Service because Azure App Service does not allow the [On Linux systems](/sonarqube-server/10.8/setup-and-upgrade/pre-installation/linux.md). Using Azure App Service may cause issues that will ultimately make SonarQube Server unreliable and unsuitable for enterprise production use.
{% endhint %}

See:

* [SonarQube Server host](/sonarqube-server/10.8/setup-and-upgrade/installation-requirements/server-host.md)
* [Database](/sonarqube-server/10.8/setup-and-upgrade/installation-requirements/database-requirements.md)
* **Reference architectures:**
  * [Up to 10M LOC](/sonarqube-server/10.8/setup-and-upgrade/reference-architectures/up-to-10m-loc.md)
  * [Up to 50 M LOC](/sonarqube-server/10.8/setup-and-upgrade/reference-architectures/up-to-50m-loc.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://docs.sonarsource.com/sonarqube-server/10.8/setup-and-upgrade/installation-requirements/overview.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.