Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by SonarSource Sàrl · www.sonarsource.com

Compare with Codacy → Report an error on this page Is this your product? →

Link to this page

SonarQube: AI-assisted analysis on whats-best.ai SonarQube: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

SonarQube at a glance

Vendor
SonarSource Sàrl
Headquarters
Incorporated in Switzerland source, captured 6 Nov 2026
Data hosting
In the EU by default source, captured 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates SonarQube 3.5/5, the mean of 6 judges. SonarQube — SonarSource Sàrl's code security and quality platform, in cloud, self-managed or IDE editions — takes top marks, 8, on code analysis, trust and compliance, and sovereignty. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

SonarQube alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Platform Engineer

Weighted verdict

Platform engineer at an insurer in Hanover who runs a self-managed GitLab and Jenkins for 300 developers inside the company network; source code may not leave it. Wants a self-hosted edition or a scanner that runs in the pipeline and sends only results, SAML and SCIM from Entra ID, an API to roll scan settings out to 900 repositories, SARIF output, audit logs, and upgrades that do not break the pipelines.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Platform Engineer

Panel median The Platform Engineer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Platform Engineer
Code analysis (SAST & code quality) 4 of 5 4 of 5
Dependencies (SCA), licences & secrets 3.5 of 5 3.5 of 5
Developer workflow, quality gates & fixes 3.5 of 5 3.5 of 5
Platforms, deployment & administration 3.5 of 5 3.5 of 5
Source-code handling, security & compliance 4 of 5 4 of 5
European sovereignty 4 of 5 4 of 5
Pricing transparency 2.5 of 5 2.5 of 5

Code analysis (SAST & code quality)

How this is scored

What the tool finds in the company's own code: static application security testing with data-flow and taint analysis across functions and files, the languages and frameworks covered and at what depth, the rule sets (OWASP Top 10, CWE, custom rules), bugs and code smells, duplication, cyclomatic and cognitive complexity, maintainability and technical-debt measures, test coverage import, infrastructure-as-code checks, and how false positives are measured and kept down.

0 — Does not analyse source code; a dependency, secret or runtime scanner only, or a different kind of product.

3 — Pattern-based rules or linters for a handful of languages; data-flow analysis, the rule list, quality metrics and false-positive handling are basic or not described.

