Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

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

by Qamine Portugal S.A. · www.codacy.com

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

Link to this page

Codacy: AI-assisted analysis on whats-best.ai Codacy: 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.

Codacy at a glance

Vendor
Qamine Portugal S.A.
Headquarters
Incorporated in Portugal source, captured 6 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 6 Nov 2026
Free plan
Not stated on the vendor’s pages as of 6 Nov 2026
Panel verdict
The AI panel rates Codacy 3.5/5, the mean of 6 judges. Codacy, from Qamine Portugal S.A., is a cloud-hosted code quality and security platform: static analysis across 49 languages and frameworks, Trivy-based dependency scanning over 20 manifest and lockfile formats in 16 languages, and pull-request merge gates on GitHub, GitLab and Bitbucket. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Codacy alternatives, European ones first →

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

The panel's verdict

Codacy, from Qamine Portugal S.A., is a cloud-hosted code quality and security platform: static analysis across 49 languages and frameworks, Trivy-based dependency scanning over 20 manifest and lockfile formats in 16 languages, and pull-request merge gates on GitHub, GitLab and Bitbucket. It scores highest on developer workflow and trust and compliance, both at a flat 7, on documented inline comments, organization-wide gate policies, an AI position spelled out — enterprise OpenAI and Google Gemini instances, no training on customer code, secrets redacted before snippets are sent, per-repository or full opt-out — and mappings to SOC 2, ISO 27001 and PCI DSS. The clear weakness is pricing transparency at 4 to 5: the Team plan is public at Starting at $18 Per dev/mth, but the Business and Enterprise tiers list features without prices and VAT treatment is unstated. Elsewhere scores range 6 to 7, a split of weight rather than fact: the same gaps recur — no public information on cross-file taint analysis or false-positive rates, and reachability only as a prompt for your AI assistant. Self-hosted is stated to be unavailable to new customers.

Report an error

Speaks for it

  • Developer workflow scores a flat 7 on documented inline pull-request comments, status checks and configurable merge gates across GitHub, GitLab and Bitbucket.
  • Dependency scanning via Trivy covers 20 manifest and lockfile formats across 16 languages, with transitive chains, daily re-scans and OpenSSF malicious-package checks.
  • AI handling is documented in detail — enterprise OpenAI and Google Gemini instances, no training on customer code, secrets redacted before any snippet is sent, and per-repository or full opt-out.
  • Findings map to SOC 2, ISO 27001 and PCI DSS controls, with audit logs kept one year and retrievable by API.
  • The Team plan is published at Starting at $18 Per dev/mth with unlimited lines of code, a free Developer plan and a 14-day trial with no credit card required.

Report an error

Held against it

  • Pricing transparency scores 4 to 5 — the Business and Enterprise tiers list features without public prices, penetration testing is billed separately and VAT treatment is unstated.
  • We found no public information on cross-file taint or data-flow analysis or on published false-positive rates.
  • The vendor states self-hosted is no longer available for new customers, so a buyer wanting scans inside its own network has no current offer.
  • The captured pages give different figures for private repository limits — up to 100 on the Team plan feature list, unlimited elsewhere.
  • We found no public information on a published data processing agreement or a subprocessor list with locations, and the AI chain runs through the non-EU providers OpenAI and Google Gemini.

Report an error

Best for

  • You run pull-request-based development on GitHub, GitLab or Bitbucket and want inline findings and merge gates with no CI/CD configuration.
  • You need exportable audit evidence mapped to SOC 2, ISO 27001 or PCI DSS controls.
  • You are an EU buyer who wants a Portuguese contracting entity under the courts of Lisbon and the privacy policy's statement that all data is stored on AWS servers in Ireland.
  • You have a team of up to 30 developers and want a published starting price of $18 per dev/mth with unlimited lines of code.

Report an error

Avoid if

  • You need code scanned inside your own network — the vendor states self-hosted is no longer available for new customers, and the local CLI is the only analysis that runs without sending code to Codacy.
  • Your codebase includes Ruby 3.1 — the vendor documents no static analysis tool for it and no support for the latest Brakeman due to licensing.
  • You need published prices before signing — the Business and Enterprise tiers list features without figures, penetration testing is billed separately and VAT treatment is unstated.
  • Your data policy excludes non-EU AI model providers even with secrets redacted and a full opt-out available.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Code analysis (SAST & code quality)

Show reasoning
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 Lead Developer

