As of 6 Nov 2026, the panel rates Codacy 3.5/5 and SonarQube 3.5/5 in Code Security & Quality (SAST/SCA). Weighted by what each judge cares about, 0 of the 6 judges pick Codacy and 6 pick SonarQube. SonarQube scores higher on 7 of 7 criteria (Code analysis (SAST & code quality), European sovereignty, Source-code handling, security & compliance, plus 4 more). Provenance — Codacy: EU-Made, Portugal; SonarQube: EU origin, foreign-owned, Switzerland. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
SonarQube's mean is higher on each of the seven criteria; Codacy leads on none. The widest gaps are code analysis (8.0 vs 6.2), trust and compliance (8.0 vs 7.0) and sovereignty (8.0 vs 6.7), with 6 judges leaning SonarQube and 0 ties on each. The benches sit closest on developer workflow (7.0 vs 7.2, 5 ties) and integration and admin (6.8 vs 7.0, 5 ties), with 1 lean to SonarQube apiece; pricing transparency splits 3 leans to 3 ties and is the lowest mean on both sides (Codacy 4.8, SonarQube 5.3). SonarQube's weighted total is higher on each judge row: 7.2 vs 6.5, 7.6 vs 6.5, 7.3 vs 6.4, 7.3 vs 6.4, 7.5 vs 6.9, 7.3 vs 6.1. Judges credit SonarQube's sovereignty mark to EU hosting by default on AWS Frankfurt and a self-managed, air-gapped edition; the captured sovereignty attributes read "unknown" for both products.
Choose Codacy if
Your procurement policy requires an EU-made vendor: Codacy's provenance is listed as EU-made (Qamine Portugal S.A.), while SonarSource Sàrl is listed as European and foreign-owned.
Your shortlist turns on developer workflow and integration and admin: 5 of 6 judges tied on both (means 7.0 vs 7.2 and 6.8 vs 7.0), so the scoring separates the two least on the criteria that matter most to you.
You need a published per-developer entry price: Codacy's Team plan is public at Starting at $18 Per dev/mth, and pricing transparency tied at 3 leans to 3.
Your compliance scope includes PCI DSS: Codacy's verdict lists mappings to SOC 2, ISO 27001 and PCI DSS as part of its flat-7 trust and compliance mark; we found no public information on PCI DSS mappings for SonarQube.
You require a written AI position: Codacy's verdict documents enterprise OpenAI and Google Gemini instances, no training on customer code, secrets redacted before snippets are sent, and per-repository or full opt-out; the SonarQube verdict reports no public information on the model behind the AI fixes.
Choose SonarQube if
You need taint analysis tracked from source to sink with configurable sources, sanitizers and sinks: code analysis reads 8.0 vs 6.2, with 6 judges leaning SonarQube and 0 ties.
Your policy requires EU hosting by default and a self-managed, air-gapped option: judges credit AWS Frankfurt hosting by default and an air-gapped server edition under SonarQube's 8.0 sovereignty mark (6 leans, 0 ties); Codacy's verdict states that self-hosted is unavailable to new customers.
You answer to ISO 27001:2022 and SOC 2 Type II audits: trust and compliance reads 8.0 vs 7.0 with 6 judges leaning SonarQube, on stated retention (most recent scans only, up to one year), AES-256 at rest and TLS 1.2 minimum.
Your reviewers include the skeptic judge: that judge's weighted total reads 7.3 for SonarQube vs 6.1 for Codacy.
You want dependency and secrets handling with bench backing: dependencies and secrets reads 7.0 vs 6.3, with 4 judges leaning SonarQube and 2 tying.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Skeptic
Has seen "zero false positives" bury a team under four thousand findings on day one, a "free for open source" plan that counted every bot as a contributor, and an "AI autofix" that shipped the repository to a model in the US. Asks how contributors are counted, which languages get real data-flow analysis rather than regular expressions, what happens to the code after a scan, whether the findings export when the contract ends — and what the second year costs.
Codacy
SonarQube
This judge's pick
Criterion by criterion
Code analysis (SAST & code quality)
Codacy
Forty-nine languages and frameworks are covered through more than fifty documented engines — Opengrep, Trivy, Checkov, Bandit among them — with per-language tool lists, OWASP and CWE alignment, custom rules, duplication, cyclomatic complexity and coverage import all documented. But we found no public information on cross-file taint or data-flow analysis and no published false-positive rates: the false-positive help is a business-tier triage feature, and the vendor itself documents holes such as no static analysis tool for Ruby 3.1 and the latest Brakeman unsupported for licensing reasons. This reads as a broad multi-engine linter fleet, not deep interprocedural analysis.
SonarQube
The taint engine is real and documented: security-injection rules track untrusted input from source to sink, findings display their flows, and you can configure your own sources, sanitizers, validators and sinks for homemade frameworks, with OWASP Top 10 (2025/2021/2017), CWE Top 25, ASVS and other standards coverage listed per language and IaC checks for Terraform, CloudFormation, ARM, Kubernetes and Ansible. What I want and do not get is independent proof of precision: the only published false-positive figure I can find is under five percent for secrets detection, while the SAST engine itself gets "high precision" language, and per-language depth is stated only for Advanced SAST (Java, C#) and reachability analysis (Java/Kotlin, Python, C#/VB.NET).
Dependencies (SCA), licences & secrets
Codacy
Composition analysis is real and documented: Trivy scans 20 manifest and lockfile formats across 16 languages, transitive chains are shown from the manifest down to the vulnerable package, repositories are re-scanned daily, malicious packages are checked against the named OpenSSF database, licences are identified per version, and CycloneDX SBOMs export. But the documented reachability support is a prompt for the customer's own AI assistant rather than an engine result, and we found no public information on secret validity checks, scanning of the full git history, end-of-life components or licence policy enforcement.
SonarQube
Reachability is stated for Java/Kotlin, Python and C#/VB.NET, malware and prohibited licences sit alongside CVEs as risk types, SBOMs export in both CycloneDX and SPDX, and secrets get named provider patterns (AWS, GCP, GitHub, Stripe), entropy and fake-credential filters, and a git hook that blocks commits and pushes before a secret lands. We found no public information on the vulnerability database behind the CVEs and its update latency, on end-of-life component flagging, on validity checks for found secrets, or on scanning the full git history — prevention before history is documented, cleanup after is not.
Developer workflow, quality gates & fixes
Codacy
Pull request comments, inline findings, gate rules per severity on new issues, security issues, complexity, duplication and diff coverage, organisation-wide gate policies, ignore-with-reason triage, bulk false-positive ignoring and a local CLI and IDE pre-commit path are documented in detail, with the AI providers named as enterprise OpenAI and Google Gemini instances. What held it back: we found no public information stating that IDE results match the server rules or on deduplication across the many engines, and false-positive pull request comments are documented as GitHub-only.
SonarQube
Findings arrive where developers work: pull request decoration, a quality gate that fails the pipeline with a configurable wait, IDE connected mode that pulls the server's injection findings into the editor, pre-commit and pre-push hooks, and CI across GitHub Actions, GitLab, Bitbucket, Azure, Jenkins and more, with accept/safe statuses and justifications on dependency risks. The AI CodeFix and Remediation Agent are documented as preparing fixes for eligible issues, but the model behind them is never named — "zero data retention and BYOK with LLMs" is a hint, not a provider — and we found no public information on typical scan times or on deduplication of findings across tools.
Platforms, deployment & administration
Codacy
The REST API is documented down to an OpenAPI 2.0 definition, token scopes, rate limits and cursor pagination, and roles, GitHub and GitLab role mappings, audit logs with one-year retention and API access, Jira synchronisation, webhooks and portfolio dashboards with 90-day remediation trends are all documented. However, we found no public information on SCIM provisioning or SARIF import and export, the documented hosts are GitHub, Bitbucket and GitLab cloud-hosted, and the vendor's own documentation states self-hosted is no longer available for new customers — a buyer wanting scans inside its own network has no current offer.
SonarQube
Five DevOps platforms plus Jenkins, a self-managed and air-gapped Server edition, SSO and SCIM on the enterprise plan, webhooks at global and project level with HMAC protection, Jira Cloud and Slack integrations, portfolios and SARIF import give a solid administrative base. We found no public information on audit logs, on export of findings in SARIF or CSV, on self-managed code hosts, or on per-team role granularity — the web API surfaces only as a passing mention of "Web Server API calls" secured by revocable user tokens.
Source-code handling, security & compliance
Codacy
AI handling is documented to a level few vendors reach: enterprise OpenAI and Google Gemini instances, no training on customer code, secrets redacted before any snippet is sent to a model, per-repository or total opt-out, and provider changes notified 15 days in advance; SOC 2 Type II is stated, a public status page runs, and findings map to SOC 2, ISO 27001 and PCI DSS requirements with the vendor plainly scoping its own role. Against that, we found no public information on how long source code itself is retained, and encryption is documented at rest while we found no statement covering transit.
SonarQube
They state the specifics a buyer needs: only the source code of the most recent scans is stored, snapshot retention runs up to one year, deletion is under customer control at any time, AES-256 at rest and TLS 1.2 minimum, ISO 27001:2022 and SOC 2 Type II with scope named and reports on request, published penetration test summaries, a referenced SLA, a status page with 90-day history, and mappings to PCI DSS and the EU Cyber Resilience Act. The AI leg is the soft spot: zero data retention and BYOK with LLMs appear as enterprise features and an AI Annex sits in the legal document list, but the model provider behind the fix features is not named in anything captured here.
European sovereignty
Codacy
The contracting party is Qamine Portugal S.A. under the exclusive jurisdiction of the courts of Lisbon, and the privacy policy states that by principle all data is stored on AWS servers in Ireland, with OpenAI named as the AI subprocessor, Stripe as the payment processor, and transfers out of country covered by Standard Contractual Clauses or adequacy decisions. We found no published data processing agreement or subprocessor list with locations, and the AI chain runs through the non-EU model providers OpenAI and Google Gemini, while the self-hosted edition that would have kept code on the customer's own servers is withdrawn from new customers.
SonarQube
EU hosting is the default — Frankfurt on AWS eu-central-1, with EU backups in eu-west-1 — under SonarSource Sàrl in Switzerland as principal operating entity, with a published data processing agreement, a subprocessor list in the Trust Center and fourteen days' notice before a new subprocessor touches data; the self-hosted, air-gapped Server edition keeps code and findings on the customer's own servers entirely. Against that, the parent holding company is domiciled in the United States, Standard Contractual Clauses and Swiss Addenda are invoked as transfer safeguards, and the captured pages do not show where each subprocessor — including any AI model provider — is located.
Pricing transparency
Codacy
The Team tier is published at $18 per developer per month with unlimited lines of code, a 14-day trial needs no credit card, and the terms publish the automatic renewal with an annual increase between 8% and 10% — so the second-year question is at least answerable. But the price is given as starting at, we found no public information on how a developer is counted, the Business and Enterprise tiers list features without prices, penetration testing is billed separately with no figure, VAT treatment is unstated, and the captured pages give different figures for private repository limits — up to 100 on the Team plan feature list, unlimited elsewhere.
SonarQube
The cloud Team plan is public at "$34 per month (previously listed at $65)" with a 14-day trial, private projects are free up to 50k lines of code, OSI-licensed public repositories are free, Gitar is "$20 /user/mo, billed annually", and the Server counting rule is spelled out — lines of code of the largest branch analyzed, not cumulative on re-analysis. But the Enterprise plan is "custom, contact sales", Advanced Security is an additional subscription with no public price, the captured Server pricing page shows tiers and lines-of-code recommendations without price figures, and the basis of the monthly figure plus VAT treatment go unexplained, so a real annual cost for a large estate cannot be computed from these pages.
Sovereignty, side by side
Dimension
Codacy
SonarQube
Legal entity
Incorporated in PT
Incorporated in CH
Hosting location
Not determined
EU by default
Hosting options
Self-hostable
Self-hostable
Open source
Not determined
Not determined
Data processing agreement
Not determined
Not determined
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
Fact
Codacy
SonarQube
Compliance · Privacy contact
privacy@codacy.com · two months for special complexity · 301
As of 6 Nov 2026, the panel rates both 3.5/5. Weighted by what each judge cares about, 0 of the 6 judges pick Codacy and 6 pick SonarQube. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is Codacy or SonarQube European?
Codacy is European (EU-Made, Portugal). SonarQube is European (EU origin, foreign-owned, Switzerland). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Where do Codacy and SonarQube store customer data?
Per the vendors’ own pages as captured — Codacy: its pages as captured do not say. SonarQube: In the EU by default.
Do Codacy and SonarQube have a free plan?
As of 6 Nov 2026, SonarQube’s own pages state a free plan; Codacy’s pages as captured do not. Each product page links the pricing page it was read from.