Panel 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 Snyk Limited · snyk.io
Compare with Aikido Security → Compare with Semgrep → 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.
Snyk at a glance
- Vendor
- Snyk Limited
- 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
- Yes, per the vendor’s own page source, captured 6 Nov 2026
- Panel verdict
- The AI panel rates Snyk 2.5/5, the mean of 6 judges. Snyk is a developer-security platform covering code analysis, open-source dependencies, containers, infrastructure-as-code and secrets. 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
Snyk is a developer-security platform covering code analysis, open-source dependencies, containers, infrastructure-as-code and secrets. The bench scored it strongest on code analysis — five of six judges gave 7 — with developer workflow, dependencies and secrets, integration and administration, and trust and compliance at 6-7, and pricing transparency weakest at 3-4; one judge recorded 0 on every criterion, so each criterion's range spans 0-7, or 0-4 on pricing. Judges credited an event-graph engine with per-framework coverage graded Comprehensive or Partial, taint tracking into template engines, pull-request checks that gate merges, a Jenkins plugin that fails builds at a configurable minimum severity, and fix pull requests. The clearest split among scoring judges is sovereignty, where an Irish-law data processing agreement, EU standard contractual clauses and an EU service region were weighed against a subprocessor chain that includes US-hosted OpenAI and Google Cloud Platform, the latter possibly having access to all customer data. The pricing mechanics are public — 1 credit = $1 — but the public pages show no plan or per-developer price, so an annual cost is not computable from them.
Speaks for it
- Code analysis is documented in depth — an event graph over the source, per-framework support graded Comprehensive or Partial with stated limitations, and taint tracked into template engines.
- Build and merge gating is concrete: pull-request checks gate merges into protected branches, the Jenkins plugin fails builds at a configurable minimum severity, and pre-commit hooks soft-block credentials.
- Secrets detection blends entropy, regex and machine-learning signals, accepts custom regex for proprietary formats, and reads surrounding code to separate live credentials from test fixtures.
- Trust facts are published: ISO 27001, ISO 27017 and SOC 2 Type II audited annually by Schellman, a commitment that inputs are not used to train AI models, and 72-hour security-incident notification.
- Non-US customers contract with Snyk Limited under an Irish-law data processing agreement with EU standard contractual clauses, with an EU service region and AWS hosting electable in the EU.
Held against it
- We found no public information on plan, per-developer or core-scan credit prices — the published rates cover two capabilities (1.0 credits per Active Machine / per Day; 4,000 credits per Assessment) and unused credits expire with the contract term.
- The majority of Snyk APIs are restricted to Enterprise plan customers.
- We found no public information on single sign-on, SCIM provisioning, audit logs, SARIF export or source-code retention periods.
- Accuracy appears only as vendor claims — an 80 percent fix-accuracy figure with no published false-positive rate — and the terms prohibit benchmarking.
- The published subprocessor chain includes US-hosted providers such as OpenAI, Google Cloud Platform and Salesforce, with Google Cloud Platform noted as possibly having access to all customer data.
Best for
- You need interprocedural static analysis with per-framework coverage levels and taint tracking into template engines, with data flow and remediation shown in the IDE.
- Your team gates merges and builds and wants pull-request checks, a Jenkins step that fails builds at a minimum severity, and pre-commit blocking of secrets.
- You must evidence PCI DSS 4.0, the Cyber Resilience Act or OWASP Top 10 with audit-ready compliance reporting.
- You triage open-source risk using reachability, exploit maturity and EPSS/CVSS factors in the risk score.
Avoid if
- You need a public per-developer price to budget with — the public pricing pages carry credit mechanics and two AI capability rates, and the judges could not compute an annual cost from them.
- Your compliance regime cannot accommodate US-hosted subprocessors — the published chain places OpenAI, Google Cloud Platform and Salesforce in the US.
- Your automation depends on the API outside the Enterprise plan — the majority of Snyk APIs are restricted to Enterprise plan customers.
- You must verify detection accuracy independently — the only published figure is a vendor-stated 80 percent fix accuracy, and the terms prohibit benchmarking.
The scores
| Criterion | Panel median |
|---|---|
| Code analysis (SAST & code quality) | 3.5 of 5 |
| Dependencies (SCA), licences & secrets | 3.5 of 5 |
| Developer workflow, quality gates & fixes | 3.5 of 5 |
| Platforms, deployment & administration | 3.5 of 5 |
| Source-code handling, security & compliance | 3.5 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 2 of 5 |
Code analysis (SAST & code quality)
panel disagrees
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
Snyk Code builds an event graph of the codebase and runs rules over it, with per-framework source and sink coverage documented at two support levels (Comprehensive and Partial) and taint tracking that reaches template engines like Twig, Jinja2, Razor and Thymeleaf, so PHP and the other languages we ship in are covered. Findings arrive with their data flow and remediation suggestions, as the Eclipse plugin pages show. We found no public information on a rule language customers can write in, published false-positive rates or maintainability and code-health metrics, and the terms prohibit benchmarking, so we cannot verify the precision claims independently. 16 21 2 6 12
The Application Security Engineer
The code analysis engine builds an event graph of the codebase and runs rules against it, follows taint from application code into template engines such as Jinja2 and Thymeleaf including escaping behaviour, and documents framework support per language at Comprehensive and Partial levels with stated limitations such as possible false negatives in taint analysis. Findings in the IDE carry the data flow and remediation guidance, and infrastructure-as-code results sit in the same dashboard, with documentation covering custom rules for infrastructure-as-code. We found no public information on a customer-writable rule language for application code, on quality metrics such as complexity and duplication, or on published false-positive rates or independent benchmarks; accuracy appears only as vendor claims such as 80%-accurate fixes and 25M+ modelled data flow cases. 16 2 21 4 17
The Engineering Manager
The static analysis engine looks genuinely deep for my Java and Kotlin estate: it builds an event graph of the code, tracks taint into template engines like FreeMarker, Thymeleaf and Velocity, grades framework support as comprehensive or partial with each level's limitations stated, and shows the data flow and remediation for a finding right in the IDE. What I miss for my teams is the whole quality side — the captured pages show no code smells, duplication, complexity, maintainability or technical-debt measures, no coverage import, and no published false-positive figures for the code analysis itself; customer-writable rules are documented only for infrastructure-as-code. 16 2 21 17 24
The Platform Engineer
Code analysis is documented at a depth I can work with: source is turned into an event graph that maps how parts of the code relate, framework support is graded Comprehensive or Partial with sources, sinks, testing depth and known limitations stated per framework, templates are analysed with taint flow from the application code into the template, and the IDE plugins show each finding with its data flow and remediation. We found no public information on bug, code-smell, duplication, complexity, coverage or maintainability measures, and fix accuracy is a vendor-stated 80 percent rather than an independent benchmark, which is what keeps this below the top band. 16 2 21 6
The Product Security Officer
The engine builds an event graph of the code and runs rules over it, with per-framework support graded as Comprehensive or Partial and taint tracked into template engines, and each finding is shown in the IDE with its data flow and remediation — the interprocedural depth I want for controller firmware. We found no public information on a published rule set mapped to OWASP or CWE, on code-quality metrics such as complexity, duplication or coverage, or on benchmarked false-positive rates, which keeps it below the top band. 2 16 17 21
The Skeptic
Snyk Code builds an event graph of the source and runs rules over it — framework support is graded Comprehensive or Partial with stated sources-and-sinks coverage and data-flow testing depth, and the Eclipse plugin shows each finding with its data flow and remediation, so this is real analysis rather than pattern matching. Refreshingly, limits are stated plainly: files over 1MB and filenames over 255 characters are skipped. But we found no public information on a customer-writable rule language for code checks, duplication or complexity metrics, or coverage import, and the only published precision figure we found is an 80% fix-accuracy claim with no false-positive rate or independent benchmark for the SAST engine. 16 21 2
Dependencies (SCA), licences & secrets
panel disagrees
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
Snyk Open Source builds the full dependency tree and flags vulnerable packages anywhere in it, with licence compliance, SBOM support and one-click fix pull requests with customisable templates, and reachability, exploit maturity and EPSS feed the risk score. Secrets detection blends entropy, regex and machine learning with custom regex for proprietary formats, pre-commit hooks that soft-block credentials and merge-request checks that gate protected branches. We found no public information on scanning the full git history, malicious-package detection, or the sources and update speed of the vulnerability database. 3 16 19 4 18
The Application Security Engineer
Composition analysis builds a dependency graph and reports vulnerabilities anywhere in the tree, with licence compliance, SBOM support, dependency cards showing introducing versions, fix pull requests per dependency or in bulk, and prioritization that weighs reachability alongside exploit maturity and EPSS/CVSS scores. Secrets are caught the moment they are written in the IDE, using entropy, regex and machine-learning signals, custom regex for internal token formats, pre-commit soft blocks and merge gating on protected branches. We found no public information on secrets scanned across the full git history, validity checks against providers, malicious-package detection, end-of-life components, or the sources and update speed behind the proprietary vulnerability database. 16 3 19 4 18
The Engineering Manager
Composition analysis builds the full dependency tree and matches it against Snyk's own vulnerability intelligence database, licence compliance and SBOM support ship as plan features, fix pull requests with per-issue selection are documented, and prioritisation explicitly weighs reachability alongside exploit maturity and EPSS or CVSS scores. Secrets are the strongest half: a multi-signal engine combining entropy, regex and machine learning, context reading to separate live credentials from fixtures, real-time IDE detection, pre-commit hooks that soft-block and pull request checks that gate merges. I found no captured information on malicious-package detection, end-of-life components, scanning of the full git history, or validity checks on detected secrets. 3 16 19 4 18 6
The Platform Engineer
Dependency scanning builds the full dependency tree and matches it against Snyk's proprietary vulnerability intelligence, with a risk score that factors in reachability, exploit maturity and EPSS/CVSS, one-click fix pull requests with customisable templates, and container registries including the self-hosted ones we run ourselves (Artifactory, Nexus, Harbor). Secret detection runs across the IDEs, CLI and SCM with entropy, regex and machine-learning signals, custom regex for proprietary token formats, git pre-commit hooks that soft-block commits and merge gates on protected branches. We found no public information on SBOM export formats, malicious-package and end-of-life detection, or scanning of the full git history for secrets. 19 3 5 4 18
The Product Security Officer
Composition analysis builds the full dependency tree including transitive packages against a proprietary vulnerability database, with licence compliance, upgrade and fix pull requests, SBOM support, and prioritisation that weighs reachability, exploit maturity and EPSS — most of what a Cyber Resilience Act filing needs. The captured pages do not state the SBOM export format, and we found no public information on malicious-package detection, end-of-life component flagging, or the vulnerability database's sources; secrets detection is well documented with entropy, regex and machine-learning signals, context checks against test fixtures, and pre-commit soft-blocking. 3 16 18 19 24
The Skeptic
The dependency tree is built and checked against a proprietary vulnerability database, transitive packages included, with licence compliance, SBOM support, fix pull requests and container image scanning in scope — though the database's sources are not documented, and we found no public information on malicious-package detection or end-of-life components. Secrets blends entropy, regex and ML scoring, reads surrounding code to separate a live credential from a test fixture, soft-blocks commits via pre-commit hooks and gates merges — but we found no public information on scanning the full git history or validity checks against providers, and the scanner states it will not detect fake or AI-generated secrets and caps repositories at 800 findings per scan. Reachability appears as one prioritisation factor rather than a documented per-dependency analysis. 16 19 3 4 18
Developer workflow, quality gates & fixes
panel disagrees
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
Every pull request gets status checks and fix pull requests, the Jenkins step can fail builds on issues with a configurable minimum severity, and pre-commit hooks soft-block hardcoded credentials before they land, which is exactly the merge-request gating I want for my team. IDE plugins cover Visual Studio Code, the JetBrains family, Eclipse and Visual Studio, with issue filtering, an ignore approval workflow and data-flow details in the editor. We found no public information confirming that IDE results match the server rules, naming the model behind Agent Fix, or on typical scan times and deduplication across tools. 2 4 5 20 21 18
The Application Security Engineer
Pull request checks gate merges into protected branches, the Jenkins plugin fails builds on issues with a configurable minimum severity of low, medium, high or critical, and IDE plugins for Visual Studio Code, JetBrains, Eclipse and Visual Studio show data flow and remediation in-editor with filters by severity and fixability. False positives run through consistent ignores governed by an approval workflow, fixes arrive as one-click pull requests with customizable templates plus an agent-based automated fix behind the DeepCode AI engine, and CI integrations cover Jenkins, CircleCI, GitHub Actions, Azure Pipelines, TeamCity and Bitbucket. We found no public information on documented typical scan times or on deduplication of findings across tools. 2 3 4 20 21 11
The Engineering Manager
Developers meet findings where they work: status checks on every pull request, a CI/CD security gate, a Jenkins plugin that can fail the build on found issues with a minimum severity setting, IDE plugins for VS Code, Visual Studio, Eclipse and JetBrains showing data flow and remediation inline, and pre-commit protection for secrets. Ignore requests run through an approval workflow, and automated fixes arrive as reviewable pull requests with a claimed 80 percent accuracy. I found no documented baseline that gates only new code against the existing one, no typical scan times, and no stated model behind the automated fixes beyond the DeepCode AI branding. 2 20 21 4 18 19
The Platform Engineer
For my pipelines the decisive detail: a native Jenkins plugin whose fail-on-issues and severity settings can fail the build — though it covers only Snyk Open Source, and code, container and infrastructure-as-code scans must go through the generic CLI. Pull request checks gate merges, pre-commit hooks soft-block commits with credentials, ignores are governed through an approval workflow, fix pull requests let you select issues individually, and the IDE plugins show findings inline in real time. We found no public information on deduplication across tools or typical scan times, and the pages read name DeepCode AI as the engine but not the model provider behind the automated fixes. 20 2 4 18 19 21
The Product Security Officer
Pull request checks on the common hosts, a CI gate that fails the build when issues are found at a configurable minimum severity level, documented Jenkins, GitHub Actions, GitLab and other CI integrations, IDE plugins showing findings with an ignore approval workflow, and one-click fix pull requests with customisable templates put the findings where developers work. We found no public information on documented scan times, deduplication across tools, or the model provider behind the automated agent fixes. 2 5 18 20 21
The Skeptic
Pull request checks gate merges, the Jenkins plugin can fail a build with a minimum-severity setting, pre-commit hooks soft-block secrets before they land, and findings can be ignored through an approval workflow with consistent ignores — the workflow basics are real. Fixes arrive as one-click, customisable pull requests backed by the DeepCode AI engine, with Agent Fix automating them. We found no public information on typical scan times, whether IDE results match the server's rules, or deduplication across tools, so the noise story rests on claims like finding unsafe code "up to 50x faster" rather than documented numbers. 2 4 20 18 21
Platforms, deployment & administration
panel disagrees
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 the hosts we work with are supported — GitHub including self-hosted instances and the Server App for Universal Broker, GitLab, Bitbucket Cloud and Data Center, and Azure Repositories — plus documented REST, V1 and OAuth2 APIs, Jira ticketing, Slack notifications and a Broker component for security and auditability. Roles are genuinely granular, assignable per account, team and target with multiple roles per user, custom user roles on Enterprise, and an EU environment (app.eu.snyk.io) exists. We found no public information on SAML or OIDC single sign-on, SCIM provisioning, customer audit logs or SARIF export, and the majority of the APIs are reserved for Enterprise plan customers. 23 7 22 5 10 3
The Application Security Engineer
GitHub including Enterprise and Server App variants, GitLab, Bitbucket Cloud and Data Center, and Azure Repositories are all supported, with a documented Broker option for greater security and auditability and service environments spanning the US, EU, Australia and government. The REST API ships in REST, V1 and OAuth2 variants though the majority of endpoints are restricted to the Enterprise plan, Jira and Slack sit among 109 listed integrations, and roles map at account, team and target level with multiple roles per user. We found no public information on single sign-on, SCIM provisioning, audit logs, or SARIF import and export. 23 7 5 22 10
The Engineering Manager
All four code hosts are supported including self-managed GitHub Enterprise and Bitbucket Data Center variants, the REST API is documented in three variants, Jira is a first-class integration, and role assignment at account, team and target level — with several roles per user and per-feature permissions — is more granular than most vendors I evaluate. Trend reporting across every repository for leadership is documented, and there is a public status page. But the captured pages say nothing about single sign-on, SCIM provisioning or audit logs, which is the admin spine I need before six teams share a tool, and findings export is described only as API issue reports rather than a named standard format. 23 22 7 5 4 10
The Platform Engineer
All the hosts we run are covered with documented token scopes — self-managed GitLab via personal or group access tokens, GitHub Enterprise, Bitbucket Data Center and Server — plus Jira and ServiceNow ticketing, a documented REST API, roles assignable at account, team and target level, cross-repository reporting with remediation trends, and a European regional instance among the multi-region endpoints. Two things hold it back for a 300-developer insurer: the majority of the APIs are restricted to Enterprise plan customers, and the deployment option documented for restricted networks is a Broker component rather than a self-hosted edition. We found no public information on single sign-on with SAML or OIDC, SCIM provisioning from Entra ID, audit logs, or SARIF export — the documented machine-readable output is JSON. 23 5 7 22 4 10
The Product Security Officer
GitHub including self-hosted Enterprise instances, GitLab, Bitbucket Cloud and Data Center, and Azure Repos are documented down to their token scopes, alongside a REST API in three variants (most of it Enterprise-gated), Jira ticketing, and roles mappable at account, team and target level with multiple roles per user. We found no public information on single sign-on, SCIM provisioning, audit logs, or SARIF export; the Broker improves security of the SCM connection, but a fully self-hosted edition is not documented on the captured pages. 5 7 22 23
The Skeptic
GitHub (including server variants), GitLab, Bitbucket Cloud and Data Center, and Azure Repos are supported, a broker sits between Snyk and the SCM for security and auditability, and roles can be assigned at account, team and target level with multiple roles per user. A REST API is documented alongside V1 and OAuth2 variants, Jira and ServiceNow integrations exist, and detection and remediation trends are reported across every repository for leadership. Three caveats: the majority of Snyk APIs are restricted to Enterprise plan customers only, and we found no public information on single sign-on, SCIM provisioning, audit logs, or SARIF import and export. 23 7 22 3
Source-code handling, security & compliance
panel disagrees
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, ISO 27017 and SOC 2 Type II are stated with annual independent certification by Schellman and a named report window, and capabilities map to SOC 2, ISO 27001, PCI DSS 4.0, the Cyber Resilience Act and OWASP Top 10. The terms commit that customer inputs are not used to train the AI models, security incidents are notified within 72 hours, and a public status page runs on Atlassian Statuspage with a Trust Center behind it. We found no public information on how long source code is retained, on encryption specifics or an option where code never leaves our network, and deletion on termination puts the onus on the customer to delete organizations and projects. 24 25 12 10 9
The Application Security Engineer
Snyk commits that customer inputs will not be used to train or improve AI models, names its generative AI providers (OpenAI, AWS Bedrock, Google Vertex) in the subprocessor list, and holds ISO 27001, ISO 27017 and SOC 2 Type II certified annually by Schellman with the report available through the account team, alongside a public status page and a security portal. Compliance capabilities are explicitly mapped to PCI DSS 4.0, CRA, ISO 27001, SOC 2 and OWASP Top 10 with audit-ready reporting, and security incidents are notified within 72 hours. We found no public information on how long source code itself is retained, and the SLA is referenced as a schedule without its contents published. 12 15 24 25 10 9
The Engineering Manager
The terms state plainly that inputs are not used to train the AI models incorporated in the service, the infrastructure carries ISO 27001, ISO 27017 and a Schellman-audited SOC 2 Type II report obtainable through the account team, a public status page with a published maintenance schedule exists, and an SLA schedule and 72-hour security incident notification are written into the terms. Compliance reporting is mapped to SOC 2, ISO 27001, PCI DSS 4.0, the Cyber Resilience Act and OWASP Top 10. I found no stated retention period for source code and no explicit statement of whether scanned code is stored. 12 24 25 10 15
The Platform Engineer
The terms commit that inputs are not used to train, enhance or improve the AI models in the services beyond customer-specific improvements, a security addendum is published, ISO 27001, ISO 27017 and SOC 2 Type II are audited annually by Schellman with the report available through the account team, security incidents are notified within 72 hours, and a public status page announces quarterly maintenance 30 days ahead. For an audit file the gaps matter: we found no public information on retention periods for source code and findings, on encryption in transit and at rest beyond the referenced addendum, or on an option where code never leaves our network — the Broker is documented for security and auditability of connectivity. Compliance support is mapped to OWASP, PCI DSS 4.0, SOC 2 and the EU Cyber Resilience Act. 12 24 25 9 10
The Product Security Officer
The terms state plainly that inputs are not used to train AI models except for customer-specific improvements that are not shared, ISO 27001, ISO 27017 and SOC 2 Type II are certified annually with the Schellman report available via the account team, there is a public status page, a 72-hour incident-notification commitment, and compliance support mapped to PCI DSS 4.0 and the Cyber Resilience Act with audit-ready reports — directly relevant to my filing. We found no public information on how long source code is retained, where it is stored, or encryption specifics beyond a referenced security addendum. 10 12 24 25
The Skeptic
The terms state plainly that inputs are not used to train, enhance or improve AI models incorporated in the services, ISO 27001, ISO 27017 and a Schellman-audited SOC 2 Type II are certified annually with the report period stated and copies available through the account team, a public status page runs on Atlassian Statuspage, and security incidents are notified within 72 hours. Compliance reporting is mapped to SOC 2, ISO 27001, PCI DSS 4.0, the Cyber Resilience Act and OWASP Top 10. We found no public information on encryption specifics or code retention periods, and deletion on termination falls to the customer with support assistance rather than a stated vendor process. 12 24 25 10
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 Snyk Limited, registered in England and Wales with headquarters in Boston, so there is no EU entity; a GDPR representative sits in Brussels and the data processing agreement names the Irish supervisory authority. The subprocessor list is published with locations, but Google Cloud, which may have access to all customer data, is hosted in the US, as are OpenAI and GCP Vertex for AI features, Salesforce for support and Slack for communications, while AWS and Bedrock can be elected in the EU and an EU environment exists. EU standard contractual clauses, UK and Swiss addenda and objection rights with 30 days' notice are published, which is the baseline safeguard rather than a European chain. 15 14 13 11 10
The Application Security Engineer
Non-US customers contract with Snyk Limited, registered in England and Wales, under a data processing agreement governed by Irish law with EU standard contractual clauses, an Irish supervisory authority and a GDPR representative in Brussels, and an EU service region exists alongside US, Australian and government environments. The subprocessor list is published with locations, showing AWS as the hosting backbone selectable in the US, EU or Australia at the customer's election, alongside US-hosted AI models, analytics and support providers, with transfer safeguards, thirty-day notice and objection rights for subprocessor changes. We found no public information on the parent or ownership structure, or on a default commitment that code and findings are stored in the EU. 14 13 15 10 9
The Engineering Manager
The facts show a UK contracting entity, Snyk Limited registered in England and Wales, with Irish governing law for the data processing agreement, a Brussels GDPR representative, EU standard contractual clauses, EU hosting at the customer's election on AWS alongside a dedicated EU environment, a published subprocessor list with each location, and ISO and SOC certifications. The tempering facts are a Boston-headquartered parent and an AI, analytics and support chain that runs through US providers such as OpenAI, Google Vertex and Salesforce. For a Munich buyer there is a real EU-processed path on paper, but parts of the chain I would depend on sit in the US. 15 14 13 10 11 24
The Platform Engineer
Customers outside the US contract with Snyk Limited, registered in England and Wales, with an EU GDPR representative in Brussels and the Irish supervisory authority named in the data processing agreement, which incorporates EU standard contractual clauses; a European regional endpoint exists and AWS and Auth0 hosting can be elected as EU. The published subprocessor list names each third party with its location, and the chain includes US-hosted generative AI services (OpenAI, Google Vertex), Salesforce for support, Datadog, Segment and Slack — covered by the SCCs but outside the EU. We found no public information on a self-hosted edition that would keep code and findings entirely on our own servers. 14 15 10
The Product Security Officer
Non-US customers contract with Snyk Limited, registered in England and Wales, with an EU representative in Brussels and Irish governing law for the data processing agreement; a dedicated EU deployment region exists and hosting on AWS can be elected in the EU. The subprocessor list is public with locations and purposes — the AI providers OpenAI, AWS Bedrock and Google Vertex all run in the US — with EU standard contractual clauses as the safeguard, but the parent company is headquartered in Boston, so the chain is not European end to end. 10 11 13 14 15
The Skeptic
Customers outside the US contract with Snyk Limited, registered in England and Wales, under a DPA governed by Irish law with a Brussels GDPR representative, published EU SCCs, an Irish supervisory authority, and a subprocessor list published with locations, thirty days' notice and objection rights. But the chain matters: the hosting backbone is AWS at US, EU or Australia at the customer's election, while Google Cloud Platform is US-hosted and "may have access to all Customer Data", and the generative AI providers include US-hosted OpenAI and Google Vertex. We found no public information on where the customer's source code and findings are actually stored. 15 14 13 9
Pricing transparency
panel disagrees
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
Pricing is credit-based with 1 credit = $1, but the only published rates we found are for two AI capabilities (1.0 credits per Active Machine / per Day and 4,000 credits per Assessment), alongside a free tier, an open-source offer and an unpriced flat-rate mention for small teams. The terms state US Dollar billing with taxes borne by the customer, non-refundable fees, credits expiring at term end, overage invoiced in arrears and renewals at Snyk's then-current rates, so the annual cost for our developers and repositories is not computable from public pages alone. We found no public information on a price per developer for the core plans or on how scanning of code, dependencies, secrets or containers consumes credits. 8 12 3
The Application Security Engineer
Pricing runs on a credit model where 1 credit = $1, pre-purchased for the contract term with unused credits expiring, overage invoiced in arrears at then-current rates, mid-contract top-ups, and real-time usage visibility with a per-capability breakdown in the admin dashboard; some AI security capabilities carry stated rates such as 4,000 credits per Assessment and 1.0 credits per Active Machine per Day. A free tier, no-cost access for open source maintainers and simple flat-rate access for small teams are described, with fees payable in US dollars exclusive of taxes that the customer bears. We found no public information on per-developer or per-plan prices for the team and enterprise tiers, or on how code, dependency and container scanning consumes credits. 8 3 12
The Engineering Manager
Pricing is public only in its mechanics: one credit equals one dollar, credits expire with the contract term and are non-refundable, overage is invoiced in arrears, all fees are in US dollars exclusive of taxes the customer bears, and two AI capabilities carry published credit rates, with auto-renewal for one-year terms on 30 days' notice. No plan carries a public price — the small-teams flat rate and the enterprise credit pools both lead to the account team — and how developers or contributors are counted for the core code and dependency scanning is nowhere stated. I cannot compute an annual cost for six teams from these pages. 8 12 3
The Platform Engineer
The credit model is public in outline: one credit equals one dollar, credits are pre-purchased for the contract term, expire unused and are non-refundable and non-transferable, with real-time usage tracking, per-capability breakdowns, consumption alerts and published rates for two capabilities (1.0 credits per active machine per day; 4,000 credits per assessment). But we found no public information on the price of the Team and Enterprise plans, the credit consumption of the core code, dependency, container and secrets scans, or a per-developer counting basis — the terms only add that fees are payable in US dollars excluding taxes and that overage is invoiced in arrears at then-current rates. I cannot compute the annual cost for 300 developers and 900 repositories from public pages. 8 3 12
The Product Security Officer
The pricing page defines the unit exactly — 1 credit = $1 — with published rates for two capabilities (1.0 credits per Active Machine per Day for coding agent security; 4,000 credits per Assessment for AI pentesting), credit expiry at contract end, overage invoiced in arrears, a usage dashboard with alerts, a flat rate for small teams and a free tier for open-source maintainers, plus tax treatment in the terms. We found no public information on what the core scans cost in credits, on the price of the small-teams flat rate, or on per-developer pricing, so the real annual cost cannot be computed from public pages alone. 3 8 12
The Skeptic
The model is credits — 1 credit = $1 — with per-capability rates published for exactly two capabilities ("1.0 credits per Active Machine / per Day" for Evo ADS and 4,000 credits per Assessment for AI Pentesting), but no plan price, no per-developer or per-contributor figure, and no counting rule on the captured pages. The second year is not computable: renewals are priced at Snyk's then-current rates and rate card, unused credits expire with the term, fees are non-cancellable and non-refundable, overage is invoiced in arrears at then-current rates, and everything is payable in US dollars exclusive of taxes. A free tier and a no-cost plan for open-source maintainers exist, and small teams get a flat rate whose amount is not stated. 8 12 3
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
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Published, self-serve | 1/1 pts | 14 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Snyk
Is Snyk European?
No. whats-best.ai classifies Snyk as Rest of world.
Where does Snyk store data?
Not stated on the vendor’s pages as of 6 Nov 2026.
Does Snyk have a free plan?
Yes. Snyk has a free plan, per the vendor’s page captured 6 Nov 2026.
What are the best alternatives to Snyk?
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: Snyk 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 — Legal entity. Not confirmed on the vendor’s own pages as captured.
- 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.
- 15 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
- 10 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
- 9 legal 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 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
- 5 integrations 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
- 4 subprocessors 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
- 2 support 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 data 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. 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 (25)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage snyk.io Checked 6 Nov 2026 Details →
- 2 Features page (SAST) snyk.io Checked 6 Nov 2026 Details →
- 3 Features page (SCA) snyk.io Checked 6 Nov 2026 Details →
- 4 Features page (secrets) snyk.io Checked 6 Nov 2026 Details →
- 5 Integrations page snyk.io Checked 6 Nov 2026 Details →
- 6 Documentation docs.snyk.io Checked 6 Nov 2026 Details →
- 7 API documentation docs.snyk.io Checked 6 Nov 2026 Details →
- 8 Pricing page snyk.io Checked 6 Nov 2026 Details →
- 9 Security / trust page snyk.io Checked 6 Nov 2026 Details →
- 10 Public status page status.snyk.io Checked 6 Nov 2026 Details →
- 11 About page snyk.io Checked 6 Nov 2026 Details →
- 12 Terms of service (names the contracting company) snyk.io Checked 6 Nov 2026 Details →
- 13 Privacy policy snyk.io Checked 6 Nov 2026 Details →
- 14 Data processing agreement (dpa) snyk.io Checked 6 Nov 2026 Details →
- 15 Subprocessor list snyk.io Checked 6 Nov 2026 Details →
- 16 Code analysis (SAST & code quality) — found from sitemap docs.snyk.io Checked 6 Nov 2026 Details →
- 17 Code analysis (SAST & code quality) — found from sitemap docs.snyk.io Checked 6 Nov 2026 Details →
- 18 Dependencies (SCA), licences & secrets — found from sitemap docs.snyk.io Checked 6 Nov 2026 Details →
- 19 Dependencies (SCA), licences & secrets — found from sitemap docs.snyk.io Checked 6 Nov 2026 Details →
- 20 Developer workflow, quality gates & fixes — found from sitemap docs.snyk.io Checked 6 Nov 2026 Details →
- 21 Developer workflow, quality gates & fixes — found from sitemap docs.snyk.io Checked 6 Nov 2026 Details →
- 22 Platforms, deployment & administration — found from sitemap docs.snyk.io Checked 6 Nov 2026 Details →
- 23 Platforms, deployment & administration — found from sitemap docs.snyk.io Checked 6 Nov 2026 Details →
- 24 Source-code handling, security & compliance — found from sitemap snyk.io Checked 6 Nov 2026 Details →
- 25 Source-code handling, security & compliance — found from sitemap snyk.io Checked 6 Nov 2026 Details →