Security rules cover every language we build with — PHP, TypeScript, Python, Java, Go — plus infrastructure-as-code for Terraform, Kubernetes and friends, aligned to OWASP and CWE, with custom rules, cyclomatic complexity, duplication, coverage metrics and false-positive triage all documented. What I could not find is cross-file taint analysis, published false-positive rates or a data-flow explanation per finding, which is what I would want before trusting it on injection flaws in a large Laravel monolith. 3 9 11 17 18

Report an error

The Application Security Engineer

Static analysis across forty-nine languages with per-language tool lists, twelve thousand plus rules aligned to OWASP and CWE, custom rules, cyclomatic complexity, duplication and coverage metrics, and infrastructure-as-code checks for Terraform, Kubernetes, CloudFormation and more — the core is documented, and false positives get triaged with reasons rather than merely listed. We found no public information on taint or data-flow analysis that follows user input across files, on published false-positive rates, or on each finding being explained with its data flow — for a payments codebase that is what separates a verdict from a hint. 3 9 17 18 11

Report an error

The Engineering Manager

Static analysis spans 49 languages and frameworks with the per-language tool list published — SpotBugs for our Java, detekt called out for Kotlin, Lizard for complexity — alongside duplication and coverage measures, issues per thousand lines of code, OWASP- and CWE-aligned rules, custom rules and infrastructure-as-code checks for Terraform and Kubernetes. We found no public information on cross-file taint analysis, per-finding data-flow explanations, or measured false-positive rates, so it covers what my six teams need daily but not the deep interprocedural work. 3 7 9 11 17 18

Report an error

The Platform Engineer

Security rules cover 18 languages plus Terraform, Kubernetes and Dockerfiles, aligned to OWASP and CWE and applied at every commit, on top of 49-language quality analysis with a published per-language tool matrix, duplication, cyclomatic complexity, coverage import and custom rules — a broad platform for our polyglot estate. The false-positive triage and per-repository auto-tuning are described but unquantified. We found no public information on cross-file taint or data-flow analysis or on published false-positive rates, so it sits clearly above the mid level but not near the top. 3 9 17 18 11

Report an error

The Product Security Officer

Static analysis spans 49 languages with a published per-language tool table, rules aligned to OWASP and CWE, 22 security categories, infrastructure-as-code checks, duplication, complexity and coverage metrics, custom rules and suggested fixes in eleven languages. For an auditor's file this is broad, but we found no public information on cross-file taint or data-flow analysis, published false-positive rates or maintainability scores, and the vendor itself states Ruby 3.1 has no supported static analysis tool. 3 17 11 18 9 7

Report an error

The Skeptic

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. 3 7 9 11 17 18

Report an error

Dependencies (SCA), licences & secrets

Show reasoning
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 Lead Developer

Trivy-based scanning of twenty manifest and lockfile formats across sixteen languages, with the transitive chain shown down to the vulnerable package, daily re-scans for new CVEs, malicious-package checks against the OpenSSF database updated daily, licence scanning, CycloneDX SBOM export and container image scanning. Reachability comes only as a prompt for my AI assistant to check whether affected functions are actually called, and we found no public information on end-of-life components, secret validity checks or scanning the full git history. 4 12 17 19

Report an error

The Application Security Engineer

Trivy-based dependency scanning covers twenty manifest and lockfile formats across sixteen languages, shows the chain from direct dependency down to the vulnerable transitive package, rescans daily, checks the OpenSSF malicious-packages database, and ships per-version licence views, OSSF Scorecard, CycloneDX SBOM export and container image scanning. Reachability, though, is only a prompt handed to your AI assistant with the human deciding, and we found no public information on secrets scanned across the full git history or checked for validity, on server-side push protection beyond the local pre-commit check, or on end-of-life components being flagged. 4 17 19 12 3

Report an error

The Engineering Manager

Dependency scanning covers 20 manifest and lockfile formats across 16 languages via Trivy, shows the chain from direct to vulnerable transitive package, re-scans daily, checks npm, PyPI, Maven, NuGet, RubyGems, crates.io and Go against the OpenSSF malicious-package database, and adds the licence per dependency version, OSSF Scorecard, CycloneDX SBOM export and container image scanning. What is offered as reachability is a prompt for our own AI assistant rather than an automated call-path analysis, and we found no public information on end-of-life components, git-history secret scanning, or validity checks on detected secrets. 4 9 17 19

Report an error

The Platform Engineer

