CodeScene
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by CodeScene AB · codescene.com
Report an error on this page Is this your product? →
Link to this page
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.
CodeScene at a glance
- Vendor
- CodeScene AB
- Headquarters
- Not stated on the vendor’s pages as of 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 CodeScene 2.5/5, the mean of 6 judges. The bench scores CodeScene, from the Swedish company CodeScene AB, as a maintainability and technical-debt analyser with a strong developer workflow: automated Code Health reviews gate pull and merge requests on GitHub, Bitbucket, Azure DevOps and GitLab, a CLI runs the same checks locally, and free IDE extensions cover JetBrains, VS Code and Visual Studio. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
The bench scores CodeScene, from the Swedish company CodeScene AB, as a maintainability and technical-debt analyser with a strong developer workflow: automated Code Health reviews gate pull and merge requests on GitHub, Bitbucket, Azure DevOps and GitLab, a CLI runs the same checks locally, and free IDE extensions cover JetBrains, VS Code and Visual Studio. Developer workflow scored 6-7 and integration and administration a uniform 6, with a self-managed on-premise edition, Azure Entra SSO and a public REST API. Weaknesses are sharp: dependencies and secrets sits at 0 from minimum to maximum, with no public information on dependency scanning, SBOMs or secret detection, and code analysis shows deep quality metrics but no public information on OWASP or CWE rule mapping, taint analysis or false-positive handling. The judges split on sovereignty: higher scores credit the Swedish entity and the on-premise edition, the low score points to cloud regions shown only as 'International' and 'United States' and no public information on subprocessors or a data processing agreement. Standard is '€18 Billed yearly', Pro '€27 Billed yearly'; Enterprise is 'Talk to sales'.
Speaks for it
- Code Health analysis built from 25+ factors on a 1-to-10 scale, with hotspot, change-coupling and function-level X-Ray analysis across 30+ languages
- Automated code health reviews gate pull and merge requests on GitHub, Bitbucket, Azure DevOps and GitLab, with a CLI that runs the same checks locally and free IDE extensions
- A self-managed on-premise edition is documented with a licence purchase path, alongside Azure Entra SSO, a public REST API and Jira integration
- Standard is priced at '€18 Billed yearly' and Pro at '€27 Billed yearly', with a free Community Edition for open-source projects and unlimited private repositories
- ISO 27001 certification is stated on the captured homepage and pricing pages
Held against it
- Dependencies and secrets scored 0 from minimum to maximum, with no public information on dependency scanning, licence detection, SBOM export or secret detection
- We found no public information on security rules mapped to OWASP or CWE, taint or data-flow analysis, or false-positive handling, and code analysis scored 4-5
- Trust and compliance scored 4 across the table, with no public information on code retention, encryption, whether code trains AI models, an SLA or a status page
- Sovereignty scores ranged from 3 to 7, with no public information on cloud hosting location, subprocessors or a data processing agreement behind the split
- The counting basis for the published prices is not shown beyond a '100+ active authors' tier figure, Enterprise is 'Talk to sales' and the ACE add-on carries no public price
Best for
- You prioritise technical debt in a large ageing codebase and want hotspot, change-coupling and complexity-trend analysis with trend-based quality gates
- Your teams work across GitHub, GitLab, Bitbucket and Azure DevOps and want findings in pull requests, pre-commit hooks and IDEs
- You must keep analysis inside your own network and can use the documented self-managed on-premise edition
- You maintain open-source projects and qualify for the free Community Edition
Avoid if
- You need dependency scanning, SBOM export, licence policies or secret detection in the same tool; dependencies and secrets scored 0 across the table
- You need security SAST with rules mapped to OWASP or CWE, taint analysis or documented false-positive handling
- You need a cloud deployment with named EU hosting; the captured pricing page lists only 'International' and 'United States' regions
The scores
| Criterion | Panel median |
|---|---|
| Code analysis (SAST & code quality) | 2.5 of 5 |
| Dependencies (SCA), licences & secrets | 0 of 5 |
| Developer workflow, quality gates & fixes | 3.5 of 5 |
| Platforms, deployment & administration | 3 of 5 |
| Source-code handling, security & compliance | 2 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 2 of 5 |
Code analysis (SAST & code quality)
Show reasoningHide 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.
The Lead Developer
Strong maintainability analysis: Code Health with 25+ factors, hotspot and change-coupling views, complexity trends, X-Ray at function level, coverage measurement and customisable quality rules, across many languages (the captured pages give different figures — over 25 and 30+). For our security needs we found no public information on rule sets mapped to OWASP or CWE, on data-flow or taint analysis, or on false-positive handling, so I treat it as a code-quality engine rather than a SAST. 3 8 10 13
The Application Security Engineer
The captured pages show genuinely deep code-quality analysis — Code Health built from 25+ factors, 25+ code smells across 30+ languages, complexity trends, function-level X-Ray and code coverage — but every page I read frames it as maintainability and technical debt. I found no public information on a security rule list mapped to OWASP or CWE, taint or data-flow analysis, or how false positives are measured, which is what I need before pointing a tool at payment-scoped code. 3 4 7 8 10 13
The Engineering Manager
Deep on exactly what an ageing codebase needs: a Code Health score on a 1-to-10 scale built from 25+ factors, hotspot and change-coupling analysis, complexity trends, function-level X-ray, coverage measurement and team-level breakdowns across 30+ languages, with customisable quality rules. What is documented is a maintainability and technical-debt analyser; we found no public information on security rule sets mapped to OWASP or CWE, taint analysis, duplication metrics, or false-positive handling. 2 3 10 13
The Platform Engineer
The captured pages show a deep code-quality analyser: the Code Health metric combining 25+ factors on a 1-10 scale, code smells, complexity and code-health trends over time, function-level X-ray analysis, hotspots, coverage and customisable quality rules across 30+ languages, backed by published peer-reviewed research. We found no public information on security-oriented static analysis — OWASP or CWE rule mapping, taint or data-flow analysis, or false-positive handling — so the evidence positions it as a maintainability and technical-debt analyser. 2 3 9 10 13
The Product Security Officer
As a maintainability analyser this is strong: a Code Health score from more than 25 factors, complexity trends, hotspot and change-coupling analysis, function-level X-ray drilling, and coverage checks across 30+ languages, with team-level breakdowns of code health over time. For my CRA secure-development file, though, this is not security SAST: we found no public information on data-flow or taint analysis, rules mapped to OWASP or CWE, or how false positives are handled, and a published rule list per language is not shown. 3 8 10 12 13
The Skeptic
The quality side is genuinely deep — Code Health built from 25+ factors, hotspot and change-coupling analysis, function-level X-ray, complexity trends over time, and support for 30+ languages with customisable quality rules — but I found no public information on data-flow or taint analysis, a published rule list, OWASP or CWE mapping, or how false positives are handled. This is evidenced behavioural code quality at scale, not evidenced security SAST. 2 3 8 10 12 13
Dependencies (SCA), licences & secrets
n/r
n/r
n/r
n/r
n/r
Show reasoningHide 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.
The Lead Developer not rated — no public information
We found no public information on dependency or supply-chain scanning, licence detection and policies, SBOM export, or secret detection including git history on the product, integrations, documentation and pricing pages I read. As a buyer I would still need a separate tool for vulnerable packages. 2 4 7 8
The Application Security Engineer not rated — no public information
I found no public information on dependency scanning, licences, SBOMs, container images or secret detection in the homepage, product, integrations, documentation or pricing pages I read. For a payments company that must check secrets for validity across the whole git history and stop them before they land, this entire dimension is undocumented in the captures. 1 2 4 7 8
The Engineering Manager not rated — no public information
We found no public information on dependency scanning, licence detection, SBOM export or secret detection on the pages we read; the vendor positions the product as behavioural code analysis that goes beyond traditional static analysis, with product areas of code quality, team dynamics, software delivery and code coverage. 9 15
The Platform Engineer not rated — no public information
We found no public information on dependency analysis, licence detection, SBOM export, container image scanning or secret detection in the captured pages; the product, integrations and pricing pages centre on code health, technical debt and team analytics. 2 4 8
The Product Security Officer not rated — no public information
We found no public information on software composition analysis, licence detection, SBOM export in a standard format, or secret detection on the captured product, integrations and pricing pages. Since an SBOM per release and post-shipping vulnerability and licence tracking are the core of our Cyber Resilience Act obligations, this dimension is undocumentated for a buyer in my seat and I cannot score it. 2 4 8
The Skeptic
The captured pages describe the product's scope as code quality, team dynamics, software delivery and code coverage, with a stated mission of going beyond traditional static analysis by combining code metrics with behavioural insights. We found no public information about dependency scanning, licences, SBOMs, container image checks or secret detection on any page we read. 9 15
Developer workflow, quality gates & fixes
Show reasoningHide 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.
The Lead Developer
Automated Code Health reviews on GitHub, GitLab, Bitbucket and Azure DevOps merge requests acting as gate and coach, a CLI performing the same checks as the PR integration on staged changes, pre-commit hooks via Git hooks, hotspot- and trend-based quality gates, and IDE extensions for PhpStorm, the JetBrains family, VS Code and more with smells detected locally. We found no public information on the model behind the AI refactoring add-on, on triage or ignoring findings, or on scan times. 4 6 7 8 13
The Application Security Engineer
Developers meet the findings where they work: automated reviews act as a quality gate on pull and merge requests for GitHub, GitLab, Bitbucket and Azure DevOps, the CLI runs the same checks as the pull-request integration on staged or non-committed changes and can be wired into a pre-commit Git hook, and IDE extensions cover ten JetBrains editors plus VS Code and its forks. The AI refactoring add-on is sold separately but the model behind it is not named, and I found no public information on suppression with reasons, or on typical scan times. 3 4 5 6 7 12 13
The Engineering Manager
Automated Code Health reviews on pull and merge requests across GitHub, GitLab, Bitbucket and Azure DevOps act as a quality gate that prevents new technical debt, the CLI performs the same checks as the pull request integration on staged or inter-branch changes, pre-commit hooks run the delta command, and JetBrains, VS Code and Visual Studio extensions give real-time feedback with hotspot-specific gates. We found no public information on suppression and triage with reasons, deduplication across tools, the model provider behind the AI refactoring add-on, or typical scan times. 4 5 6 7 13
The Platform Engineer
Automated Code Health reviews on pull and merge requests for GitLab, GitHub, Bitbucket and Azure DevOps act as quality gate and coach, and the CLI performs the same checks locally with a delta view of new work and documented pre-commit hooks; the IDE story is unusually broad, with a free extension for VS Code, ten JetBrains IDEs, Visual Studio in early access and Cursor-class editors, plus a PR-triggered refactoring agent. We found no public information on triage and suppression rules, deduplication or typical scan times, and among the CI integrations we found no mention of Jenkins, only a general statement about major cloud DevOps platforms. 4 5 6 7 13
The Product Security Officer
Developers meet the findings where they work: automated review and quality gate on GitHub, Bitbucket, Azure DevOps and GitLab pull requests, a CLI that performs the same checks as the server integration, a documented pre-commit hook running the delta command, and free IDE extensions for JetBrains, VS Code and Visual Studio, plus an AI refactoring add-on in the IDE. We found no public information on triage and suppression handling, the model provider behind the AI refactoring, or typical scan times, which keeps it a step below the top workflow tier. 3 4 6 7 13
The Skeptic
Automated code health reviews gate pull and merge requests on GitHub, Bitbucket, Azure DevOps and GitLab, the CLI performs the same checks locally and slots into a documented pre-commit hook, the delta command inspects new work before it is pushed, and IDE extensions cover the JetBrains suite, the VS Code family and Visual Studio. Quality gates adapt by trend and hotspot rather than absolute values, and an AI refactoring add-on plus a PR refactoring agent act on findings. Unanswered: the model behind the AI fixes, triage and suppression handling, and any scan-time figures. 3 6 7 10 12 13
Platforms, deployment & administration
Show reasoningHide 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.
The Lead Developer
All four hosts we use are supported, there is an open REST API, Jira and further tracker integrations, Azure Entra SSO, organisational accounts, a software portfolio overview, and a documented on-premise self-managed edition with on-premise licensing — the latter matters for our client repositories. We found no public information on SCIM provisioning, audit logs, granular team roles, webhooks, or SARIF/CSV export. 2 7 8 15
The Application Security Engineer
The four major code hosts are supported alongside a public REST API, Jira, Slack and Azure Entra single sign-on, and an on-premise self-managed edition is documented on the pricing and licence-request pages, which matters for our network isolation requirements. But I found no public information on SCIM provisioning, audit logs, granular roles per team, or SARIF/CSV export of findings, which my auditors and SIEM would expect. 3 4 7 8 15
The Engineering Manager
A self-managed on-premise edition is documented with a licence purchase path, Azure Entra single sign-on is listed, a public REST API is documented, and Jira, Trello, Azure DevOps and GitHub Issues integrations exist — the Jira one ties delivery metrics and cost per hotspot to the numbers I take to the board — alongside organisational accounts and portfolio overviews. We found no public information on SCIM provisioning, audit logs, roles and permissions per team, webhooks, or export of findings in formats such as SARIF or CSV. 2 4 7 8 15
The Platform Engineer
The decisive facts for a shop like ours are documented: an on-premise self-managed licence, a public REST API, Azure Entra single sign-on, repository analysis for GitLab, GitHub, Bitbucket and Azure DevOps, Jira integration, organisational accounts, a software portfolio overview and unlimited private repositories. We found no public information on SCIM provisioning, audit logs, SARIF export, or whether self-managed GitLab instances are supported — the pieces I would need to roll this out to 900 repositories. 4 7 8 15
The Product Security Officer
The pieces an operator needs are there: a documented REST API, all four major Git hosts, Jira and project-management integrations, Azure Entra single sign-on, organisational accounts, portfolio-level overviews with monitoring dashboards, PDF reports, and — decisive for us — a self-managed on-premise edition purchasable through the vendor. We found no public information on audit logs, SCIM provisioning, granular role models or SARIF export, which is what holds it back from a higher mark. 7 8 15
The Skeptic
All four major code hosts are supported alongside Jira, Trello and GitHub Issues, an open REST API exists, Azure Entra single sign-on and organisational accounts are offered, and an on-premise self-managed edition is documented with a license purchase page. We found no public information on SCIM provisioning, audit logs, granular per-team permissions, or export of findings in a standard machine-readable format — the only export shown is PDF reports, and the enterprise tier is a sales conversation. 2 7 8 15
Source-code handling, security & compliance
Show reasoningHide 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.
The Lead Developer
ISO 27001 certification is stated, and the on-premise edition plus the locally running CodeHealth MCP give options where analysis stays on our own machines. We found no public information on code retention periods, encryption in transit and at rest, a statement on whether code trains AI models, a public status page, an SLA, or compliance reports mapped to standards such as OWASP, CWE or PCI DSS. 1 8 14 15
The Application Security Engineer
ISO 27001 certification is stated on the homepage and pricing page, though without scope, and that is nearly all the evidence gives me. I found no public information on code retention periods, encryption, whether customer code trains AI models, an SLA or status page, or compliance reports mapped to OWASP, CWE or PCI DSS — the last being what a PCI auditor would ask me to produce. 1 8 13
The Engineering Manager
ISO 27001 certification is stated, an on-premise option exists so code need not leave our network, and the AI guardrails run locally on the developer's machine. We found no public information on retention periods for code and findings, encryption, a statement on whether code trains AI models or an opt-out, a status page or SLA, or compliance reports mapped to OWASP, CWE or PCI DSS. 1 4 8 15
The Platform Engineer
ISO 27001 certification is stated on the home and pricing pages, the MCP component runs locally on the developer machine, and the on-premise edition exists. We found no public information on code retention, encryption, whether customer code trains AI models, a status page, an SLA or audit logging, and no OWASP, CWE or PCI-mapped reporting appears. 1 8 13 14
The Product Security Officer
ISO 27001 is stated, the self-managed on-premise edition and a locally running MCP component give options where controller source code never leaves our own network, and that is genuinely useful for a machine builder under the Cyber Resilience Act. But an auditor of mine would stall there: we found no public information on code retention periods, whether customer code is used to train AI models or how to opt out, the certification's scope, a published SLA or status page, or reports mapped to OWASP, CWE, PCI DSS or the Cyber Resilience Act. 1 8 14 15
The Skeptic
ISO 27001 certification is stated, and the MCP server plus local CodeHealth checks that run on the developer's own machine put some analysis inside the customer's walls. Beyond that, the captured pages say nothing about code retention, encryption, whether code is used to train AI models, a status page, an SLA, or reports mapped to OWASP, CWE or PCI DSS — and the AI refactoring add-on's model provider and data handling are undocumented. 1 4 8 14
European sovereignty
panel opinion
panel disagrees
Show reasoningHide 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.
The Lead Developer
The contracting entity is the Swedish company CodeScene AB, and a documented self-managed on-premise edition plus locally running MCP components let us keep code and findings on our own servers. The cloud edition's regions are listed only as "International" and "United States" with no named EU option, and we found no public information on the hosting infrastructure, subprocessors, or a data processing agreement. 8 14 15
The Application Security Engineer
The contracting entity shown is the Swedish company CodeScene AB, and the pricing page documents an on-premise self-managed deployment option, which gives us a European entity and a path that keeps code on our own servers. Where the cloud edition stores code and findings, who the subprocessors are — including any AI model behind the refactoring add-on — and whether a data processing agreement is published are not shown on the captured pages. 8 9 15
The Engineering Manager
The contracting entity is CodeScene AB, a Swedish company, and a self-managed on-premise edition is documented, which on our own servers would keep code and findings inside our chain; ISO 27001 is stated. The captured pages leave the cloud hosting location unconfirmed, and we found no public information on subprocessors or a published data processing agreement, so I score only the chain the evidence shows. 1 8 9 15
The Platform Engineer
The on-premise, self-managed licence lets us run the analysis on our own servers inside the company network — the customer's own chain — and the vendor presents itself as CodeScene AB, a Swedish company. The cloud chain is unproven on the captured pages: no hosting location, no subprocessor list and no data processing agreement, while the pricing page also offers an AWS purchase route with regions shown only as International and United States. 1 8 15
The Product Security Officer
The contracting entity is the Swedish company CodeScene AB, terms are under Swedish law per the captured provenance, and a self-managed on-premise edition is listed that would place code and findings on our own servers — the customer's own European chain. What the captured pages leave open is the cloud edition: hosting location is unstated, no subprocessors are named, and we found no public information on a published data processing agreement, with an AWS partnership being the only infrastructure hint. 1 8 15
The Skeptic
CodeScene AB is the named entity and a self-managed on-premise edition is documented, which would keep code and findings on the customer's own servers. For the cloud service, however, the captured pricing page offers only 'International' and 'United States' as regions, the vendor presents itself as an AWS partner with a 'Buy with AWS' path, and no captured page states a hosting location, lists subprocessors, or publishes a data processing agreement. 1 8 15
Pricing transparency
Show reasoningHide 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.
The Lead Developer
Standard at "€18 Billed yearly" and Pro at "€27 Billed yearly" are public with a stated 10% yearly saving, a free Community Edition for open source, unlimited private repositories, and named Pro inclusions. We found no public information on how developers or active authors are counted — the difference for us between a predictable bill and one that jumps when a freelancer pushes — nor on the ACE add-on's price or VAT; the on-premise license and Enterprise tier are request and "Talk to sales" based. 8 13 15
The Application Security Engineer
Standard at "€18 Billed yearly" and Pro at "€27 Billed yearly" are public with their main inclusions, a free community edition for open source, unlimited private repositories and a 10% yearly discount; the enterprise tier is talk-to-sales and the AI refactoring add-on and on-premise licences are unpriced. What the price is counted on is only hinted at by a "100+ active authors" figure, so I cannot compute a real annual cost for my 120 developers from these pages alone. 8 13 15
The Engineering Manager
Standard at "€18 Billed yearly" and Pro at "€27 Billed yearly" are public with their main inclusions, and a free Community Edition for open source plus a free trial exist with unlimited private repositories. Enterprise is "Talk to sales", the on-premise licence and the ACE AI refactoring add-on carry no public price, and the pages do not state the counting rule for seats, the monthly figure, or VAT treatment. 8 13 15
The Platform Engineer
Two cloud tiers are public — Standard at €18 billed yearly and Pro at €27 billed yearly, with a stated 10% saving on yearly billing, a free Community Edition for open source, a trial and unlimited private repositories. The counting basis behind the prices is not shown beyond a tier framed around 100+ active authors, Enterprise is quoted as "Talk to sales", the on-premise licence goes through a purchase request form, the ACE add-on carries no price, and VAT treatment is unstated, so I cannot compute our annual cost from these pages. 8 15
The Product Security Officer
Standard at "€18 Billed yearly" and Pro at "€27 Billed yearly" are published with their feature inclusions, a free Community Edition for open-source projects, trials, and a 10% yearly-billing discount. The enterprise tier is "Talk to sales", the on-premise licence runs through a purchase-request form, the AI refactoring add-on carries no public price, and how the price is counted — per developer or otherwise — and VAT treatment are not shown on the captured pages. 8 15
The Skeptic
Standard is '€18 Billed yearly' and Pro '€27 Billed yearly', with a free Community Edition for open-source projects, unlimited private repositories, trials, and 'Save 10% on yearly billing' versus monthly. What I cannot do is compute a real annual cost: the pages never say whether those figures are per developer or something else, how contributors are counted, or how VAT is treated, while the ACE add-on carries no price and Enterprise is 'Talk to sales'. 8 13 15
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?The on-prem option appears only as a plan toggle and a purchase-request form; deployment details and any EU-region choice for the cloud option are not covered in these excerpts. |
1/1 pts | 8 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 CodeScene
Is CodeScene European?
Yes. whats-best.ai classifies CodeScene as EU-Made.
Where does CodeScene store data?
Not stated on the vendor’s pages as of 6 Nov 2026.
Does CodeScene have a free plan?
Not stated on the vendor’s pages as of 6 Nov 2026.
What are the best alternatives to CodeScene?
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: CodeScene alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting options. The on-prem option appears only as a plan toggle and a purchase-request form; deployment details and any EU-region choice for the cloud option are not covered in these excerpts.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 23 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage codescene.com Checked 6 Nov 2026 Details →
- 2 Features page codescene.com Checked 6 Nov 2026 Details →
- 3 Features page (code health) codescene.com Checked 6 Nov 2026 Details →
- 4 Integrations page codescene.com Checked 6 Nov 2026 Details →
- 5 Features page (IDE extensions) codescene.com Checked 6 Nov 2026 Details →
- 6 Features page (CLI and CI gate) codescene.com Checked 6 Nov 2026 Details →
- 7 Documentation codescene.io Checked 6 Nov 2026 Details →
- 8 Pricing page codescene.com Checked 6 Nov 2026 Details →
- 9 About page codescene.com Checked 6 Nov 2026 Details →
- 10 Code analysis (SAST & code quality) — found from sitemap codescene.com Checked 6 Nov 2026 Details →
- 11 Code analysis (SAST & code quality) — found from sitemap codescene.com Checked 6 Nov 2026 Details →
- 12 Developer workflow, quality gates & fixes — found from sitemap codescene.com Checked 6 Nov 2026 Details →
- 13 Developer workflow, quality gates & fixes — found from sitemap codescene.com Checked 6 Nov 2026 Details →
- 14 Platforms, deployment & administration — found from sitemap codescene.com Checked 6 Nov 2026 Details →
- 15 Platforms, deployment & administration — found from sitemap codescene.com Checked 6 Nov 2026 Details →