5 — SAST for the common languages (Java, JavaScript/TypeScript, Python, C#, Go, PHP) with the rule list published and mapped to OWASP and CWE, bugs and code smells, duplication and complexity metrics, coverage import, and custom rules or rule configuration documented.

8 — Cross-file taint analysis with the supported frameworks listed per language, a rule language customers can write in, infrastructure-as-code checks, maintainability or code-health scores over time, false-positive rates or benchmarks published, and each finding explained with its data flow and a fix.

10 — Analysis a large polyglot codebase relies on: deep interprocedural analysis across many languages with the depth stated per language, independent benchmark results, quality and security trends per team and hotspot, and every rule documented with examples and its precision.

Report an error

The Platform Engineer

Taint analysis is real and documented: SQL injection tracked from source to sink with up to twenty flows shown, deeper taint analysis for Java and C#, and custom sources, sanitizers, validators and sinks configurable for our in-house frameworks, alongside custom rule development, IaC scanning for Terraform, Kubernetes and Ansible, and mappings to OWASP Top 10, CWE Top 25, PCI DSS and the EU Cyber Resilience Act. Quality measures include bugs, code smells, duplication, coverage and technical debt, and findings come with fix suggestions. Precision is only quantified for secrets detection (under 5% false positives), not for the SAST engine itself. 2 3 4 5 21

Report an error

Dependencies (SCA), licences & secrets

How this is scored

What comes from outside or should never be committed: software composition analysis of direct and transitive dependencies with the ecosystems and lockfiles supported, the vulnerability database and how quickly it is updated, reachability analysis, licence detection and policies, SBOM export (CycloneDX, SPDX), malicious and typosquatted package detection, end-of-life components, automatic upgrade pull requests, container image scanning, and secret detection in code and git history with the number of detectors, validity checks and revocation guidance.

0 — No dependency or secret scanning of any kind.

3 — Known-vulnerability alerts for dependencies in one or two ecosystems or a basic secret pattern check; transitive dependencies, licences, SBOMs and git history are basic or not described.

5 — SCA for the main ecosystems including transitive dependencies, licence detection with policies, SBOM export in a standard format, upgrade suggestions or pull requests, and secret detection in commits with the detector list described.

8 — Reachability analysis that shows whether vulnerable code is called, malicious-package detection, the vulnerability database and its sources documented, end-of-life components flagged, secrets checked for validity and scanned across the full git history, and push protection that stops a secret before it lands.

10 — Supply-chain coverage a regulated software maker can file: every ecosystem the company builds with, reachability for each, SBOM and VEX output for customers, licence obligations explained per licence, secrets found outside git (tickets, chat, containers) with automated revocation, and the database's coverage and latency evidenced.

Report an error

The Platform Engineer

SCA reads manifests and lock files across every supported package manager and reports CVEs, malware and prohibited licences, with reachability analysis for Java/Kotlin, Python and C#/VB.NET and SBOM export in both CycloneDX and SPDX; secrets detection runs locally with pre-commit and pre-push hooks that block a secret before it lands, an allowlist, and custom secret rules on the Server edition. I found no public information on the vulnerability database's sources and update cadence, end-of-life component flagging, validity checks for secrets, or scanning of the full git history. 3 5 22 23

Report an error

Developer workflow, quality gates & fixes

How this is scored

Whether developers see and act on the findings where they work: pull and merge request comments and status checks, quality gates that block a merge on new issues, a focus on new code against a baseline, IDE plugins with the same rules as the server, CLI and CI integrations (GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, Bitbucket Pipelines), pre-commit hooks, triage, suppression and ignore rules with reasons, deduplication, fix suggestions and AI autofix with the model behind it, and scan times.

0 — Findings only in a separate report; no pull request, IDE or CI integration.

3 — A CI step or a dashboard of findings; pull request comments, gates, IDE plugins and triage are basic or not described.

5 — Pull or merge request comments and status checks on the common platforms, a configurable quality gate that can fail a build, a new-code baseline, IDE plugins for the common editors, CI integrations documented, and findings that can be ignored or marked as false positives.

8 — IDE results that match the server rules, gates per branch or project with thresholds per severity, pre-commit or push-time checks, deduplicated findings across tools, fix suggestions or AI autofix as a reviewable change with the model provider stated, and typical scan times documented.

10 — A workflow that keeps noise low on a large team: findings routed to the owning team, every suppression audited with a reason and expiry, autofix with its acceptance rates published, and the gate's behaviour on every supported platform documented with its limits.

Report an error

The Platform Engineer

This maps to my pipelines: GitLab CI/CD and Jenkins integration are documented concretely (branch and merge-request auto-detection from the Developer edition, quality-gate wait and timeout parameters that fail the pipeline, a Jenkins extension showing the gate as a badge and widget on the job page), merge-request decoration is supported, IDE plugins run in connected mode with the same engine as the server, pre-commit hooks exist, and issues can be accepted or marked safe with justification. I found no public information on deduplication of findings across tools, the model behind the AI fixes, or typical scan times. 6 8 9 22 24 25

Report an error

Platforms, deployment & administration

How this is scored

How the tool fits the company: the code hosts supported (GitHub, GitLab, Bitbucket, Azure DevOps) cloud and self-managed, a self-hosted or on-premise edition or a scanner that runs inside the customer's network, a documented REST API and webhooks, issue tracker integrations (Jira), single sign-on (SAML or OIDC) and SCIM, roles and permissions per project and team, portfolio reports across repositories, audit logs, export of findings (SARIF, CSV), and partner or multi-organisation accounts.

0 — One repository at a time with no integrations and no administration.

3 — A web dashboard and one code host; the API, roles, SSO and self-hosted options are basic or not described.

5 — GitHub, GitLab and Bitbucket or Azure DevOps supported, a documented REST API, Jira integration, roles per organisation and project, single sign-on, reports across repositories, and export of findings in a standard format.

8 — Self-managed code hosts supported, a self-hosted edition or an in-network scanner documented, SCIM provisioning, audit logs, granular roles per team, portfolio dashboards with trends, SARIF import and export, and webhooks for findings.

10 — Administration that scales across many teams and business units: every setting reachable by API with parity stated, an air-gapped deployment documented, SSO enforced with SCIM, audit logs exportable to a SIEM, and multi-organisation or partner management.

Report an error

The Platform Engineer

The self-managed Server edition documented for operation inside my perimeter, including air-gapped, plus SSO and SCIM in the enterprise tier, webhooks at project and global level with HMAC-SHA256 verification, Jira Cloud, portfolios, and SARIF import cover most of my checklist. I found no public information on audit logs, SARIF export of findings, granular roles per team, or whether every scan setting is reachable by API for rollout to 900 repositories — the last two are what I would need proven before signing. 2 6 9 24 25 26 27 29

Report an error

Source-code handling, security & compliance

How this is scored

What the vendor does with the customer's source code and how it holds up in an audit: whether code leaves the customer's network or only results do, where and how long code and findings are stored, whether code or findings are used to train AI models and how to opt out, encryption, the vendor's own certifications (ISO 27001, SOC 2) with their scope, a stated availability or SLA and a public status page, audit logs, and reports mapped to OWASP, CWE, PCI DSS, ISO 27001 or the EU Cyber Resilience Act.

0 — Nothing on how source code is handled, secured or retained.

3 — A security page with general claims; code retention, AI training, certifications and the status page are basic or not described.

5 — How source code is accessed and whether it is stored is described, encryption in transit and at rest, SOC 2 or ISO 27001 stated, a public status page, a statement on whether code trains AI models, and compliance reports mapped to OWASP or CWE.

8 — Code retention periods stated, an option where code never leaves the customer's network, AI features documented with their model provider and an opt-out, certifications with scope and reports available on request, an SLA published, and reports mapped to several standards including PCI DSS or the Cyber Resilience Act.

10 — Source-code handling evidenced end to end: a data-flow diagram of what is sent where, zero retention options, independent audits published with scope, AI processing that can run on the customer's own models, and compliance evidence an auditor can export without asking the vendor.

Report an error

The Platform Engineer

Retention is stated (only the code of the most recent scans is stored, snapshots kept up to one year, customer-controlled deletion at any time), encryption in transit (TLS 1.2 minimum) and at rest (AES-256) are documented, ISO 27001:2022 and SOC 2 Type II are held with scope covering Server, Cloud and IDE, penetration tests run annually with executive summaries published, and findings map to OWASP, CWE, PCI DSS and the EU Cyber Resilience Act. With the self-hosted edition my code never leaves the network at all. I found no public information on the model provider behind the AI features or an opt-out regarding AI training. 2 11 16 19 21 28 29

Report an error

European sovereignty

How this is scored

Who the contracting entity and the parent company are, where source code, findings, SBOMs, account and usage data are stored and processed, and who the subprocessors are (hosting, AI models used for autofix and triage, vulnerability data sources, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Public vulnerability databases and package registries the scanner queries are part of what the product does and are not counted against it; where the customer's code and findings are stored and who processes them is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (AI models, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps code and findings on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The Platform Engineer

For my deployment the decisive fact is the self-hosted, air-gapped Server edition that keeps code and findings on our own servers; for the cloud, Frankfurt on AWS is the default region with EU backups, the contracting entity SonarSource Sàrl sits in Switzerland with a group parent domiciled in the United States, a data processing agreement is published with a subprocessor list and fourteen days' notice of changes, and standard contractual clauses are in place. The captured pages do not show each subprocessor's location. 2 11 15 18 19

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per developer, contributor, committer or line of code and per plan, how contributors are counted, what the free tier and open-source plan include, which scanners (SAST, SCA, secrets, containers) and features (SSO, self-hosting, AI autofix, compliance reports) cost extra, limits on repositories, scans or lines of code, minimum seats, monthly versus annual terms, and VAT.

0 — No public prices at all; every customer is a sales call.

3 — A starting price exists, but how developers or lines of code are counted and what the add-ons cost is unclear.

5 — Plans are public with their price per developer or per lines of code and main inclusions, but at least one commonly needed piece (SSO, self-hosting, an extra scanner, AI autofix or the enterprise tier) is unpriced or "contact sales".

8 — Every plan priced publicly with its counting rule (active contributors, lines of code) explained, scanners and add-ons priced, limits on repositories and scans stated, a free or open-source tier with its limits, and monthly and annual terms and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of developers, repositories and lines of code, with every scanner, add-on, self-hosted licence and support level priced and the cancellation and data-export terms published.

Report an error

The Platform Engineer

The cloud Team plan starts at $34 per month with a free tier for private projects up to 50k lines of code, the open-source tier is free, and the Server counting rule (largest branch analysed, not cumulative on re-analysis) is published. But the Server plan prices, the Enterprise tier (custom, contact sales) and the Advanced Security subscription my Jenkins pipelines would need are unpriced, and VAT treatment is not stated — I cannot compute an annual cost for my estate from the public pages. 1 9 10 17

Report an error

European sovereignty — proven facts

3 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location EU by default unverified
Why unverified?

US-based hosting (AWS us-east-1) exists for some customers, and the privacy notice says personal data may be stored and processed in the US and other non-EU jurisdictions; the statement covers SonarQube Cloud only, not self-hosted SonarQube Server.

2/4 pts 11 Report an error
Hosting options Self-hostable unverified
Why unverified?

Self-hosting applies to the SonarQube Server product only; SonarQube Cloud itself is a SaaS solution (hosted in AWS with EU hosting by default), and both self-hosted and EU-region options coexist, with self-hosting taking precedence.

1/1 pts 10 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about SonarQube

Is SonarQube European?

Partly. whats-best.ai classifies SonarQube as EU origin, foreign-owned. Its vendor, SonarSource Sàrl, is incorporated in Switzerland, per the vendor’s page captured 6 Nov 2026.

Where does SonarQube store data?

SonarQube stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 6 Nov 2026.

Does SonarQube have a free plan?

Yes. SonarQube has a free plan, per the vendor’s page captured 6 Nov 2026.

What are the best alternatives to SonarQube?

As of 19 Nov 2026, the panel rates Aikido Security (3.5/5), Endor Labs (3.5/5) and Qodana (3.5/5) highest among the other 18 Code Security & Quality (SAST/SCA) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Aikido Security (EU-Made, Belgium). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: SonarQube alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (29)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.sonarsource.com Checked 6 Nov 2026 Details →
  2. 2 Features page (SonarQube) www.sonarsource.com Checked 6 Nov 2026 Details →
  3. 3 Features page (code security) www.sonarsource.com Checked 6 Nov 2026 Details →
  4. 4 Features page (secrets detection) www.sonarsource.com Checked 6 Nov 2026 Details →
  5. 5 Features page (SCA) www.sonarsource.com Checked 6 Nov 2026 Details →
  6. 6 Integrations page www.sonarsource.com Checked 6 Nov 2026 Details →
  7. 7 Documentation (SonarQube Server) docs.sonarsource.com Checked 6 Nov 2026 Details →
  8. 8 Documentation (SonarQube Cloud) docs.sonarsource.com Checked 6 Nov 2026 Details →
  9. 9 Pricing page www.sonarsource.com Checked 6 Nov 2026 Details →
  10. 10 Pricing page (SonarQube Server) www.sonarsource.com Checked 6 Nov 2026 Details →
  11. 11 Security / trust page www.sonarsource.com Checked 6 Nov 2026 Details →
  12. 12 Trust centre trust.sonarsource.com Checked 6 Nov 2026 Details →
  13. 13 Public status page status.sonarqube.com Checked 6 Nov 2026 Details →
  14. 14 About page www.sonarsource.com Checked 6 Nov 2026 Details →
  15. 15 Legal documents www.sonarsource.com Checked 6 Nov 2026 Details →
  16. 16 Terms of service (SonarQube Cloud) www.sonarsource.com Checked 6 Nov 2026 Details →
  17. 17 Terms of service (SonarQube Server) www.sonarsource.com Checked 6 Nov 2026 Details →
  18. 18 Privacy policy www.sonarsource.com Checked 6 Nov 2026 Details →
  19. 19 Data processing agreement (dpa) www.sonarsource.com Checked 6 Nov 2026 Details →
  20. 20 Code analysis (SAST & code quality) — found from sitemap docs.sonarsource.com Checked 6 Nov 2026 Details →
  21. 21 Code analysis (SAST & code quality) — found from sitemap docs.sonarsource.com Checked 6 Nov 2026 Details →
  22. 22 Dependencies (SCA), licences & secrets — found from sitemap docs.sonarsource.com Checked 6 Nov 2026 Details →
  23. 23 Dependencies (SCA), licences & secrets — found from sitemap docs.sonarsource.com Checked 6 Nov 2026 Details →
  24. 24 Developer workflow, quality gates & fixes — found from sitemap docs.sonarsource.com Checked 6 Nov 2026 Details →
  25. 25 Developer workflow, quality gates & fixes — found from sitemap docs.sonarsource.com Checked 6 Nov 2026 Details →
  26. 26 Platforms, deployment & administration — found from sitemap docs.sonarsource.com Checked 6 Nov 2026 Details →
  27. 27 Platforms, deployment & administration — found from sitemap docs.sonarsource.com Checked 6 Nov 2026 Details →
  28. 28 Source-code handling, security & compliance — found from sitemap www.sonarsource.com Checked 6 Nov 2026 Details →
  29. 29 Source-code handling, security & compliance — found from sitemap docs.sonarsource.com Checked 6 Nov 2026 Details →