SCA covers 20 manifest and lockfile formats across 16 languages including transitive chains, licence detection per dependency version, CycloneDX SBOM export, daily re-scans against the OpenSSF Malicious Packages database, and container image CVEs. What holds it down for me: reachability is an AI-assistant prompt the developer runs rather than analysis, and we found no public information on secret scanning across git history, validity checks, push protection, or end-of-life component flagging. 4 17 19 20

Report an error

The Product Security Officer

Dependency scanning runs on Trivy across 20 manifest and lockfile formats with transitive chains shown, the licence per dependency version, daily re-scans for new CVEs, malicious-package checks against the OpenSSF database updated daily, container image scanning and a CycloneDX SBOM export — the per-release SBOM I need, though one documentation page describes the export as generated only for repositories with dependency findings. Secrets are flagged in pull requests and caught locally before commit, but we found no public information on secret validity checks, git-history scanning or VEX output. 4 17 19 9 12 3 1

Report an error

The Skeptic

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. 4 9 17 19

Report an error

Developer workflow, quality gates & fixes

Show reasoning
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 Lead Developer

Findings land as in-line comments on the pull request with status checks, merge gates that count new issues and new security issues by severity, ignore-with-reason triage and bulk dismissal of false positives — exactly where I want my reviewers looking. Free IDE plugins for VS Code and JetBrains plus a local CLI give pre-commit checks, and the AI autofix names its providers (OpenAI, Google Gemini). We found no public information on deduplicating findings across tools, and scan times are only described as within minutes. 3 4 9 21 22

Report an error

The Application Security Engineer

Developers get inline pull-request comments and status checks on GitHub, GitLab and Bitbucket, gates that fail a pull request when new security issues above a chosen severity exceed a set limit, per-repository and organization-wide gate policies, local pre-commit checks through the CLI and IDE plugins, and suppression with reasons that land in the audit log; autofix runs through named enterprise OpenAI and Google Gemini models and the IDE passes findings to your assistant before commit. We found no public information on findings being deduplicated across tools or on an explicit statement that IDE results match the server rules, which is why I stop just short of the higher marks. 3 9 21 22 24

Report an error

The Engineering Manager

Findings land as in-line comments and status checks on pull requests, gates can fail a merge on introduced issues, new security issues, introduced complexity, introduced clones and diff coverage under organization-wide gate policies, ignores carry reasons and appear in the audit log, findings sync to Jira with Slack alerts, and a free IDE extension plus CLI and agent skills give local pre-commit checks. The fix-all patch and false-positive pull-request comments are documented for GitHub only, merge blocking rides on the Git provider's branch protection, and we found no public information on deduplicating findings across tools. 3 9 21 22 24

Report an error

The Platform Engineer

Findings land as in-line comments, fix suggestions and status checks on GitHub, GitLab and Bitbucket pull requests, with quality gates configurable as required checks, limits per severity, and a clean new-code versus unchanged-lines distinction — exactly the shape our merge flow needs. Local CLI and free IDE extensions scan before commit, and AI fixes run on named models (OpenAI, Google Gemini) with per-repository or full opt-out. We found no public information on Jenkins or GitLab CI steps, on typical scan times beyond 'minutes', or on deduplication across tools. 3 21 22 12 9

Report an error

The Product Security Officer

Findings arrive as in-line comments and status checks on GitHub, Bitbucket and GitLab, gates can be set per organization policy on new issues by severity, complexity, duplication and diff coverage with optional merge blocking, and the local CLI and IDE extension check before commit. Ignore-with-reason and bulk false-positive handling are documented, and the AI fix suggestions name their model providers (enterprise OpenAI and Google Gemini) with an opt-out. We found no public information on deduplication across tools, IDE parity with server rules, or scan times beyond "within minutes". 3 22 21 9 12 5

Report an error

The Skeptic

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. 3 9 17 21 22

Report an error

Platforms, deployment & administration

Show reasoning
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 Lead Developer

GitHub, Bitbucket and GitLab are the supported hosts with an operational status page, a REST API behind an OpenAPI definition, Jira ticket creation from findings, granular roles mapped from the Git provider, audit logs with one-year retention and organization-wide reports with export. The captured pages give different pictures of self-hosting — a documentation section exists, while another page states it is no longer available to new customers — and we found no public information on SCIM provisioning or SARIF import and export. 7 8 9 23 24 26

Report an error

The Application Security Engineer

