# Introduction

## Developer and Enterprise editions <a href="#developer-and-enterprise-editions" id="developer-and-enterprise-editions"></a>

* [Server components](/sonarqube-server/server-installation/server-components-overview.md)
* [Server host requirements](/sonarqube-server/server-installation/server-host-requirements.md)
* [Networking requirements](/sonarqube-server/server-installation/networking-requirements.md)
* **Pre-installation steps**:
  * [On Linux systems](/sonarqube-server/server-installation/pre-installation/linux.md)
  * [On Unix-based systems](/sonarqube-server/server-installation/pre-installation/unix.md)
  * [On macOS systems](/sonarqube-server/server-installation/pre-installation/macos.md)
* **Installing**:
  * [From ZIP file](/sonarqube-server/server-installation/from-zip-file.md)
  * [From Docker image](/sonarqube-server/server-installation/from-docker-image.md)
  * [On Kubernetes or OpenShift](/sonarqube-server/server-installation/on-kubernetes-or-openshift.md)
* **Post-installation**\
  By default, the `sonar-users` group has the **Execute Analysis** global permission, which means that its users can see the branch status of any project, even if they don’t have explicit permissions for it. We recommend that after your trial, you review all global permissions and ensure they comply with your company policy. See [Managing permissions](/sonarqube-server/instance-administration/user-management/user-permissions.md#global-permissions) for more information.
* **Network security:**
  * [Reverse proxy and network security](/sonarqube-server/server-installation/network-security/securing-behind-proxy.md)
  * [Network rules](/sonarqube-server/server-installation/network-security/network-rules.md)
* **Reference architectures:**
  * [Up to 10 M LOC](/sonarqube-server/server-installation/reference-architectures/up-to-10m-loc.md)
  * [Up to 50 M LOC](/sonarqube-server/server-installation/reference-architectures/up-to-50m-loc.md)

## Data Center Edition <a href="#data-center-edition" id="data-center-edition"></a>

* [DCE topology](/sonarqube-server/server-installation/data-center-edition/dce-topology.md)
* [Installation requirements](/sonarqube-server/server-installation/data-center-edition/installation-requirements.md)
* [Pre-installation steps](/sonarqube-server/server-installation/data-center-edition/pre-installation.md)
* **Installing:**
  * [Installing from ZIP file](/sonarqube-server/server-installation/data-center-edition/from-zip-file.md)
  * [Installing on Kubernetes or Openshift](/sonarqube-server/server-installation/data-center-edition/on-kubernetes-or-openshift.md)
* **Network security:**
  * [Securing behind a proxy](/sonarqube-server/server-installation/data-center-edition/network-security/securing-behind-proxy.md)
  * [Elasticsearch security features](/sonarqube-server/server-installation/data-center-edition/network-security/elasticsearch-security-features.md)
  * [Network rules](/sonarqube-server/server-installation/data-center-edition/network-security/network-rules.md)

## Database <a href="#database" id="database"></a>

* [Installing database](/sonarqube-server/server-installation/installing-the-database.md)

## Next steps <a href="#next-steps" id="next-steps"></a>

After your server is up and running, you’ll need to install one or more Sonar scanners on the machines where the analysis will be performed. See [Project analysis setup](/sonarqube-server/analyzing-source-code/overview.md).

## Related online learning

* <i class="fa-desktop">:desktop:</i> [Getting started with Sonar: Onboarding essentials](https://www.sonarsource.com/learn/course/core-concepts/71f50722-68bc-4504-bec9-cc269ed96f36/getting-started-with-sonar-onboarding-essentials)


---

# Agent Instructions: 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://docs.sonarsource.com/sonarqube-server/server-installation/introduction.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.
