> 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.3/setup-and-upgrade/install-the-server/introduction.md).
# Introduction
Read this before starting the SonarQube Server 10.3 installation.
{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.3 documentation. For a list of all 10.3 pages, see the [SonarQube Server 10.3 page index](https://353248219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl622HnhaCz6xSuy6XTfl%2Fuploads%2FqlWPhmFHjpw7Xdej9zkF%2Fsonarqube-server-10.3-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.3 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}
{% hint style="info" %}
We recommend installing SonarQube Server from a [Docker image](https://hub.docker.com/_/sonarqube) or [Helm chart](https://artifacthub.io/packages/helm/sonarqube/sonarqube) (Kubernetes/OpenShift). These methods make it easier to update to newer versions and to operate your instance. Install from the ZIP file only if neither of those options is feasible for your environment.
{% endhint %}
The server installation section describes a single-node SonarQube Server instance from the ZIP file or from the Docker image. For a Kubernetes installation, see [Deploy SonarQube Server on Kubernetes](/sonarqube-server/10.3/setup-and-upgrade/deploy-on-kubernetes/deploy-sonarqube-on-kubernetes.md). For details on clustered setup, see [Install the server as a cluster](/sonarqube-server/10.3/setup-and-upgrade/install-the-server-as-a-cluster.md).
## Installation roadmap
Proceed as follows to install SonarQube Server on server side:
1. Install the [Installing the database](/sonarqube-server/10.3/setup-and-upgrade/install-the-server/installing-the-database.md).
2. Install the SonarQube Server instance and perform a basic setup. You can install the server either [Installing SonarQube Server from the Docker image](/sonarqube-server/10.3/setup-and-upgrade/install-the-server/installing-sonarqube-from-docker.md) or [Installing SonarQube Server from the ZIP file](/sonarqube-server/10.3/setup-and-upgrade/install-the-server/installing-sonarqube-from-zip-file.md).
3. If necessary, perform [Advanced installation features](/sonarqube-server/10.3/setup-and-upgrade/install-the-server/advanced-installation-features.md).
## Instance components
A SonarQube Server instance comprises three components:
SQ instance components
1. The SonarQube Server instance running the following processes:
* A web server that serves the SonarQube Server user interface.
* A search server based on Elasticsearch.
* The compute engine in charge of processing code analysis reports and saving them in the SonarQube Server database.
2. The database to store the following:
* Metrics and issues for code quality and security generated during code scans.
* The SonarQube Server instance configuration.
3. One or more scanners running on your build or continuous integration servers to analyze projects.
## Hosts and locations
For optimal performance, the SonarQube Server instance and database should be installed on separate hosts, and the server host should be dedicated. The server and database hosts should be located on the same network.
All hosts must be time-synchronized.
---
# 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.3/setup-and-upgrade/install-the-server/introduction.md?ask=&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.