A documented REST API in two versions with an OpenAPI definition, a full role-and-permission matrix inherited from the Git provider, audit logs with one-year retention reachable by API, portfolio dashboards with trends and segment filters, webhooks, and Jira and Slack sync make the administration side genuinely deep. The self-hosted edition is documented but the vendor states it is no longer available to new customers, and we found no public information on SCIM provisioning, SARIF import or export, or Azure DevOps support — exactly what an enterprise rollout would ask for next. 8 9 23 24 26 7

Report an error

The Engineering Manager

GitHub, GitLab and Bitbucket are supported with role mapping from provider roles, a documented REST API with an OpenAPI definition and a CLI, webhooks, Jira sync, an organization-manager role above repository roles, audit logs covering organization, repository and user events with one-year retention and API access, and portfolio reports with three-month trends and top-ten high-risk repositories. The self-hosted edition is stated to be no longer available to new customers, and we found no public information on SCIM provisioning, SARIF export or Azure DevOps. 7 8 9 23 24 26

Report an error

The Platform Engineer

API v3 with an OpenAPI definition covers repository quality settings, people and organization management — enough to script a rollout — with granular roles mapped from Git provider roles, audit logs with API access (Business plan, one-year retention), webhooks and SAML SSO on Business. But for an insurer like us: the captured documentation states self-hosted is no longer available for new customers, the Git provider integrations are described for the cloud-hosted product, and we found no public information on SCIM provisioning from Entra ID or on SARIF export — the documented exports are CSV and CycloneDX. 8 23 24 7 9 6

Report an error

The Product Security Officer

A documented API with an OpenAPI definition, webhooks and audit logs retrievable by API with one-year retention, roles inherited from Git providers plus granular organization permissions, Jira and Slack integration, and organization-wide security dashboards cover most of what I administer. The captured pages state self-hosted is no longer available for new customers, and we found no public information on SCIM provisioning, SARIF import or export, or self-managed Git hosts beyond GitHub Enterprise with data residency. 8 23 24 9 7 26

Report an error

The Skeptic

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. 7 8 9 23 24 26

Report an error

Source-code handling, security & compliance

Show reasoning
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 Lead Developer

The vendor states SOC 2 Type II certification, a public status page, encryption at rest, that employees cannot reach user data, and that customer code never trains AI models — with the model providers named, secrets redacted before snippets are sent, and a full opt-out. Findings map to OWASP, CWE, ISO 27001 controls and PCI DSS clauses. A retention period for customer source code is not stated, and the self-hosted escape hatch is closed to new customers. 3 10 11 12 13 16 25

Report an error

The Application Security Engineer

Customer code never trains AI models, snippets have secrets redacted before reaching enterprise OpenAI or Google Gemini instances, and the opt-out can be universal, per repository or total — the cleanest AI-data statement I have scored. Dedicated pages map findings to SOC 2, ISO 27001 Annex A and PCI DSS requirements 6.2.1, 6.2.3, 6.2.4 and 6.5.1 with timestamped, exportable evidence, which is what my PCI auditors accept. We found no public information on code retention periods or encryption in transit, and for a new customer the only in-network option is the local CLI, so the top marks stay out of reach. 3 15 12 11 25 10 13

Report an error

The Engineering Manager

Customer code is stated not to train AI models, AI features run on enterprise OpenAI and Google Gemini instances with secrets redacted and a full opt-out, encryption at rest and network controls are described, SOC 2 Type II is stated with an explicit scope note, and ISO 27001, OWASP, CWE and PCI DSS mappings are published alongside a live status page and an SLA in the enterprise plan. We found no public information on how long source code itself is retained or on a data-flow diagram of what is sent where. 3 10 11 12 13 15 25

Report an error

The Platform Engineer

SOC 2 Type II is stated, a public status page with component health exists, audit logs record configuration changes, and reports are mapped to SOC 2, ISO 27001 and PCI DSS controls — good audit material. The AI handling is unusually well documented: enterprise OpenAI and Google Gemini instances, no training on customer code, secrets redacted before snippets are sent, with a full opt-out. We found no public information on source-code retention periods, the SLA appears only in a feature list, and the primary flow scans code on Codacy's own infrastructure — only the CLI analyses locally without sending code. 3 10 12 13 15 11 25

Report an error

The Product Security Officer

SOC 2 Type II, a GDPR posture with all data stored on AWS servers in Ireland, encryption at rest, a public status page, audit logs, and control-by-control mappings for SOC 2, ISO 27001 and PCI DSS give me evidence an auditor can file. AI processing is transparent: enterprise OpenAI and Gemini instances, no training on customer code, secrets redacted before any snippet is sent to a model, and an opt-out per repository or entirely. The captured pages do not state how long source code itself is retained, and we found no public information on Cyber Resilience Act mapping. 3 15 10 12 11 25 24 13 16

