> 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/2025.1/setup-and-upgrade/overview.md).

# Overview

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

## Try out SonarQube Server <a href="#try-out-sonarqube-server" id="try-out-sonarqube-server"></a>

To try out the SonarQube Server platform, follow the [Try out SonarQube Server](/sonarqube-server/2025.1/try-out-sonarqube.md) guide.

## Install a production instance <a href="#install-a-production-instance" id="install-a-production-instance"></a>

To install a production instance, read the [SonarQube Server host](/sonarqube-server/2025.1/setup-and-upgrade/installation-requirements/server-host.md), and then follow the [Introduction](/sonarqube-server/2025.1/setup-and-upgrade/install-the-server/introduction.md).

## After the installation <a href="#after-the-installation" id="after-the-installation"></a>

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

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/2025.1/instance-administration/user-management/user-permissions.md#global-permissions) for more information.

## Upgrade your production instance <a href="#upgrade-your-production-instance" id="upgrade-your-production-instance"></a>

To upgrade your production instance, read the [Overview](/sonarqube-server/2025.1/server-update-and-maintenance/update/roadmap.md) and the relevant, version-specific upgrade notes.


---

# 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/2025.1/setup-and-upgrade/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.