Development

SonarQube

SonarQube on a VPS: analyse your code's quality and security on your own server — bugs, vulnerabilities, quality gate and CI integration.

In validation

About SonarQube

SonarQube Community Build is SonarSource's open-source static analysis platform (LGPL-3.0 licence). Each analysis started from your CI or your workstation inspects code in about twenty languages — Java, JavaScript and TypeScript, Python, PHP, C#, Go, Kotlin, as well as Terraform and Dockerfile — and reports bugs, vulnerabilities, security hotspots, duplicated code and test coverage.

The quality gate decides: an analysis that introduces new issues fails, and your pipeline can stop before deployment. Your source code stays on your VPS. The ServOrbit installation replaces the admin account's factory password on first start, requires a login to see anything and publishes the instance over HTTPS.

What gets installed

Ready when the VPS starts

Compatible OS
Choice of Linux distributions
Application
SonarQube
Tech stack
DockerJavaPostgreSQLElasticsearch
Minimum RAM
4 GB minimum
Minimum CPU
2 vCPU
Default port
8122
Access
root over SSH

Key features

  • Bugs, vulnerabilities and security hotspots — every issue is explained, with its rule and a fix example.
  • About twenty languages — Java, JavaScript and TypeScript, Python, PHP, C#, Go, Kotlin, Terraform, Dockerfile and more.
  • Quality gate — an analysis that degrades new code fails, and your pipeline can stop before deployment.
  • CI integration — an analysis token and the official scanner are all you need for GitHub Actions, GitLab CI or Jenkins.
  • Duplicated code and test coverage — your tests' coverage reports are read and tracked over time.
  • Your code stays with you — the analysis and its results are stored on your VPS, in PostgreSQL.

When to use this solution?

Block a deployment on fragile code

The pipeline runs the analysis after the tests; if the quality gate fails, the release waits for the fix.

Track a client project's technical debt

An agency keeps one dashboard per project: open issues, duplicated code and coverage, and how they change from one version to the next.

Train a team in good practices

Every issue links to a documented rule with an example: junior developers learn by fixing their own code.

Guide

Deploy SonarQube on your VPS

  1. Create the VPS and choose the address

    Order an Ubuntu 24.04 VPS with at least 4 GB of RAM and 2 vCPUs. SonarQube requires a domain: your pipelines send their analyses to it over HTTPS, and the instance writes that address into its links. It opens on a subdomain of one of your domains, or on the VPS's free subdomain (sonarqube.{dns_slug}.servorbit-dns.com), HTTPS included. No need to buy a domain name.

  2. Install SonarQube from the Marketplace

    In your client area, select SonarQube, choose the address and click Install. The script deploys the official image with PostgreSQL, replaces the admin account's factory password with a generated one, declares the instance's public address and configures the nginx reverse proxy over HTTPS. The first start takes two to five minutes.

  3. Log in for the first time

    Open https://your-domain and log in with the user admin and the password shown in your client area. The factory password admin/admin no longer works. Then create your team's accounts under Administration, Security, Users.

  4. Create an analysis token

    From your account, menu My Account, Security, generate a token of type Global Analysis Token. Store it in your CI secrets as SONAR_TOKEN, with the instance address as SONAR_HOST_URL.

  5. Run a first analysis

    From the root of a project, run the official scanner: `bash docker run --rm -e SONAR_HOST_URL=https://your-domain -e SONAR_TOKEN=<token> \ -v "$PWD:/usr/src" sonarsource/sonar-scanner-cli -Dsonar.projectKey=my-project` The project appears in SonarQube with its issues and the quality gate verdict.

Proof

What we promise, and how to check it

  • The recommended size, for every application

    The memory required and the VPS that covers it, on every card.

    Check it: the “Recommended VPS” line of each card

  • Root access, on your server

    You administer the system over SSH; your data stays on your VPS.

    Check it: the “What is installed” section of each page

  • You pay for the VPS, not the software

    The applications are open source: your only cost is the VPS that runs them.

    Check it: in the cart, no line for the application

Frequently asked questions

Questions about SonarQube

← Back to DevelopmentAll applications
SonarQube Cloud is the service hosted by SonarSource: your code is sent there. SonarQube Community Build is the open-source edition you host yourself: the code and the results stay on your VPS. It analyses each project's main branch; branch and pull request analysis belong to the commercial editions.

Activate SonarQube on your infrastructure.

Dedicated Cloud VPS — IPv4 included, server in Europe, support included. Your data never leaves your server.

All applications

SonarQube also runs on a dedicated server, when models or data outgrow a VPS. See dedicated servers