138% more reported CVEs per day in 2026 than last year.New: always-on Fixboxes. Vulnerable dependencies, fixed and verified.

Comparison

European software supply chain security tools

Security tools see more of your software than almost anything else you buy: your code, your full dependency inventory, your builds. This page lists European tools by category, with the company behind each one, where it processes your data and whether you can host it yourself, checked on each vendor's own site in November 2026.

Updated

Why origin matters more for security tools

A sovereignty or data-location requirement usually starts with the tools that hold the most sensitive data. Security tools are high on that list: a scanner reads your repository, an SBOM platform holds the inventory of every component you ship, and a build security tool sits inside the build with your secrets present. The more a tool sees, the more its origin and hosting matter.

Category What the tool sees
SCA and application security Manifests and lockfiles, and for SAST your source code
Secrets detection Your code and its history, CI logs and other places secrets leak
Firmware and binary analysis The binaries you ship
SBOM management The full component inventory of every product and version
Build and CI/CD security The build itself: what it fetched, where it connected, and the secrets it used

On this page "European" means a company headquartered in Europe. For each tool, check where its hosted service processes data as well: several European vendors run on US cloud providers' European regions.

SCA and application security

Tool Company Where data is processed Self-hosted
Aikido Security Aikido Security BV, Ghent, Belgium AWS, with data stored in-region for the EU, US, Australia and the Middle East. Says it does not store your code after analysis Partly: a local scanner keeps code on your premises, while findings appear in Aikido's cloud platform
Xygeni Xygeni Security SL, Valladolid, Spain AWS in Ireland (eu-west-1), per its subprocessor list Yes, on-premise on the Enterprise plan
Codacy Qamine Portugal S.A., Lisbon, Portugal AWS; the region is not published No longer available to new customers

Aikido and Xygeni are platforms that combine SCA with SAST, secrets, containers and CI/CD checks; Xygeni also covers malicious packages and build integrity. Codacy is mainly code quality and SAST. For capabilities rather than origin, see SCA tools compared.

Secrets detection

Tool Company Where data is processed Self-hosted
GitGuardian GitGuardian SAS, Paris, France, with a US subsidiary in Cambridge, Massachusetts A US region (Oregon) on every plan; an EU region (Frankfurt) on the Growth and Enterprise plans Yes, on Enterprise, including air-gapped

Firmware and binary analysis

Tool Company Where data is processed Self-hosted
ONEKEY ONEKEY GmbH, Düsseldorf, Germany Not published Yes: cloud and on-premise deployments
Exein Exein S.p.A., Rome, Italy Not published; its privacy policy allows processing inside and, where appropriate, outside the EU Its runtime protection runs on the device; self-hosting of the analysis is not published

Both analyse the firmware you ship and produce SBOMs and vulnerability reports from it; Exein also offers a Yocto layer and on-device runtime protection. For the difference between analysing the output and recording the build, see embedded security tools compared.

SBOM management

Tool Company Where data is processed Self-hosted
Bytesafe SBOM Observer Bitfront AB, Sweden Cloud products hosted in the EU Yes, on the Enterprise plan, including air-gapped
OWASP Dependency-Track An open-source project of the OWASP Foundation, not a vendor Wherever you run it Yes, the only option

See SBOM tools compared for how generators and SBOM managers differ.

Build and CI/CD security: CRACI

Tool Company Where data is processed Self-hosted
CRACI CRACI Corporation Oy, Helsinki, Finland European bare-metal infrastructure, in several data centers in Finland and Sweden Managed today; customer-hosted runners on the roadmap

CRACI runs your GitHub Actions jobs on its own runners and records what each build actually fetched, as an SBOM with a completeness state, under a network egress policy that fails closed. It keeps tracking those components for new vulnerabilities and shows which past builds contained a vulnerable dependency. SBOMs export as CycloneDX or SPDX. CRACI processes your source code in the job's virtual machine and does not store it.

CRACI Corporation Oy's information security management system, for the development and operation of the CRACI platform, is certified to ISO/IEC 27001 by Into Certification. CRACI is GDPR compliant. See what CRACI can reach and security.

Often listed as European, but check the headquarters

  • Snyk was started in London and Tel Aviv and is headquartered in Boston, Massachusetts.
  • Sonar was founded in Switzerland and lists two headquarters, in Geneva and in Austin, Texas. SonarQube Cloud's default region is in the EU.
  • Cybellum is based in Tel Aviv, Israel, and is majority-owned by LG Electronics.
  • Mend.io lists a Boston office, with its parent company in Israel. Checkmarx is registered in Israel.
  • Socket, Sonatype, Endor Labs, Anchore, FOSSA, Black Duck, Cycode, Kusari, Finite State and NetRise are headquartered in the US. JFrog has headquarters in Sunnyvale, California, and Netanya, Israel.

For capabilities across all of them, see software supply chain security tools compared.

Questions to ask any vendor

  1. Which company processes our data, and which law governs the contract?
  2. In which regions, and on whose infrastructure, is our data processed and stored?
  3. Does the tool keep our source code after a scan?
  4. Which subprocessors does it use?
  5. Can we run it on our own infrastructure, and what still depends on the vendor's cloud if we do?
  6. Which certifications does the vendor hold, for which scope?

When CRACI is not the answer

  • You are not on GitHub Actions. CRACI supports GitHub Actions only today, with GitLab CI and Jenkins on the roadmap.
  • You need SAST or secrets scanning. CRACI does not scan source code by design; use a dedicated tool alongside it.
  • You need to analyse firmware you did not build. CRACI records the builds it runs; binary analysis tools examine the output.
  • You need a self-hosted deployment today. Customer-hosted CRACI runners are on the roadmap, not available today.

European supply chain security tools: frequently asked questions

Which software supply chain security tools are European?

Aikido Security (Belgium), Xygeni (Spain), Codacy (Portugal), GitGuardian (France), ONEKEY (Germany), Exein (Italy), Bytesafe's SBOM Observer (Sweden) and CRACI (Finland) are made by companies based in Europe. They cover different jobs: SCA and application security, secrets detection, firmware analysis, SBOM management and build security.

Is there a European alternative to Snyk?

For SCA and application security, Aikido Security (Ghent, Belgium) and Xygeni (Valladolid, Spain) are the closest European options; Codacy (Lisbon, Portugal) covers code quality and SAST. Snyk itself was started in London and Tel Aviv and is headquartered in Boston.

Which SBOM tools are made in Europe?

CRACI (Finland) generates SBOMs from what each build actually fetched. ONEKEY (Germany) and Exein (Italy) produce SBOMs from firmware and device software. Bytesafe's SBOM Observer (Sweden) manages SBOMs, with cloud hosting in the EU. OWASP Dependency-Track is open source and runs wherever you host it.

Where does a security scanner send my code and dependency data?

It depends on the tool, and not every vendor publishes it. Ask which company processes the data, in which regions and on whose infrastructure, whether the tool keeps your code after a scan, which subprocessors it uses, and whether you can run it yourself.

Does a European vendor help with the Cyber Resilience Act?

Origin does not make a tool CRA-ready; what it produces does. The CRA expects manufacturers to know the components in their products and handle their vulnerabilities, so look for SBOMs you can trust and vulnerability tracking across the versions you ship.

See what your build actually ships

Book a demo: run one of your GitHub Actions workflows on CRACI in Finland and Sweden and get its SBOM.

Book a demo