Report an error

The Skeptic

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. 3 10 11 12 13 15 25

Report an error

European sovereignty panel opinion

Show reasoning
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 Lead Developer

The contracting entity is Qamine Portugal S.A. under Portuguese law and the courts of Lisbon, and all data is stored on AWS servers in Ireland, with GDPR compliance claimed and Standard Contractual Clauses or adequacy decisions stated for transfers. The AI models (OpenAI, Google Gemini) and payment processing (Stripe) sit outside the EU with stated safeguards, and we found no public information on a published data processing agreement or a consolidated subprocessor list with locations. 3 10 15 16

Report an error

The Application Security Engineer

Contracting runs through Qamine Portugal S.A. under Portuguese law before the Lisbon courts, data is stored by principle on AWS servers in Ireland, the Portuguese supervisory authority is the complaints route, and SOC 2 Type II is stated. AI runs through OpenAI and Google Gemini and payments through Stripe, but we found no public information on a published data processing agreement, on subprocessor locations, or on a complete subprocessor list — the safeguards named are standard contractual clauses and adequacy decisions. 15 16 10 3 12

Report an error

The Engineering Manager

Qamine Portugal S.A. is the contracting party under Portuguese law and the Lisbon courts, all data is stored on AWS servers in Ireland, and OpenAI for AI recommendations and Stripe for payments are named as subprocessors. The AI chain runs through non-EU providers, with an opt-out, a no-training commitment and standard-contractual-clause transfer language as safeguards; we found no published data processing agreement or subprocessor locations on the captured pages. 3 10 15 16

Report an error

The Platform Engineer

The contracting entity is Qamine Portugal S.A. under Portuguese law and the Lisbon courts, the privacy policy states all data is stored on AWS servers in Ireland, and GDPR compliance is claimed with adequacy decisions or Standard Contractual Clauses for transfers — a solid EU base. Named subprocessors include OpenAI (and Gemini) for AI and Stripe for payments, both non-EU with no locations listed, and we found no published data processing agreement on the captured pages. 15 16 10 3

Report an error

The Product Security Officer

The contracting entity is Qamine Portugal S.A. under Portuguese law and the courts of Lisbon, and the privacy policy states all data is stored on AWS servers in Ireland, with Standard Contractual Clauses or adequacy decisions for transfers and SOC 2 Type II stated. The AI chain runs on enterprise OpenAI and Google Gemini instances and payments on Stripe, but their locations are not listed, and we found no public information on a published data processing agreement or a complete subprocessor register. 15 16 3 10 12

Report an error

The Skeptic

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. 3 7 10 15 16

Report an error

Pricing transparency

Show reasoning
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 Lead Developer

The Team plan is public starting at $18 per dev per month with unlimited lines of code, and the free developer tier and a 14-day trial without credit card are clear; the terms also disclose the 8% to 10% annual renewal increase up front. But the Business tier — where SSO, audit logs, webhooks and false-positive triage live — carries no price on the captured pricing page, and I found no statement of VAT treatment or of how occasional contributors are counted, which matters when freelancers push to my repositories. 4 5 9 15

Report an error

The Application Security Engineer

The Team plan is public at 'Starting at $18 Per dev/mth' for yearly and monthly billing, with a free open-source tier, a free Developer plan and a fourteen-day trial without a credit card, billed per developer with unlimited lines of code. For the Business and higher tiers we found no public price — the pages we read list their features (audit logs, webhooks, false-positive detection, the dependencies view, container scanning) without figures — and we found no public information on how developers are counted, on VAT treatment, or on the cost of the separately billed penetration testing. 9 4 15 19 21 23

Report an error

The Engineering Manager

The Team plan is public starting at $18 per dev/mth with unlimited lines of code, up to 30 developers and 100 private repositories, plus a free Developer plan and a 14-day trial with no credit card. The Business and Enterprise tiers list inclusions such as the dependency view, audit logs, SSO and SAML without prices on the captured pages, penetration testing is billed separately, and we found no public information on VAT treatment or how the monthly and yearly figures differ. 4 9 15 21

Report an error

The Platform Engineer

The Team plan is public at 'Starting at $18 Per dev/mth' for teams up to 30 devs with yearly and monthly options, up to 100 private repositories and unlimited lines of code, plus a free Developer plan and a 14-day trial without credit card. But the Business plan — where SSO/SAML, audit logs, webhooks, the dependencies view, licence and container scanning all sit — carries no public price, penetration testing is 'billed separately', and we found no public information on VAT treatment or on how developers are counted beyond the Pulse plan's seat auto-adjustment. 9 4 15 21

