Development
SonarQube on a VPS: analyse your code's quality and security on your own server — bugs, vulnerabilities, quality gate and CI integration.
In validation
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
The pipeline runs the analysis after the tests; if the quality gate fails, the release waits for the fix.
An agency keeps one dashboard per project: open issues, duplicated code and coverage, and how they change from one version to the next.
Every issue links to a documented rule with an example: junior developers learn by fixing their own code.
Guide
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.
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.
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.
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.
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
The memory required and the VPS that covers it, on every card.
Check it: the “Recommended VPS” line of each card
You administer the system over SSH; your data stays on your VPS.
Check it: the “What is installed” section of each page
The applications are open source: your only cost is the VPS that runs them.
Check it: in the cart, no line for the application
Open-source continuous integration and delivery server: Jenkinsfile pipelines, over 2,000 plugins, builds triggered by your Git repositories.
DevelopmentYour own GitHub, self-hosted in minutes. Full Git platform with CI/CD (Gitea Actions), package registry and team permissions — without usage-based billing.
DevelopmentAll-in-one Git forge with visual CI/CD, Kanban boards and a package registry — one container, no per-developer billing.

Dedicated Cloud VPS — IPv4 included, server in Europe, support included. Your data never leaves your server.
SonarQube also runs on a dedicated server, when models or data outgrow a VPS. See dedicated servers