> 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/server-installation/introduction.md).

# Introduction

This section explains how to install and setup your SonarQube Server 2026.5.

{% hint style="warning" %}
Installing SonarQube Server from the ZIP file is deprecated. It's still supported, but support will be removed in a future release, so consider the [Docker image](https://hub.docker.com/_/sonarqube) or the [Helm chart](https://artifacthub.io/packages/helm/sonarqube/sonarqube) instead. See the [deprecation policy](/sonarqube-server/server-update-and-maintenance/maintenance/deprecations/deprecation-policy.md) for details.

The agentic features run as containers, so they have no ZIP equivalent. You can keep SonarQube Server on the ZIP file and deploy their containers alongside it. See [Deploying AI agents](/sonarqube-server/server-installation/ai-agents.md).
{% endhint %}

## 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 Docker image](/sonarqube-server/server-installation/from-docker-image.md)\
    To add the AI features, see [Deploying with Docker Compose](/sonarqube-server/server-installation/ai-agents/deploying-with-docker-compose.md).
  * [On Kubernetes or OpenShift](/sonarqube-server/server-installation/on-kubernetes-or-openshift.md)\
    To add the AI features, see [Deploying with the Helm chart](/sonarqube-server/server-installation/ai-agents/customizing-helm-chart.md). On OpenShift, the agent runtimes are sandboxed with Kata Containers.
  * [From ZIP file](/sonarqube-server/server-installation/from-zip-file.md) ([deprecated](/sonarqube-server/server-update-and-maintenance/release-notes.md#deprecations-and-removals))\
    The AI features run as containers, so they have no ZIP equivalent. You can run SonarQube Server from the ZIP file and deploy their containers alongside it.
* **AI features** (optional, Enterprise and Data Center editions)\
  The Agent Orchestrator, the agent runtimes, and Vortex analysis run as containers alongside SonarQube Server, and they need shared storage that you provision. Each agent requires a separate subscription. See [Deploying AI agents](/sonarqube-server/server-installation/ai-agents.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)
  * [Agentic features architecture](/sonarqube-server/server-installation/reference-architectures/agentic-features-architecture.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:**
  * [From Docker image](/sonarqube-server/server-installation/data-center-edition/from-docker-image.md)
  * [Installing on Kubernetes or Openshift](/sonarqube-server/server-installation/data-center-edition/on-kubernetes-or-openshift.md)
  * [Installing from ZIP file](/sonarqube-server/server-installation/data-center-edition/from-zip-file.md) ([deprecated](/sonarqube-server/server-update-and-maintenance/release-notes.md#deprecations-and-removals))
* **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
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/server-installation/introduction.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.