Report an error

The Product Security Officer

The Team plan is published at a starting price of $18 per developer per month with yearly and monthly options, unlimited lines of code, up to 100 private repositories, a free Developer plan and free open-source use, and the terms add renewal mechanics including a possible annual increase between 8% and 10%. The Business and Enterprise tiers — where SSO, audit logs, license and container scanning sit — carry no public price, penetration testing is only described as billed separately, and VAT treatment is not stated. 9 4 15 5

Report an error

The Skeptic

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. 3 9 15

Report an error

European sovereignty — proven facts

2 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 Not determined — uncited Report an error
Hosting options Self-hostable unverified
Why unverified?

The same documentation states "Codacy Self-hosted is no longer available for new customers", so the self-hosted option may no longer be obtainable for new buyers.

1/1 pts 7 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 Codacy

Is Codacy European?

Yes. whats-best.ai classifies Codacy as EU-Made. Its vendor, Qamine Portugal S.A., is incorporated in Portugal, per the vendor’s page captured 6 Nov 2026.

Where does Codacy store data?

Not stated on the vendor’s pages as of 6 Nov 2026.

Does Codacy have a free plan?

Not stated on the vendor’s pages as of 6 Nov 2026.

What are the best alternatives to Codacy?

As of 19 Nov 2026, the panel rates SonarQube (3.5/5), Aikido Security (3.5/5) and Endor Labs (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 SonarQube (EU origin, foreign-owned, Switzerland). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Codacy 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 (26)

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

  1. 1 Vendor homepage www.codacy.com Checked 6 Nov 2026 Details →
  2. 2 Features page (code quality) www.codacy.com Checked 6 Nov 2026 Details →
  3. 3 Features page (SAST) www.codacy.com Checked 6 Nov 2026 Details →
  4. 4 Features page (SCA) www.codacy.com Checked 6 Nov 2026 Details →
  5. 5 Features page (security) www.codacy.com Checked 6 Nov 2026 Details →
  6. 6 Documentation docs.codacy.com Checked 6 Nov 2026 Details →
  7. 7 Documentation (security monitor) docs.codacy.com Checked 6 Nov 2026 Details →
  8. 8 API documentation docs.codacy.com Checked 6 Nov 2026 Details →
  9. 9 Pricing page www.codacy.com Checked 6 Nov 2026 Details →
  10. 10 Security / trust page www.codacy.com Checked 6 Nov 2026 Details →
  11. 11 Certification page (ISO 27001) www.codacy.com Checked 6 Nov 2026 Details →
  12. 12 Certification page (SOC 2) www.codacy.com Checked 6 Nov 2026 Details →
  13. 13 Public status page status.codacy.com Checked 6 Nov 2026 Details →
  14. 14 About page www.codacy.com Checked 6 Nov 2026 Details →
  15. 15 Terms of service (names the operating company) www.codacy.com Checked 6 Nov 2026 Details →
  16. 16 Privacy policy www.codacy.com Checked 6 Nov 2026 Details →
  17. 17 Code analysis (SAST & code quality) — found from sitemap docs.codacy.com Checked 6 Nov 2026 Details →
  18. 18 Code analysis (SAST & code quality) — found from sitemap docs.codacy.com Checked 6 Nov 2026 Details →
  19. 19 Dependencies (SCA), licences & secrets — found from sitemap docs.codacy.com Checked 6 Nov 2026 Details →
  20. 20 Dependencies (SCA), licences & secrets — found from sitemap docs.codacy.com Checked 6 Nov 2026 Details →
  21. 21 Developer workflow, quality gates & fixes — found from sitemap docs.codacy.com Checked 6 Nov 2026 Details →
  22. 22 Developer workflow, quality gates & fixes — found from sitemap docs.codacy.com Checked 6 Nov 2026 Details →
  23. 23 Platforms, deployment & administration — found from sitemap docs.codacy.com Checked 6 Nov 2026 Details →
  24. 24 Platforms, deployment & administration — found from sitemap docs.codacy.com Checked 6 Nov 2026 Details →
  25. 25 Source-code handling, security & compliance — found from sitemap www.codacy.com Checked 6 Nov 2026 Details →
  26. 26 Source-code handling, security & compliance — found from sitemap docs.codacy.com Checked 6 Nov 2026 Details →