Aikido Security

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

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

by Aikido Security BV · www.aikido.dev

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

Link to this page

Aikido Security: AI-assisted analysis on whats-best.ai Aikido Security: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Aikido Security at a glance

Vendor
Aikido Security BV
Headquarters
Incorporated in Belgium source, captured 6 Nov 2026
Data hosting
Outside the EU by default source, captured 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates Aikido Security 3.5/5, the mean of 6 judges. Aikido Security is a code security and quality platform from Aikido Security BV of Ghent, Belgium. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Aikido Security alternatives, European ones first →

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

The Skeptic

Weighted verdict

Has seen "zero false positives" bury a team under four thousand findings on day one, a "free for open source" plan that counted every bot as a contributor, and an "AI autofix" that shipped the repository to a model in the US. Asks how contributors are counted, which languages get real data-flow analysis rather than regular expressions, what happens to the code after a scan, whether the findings export when the contract ends — and what the second year costs.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Skeptic

Panel median The Skeptic This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Skeptic
Code analysis (SAST & code quality) 3.5 of 5 4 of 5
Dependencies (SCA), licences & secrets 4 of 5 4 of 5
Developer workflow, quality gates & fixes 3.5 of 5 3.5 of 5
Platforms, deployment & administration 3.5 of 5 3.5 of 5
Source-code handling, security & compliance 3.5 of 5 3.5 of 5
European sovereignty 2.5 of 5 2.5 of 5
Pricing transparency 2.5 of 5 2.5 of 5

Code analysis (SAST & code quality)

How this is scored

What the tool finds in the company's own code: static application security testing with data-flow and taint analysis across functions and files, the languages and frameworks covered and at what depth, the rule sets (OWASP Top 10, CWE, custom rules), bugs and code smells, duplication, cyclomatic and cognitive complexity, maintainability and technical-debt measures, test coverage import, infrastructure-as-code checks, and how false positives are measured and kept down.

0 — Does not analyse source code; a dependency, secret or runtime scanner only, or a different kind of product.

3 — Pattern-based rules or linters for a handful of languages; data-flow analysis, the rule list, quality metrics and false-positive handling are basic or not described.

5 — SAST for the common languages (Java, JavaScript/TypeScript, Python, C#, Go, PHP) with the rule list published and mapped to OWASP and CWE, bugs and code smells, duplication and complexity metrics, coverage import, and custom rules or rule configuration documented.

8 — Cross-file taint analysis with the supported frameworks listed per language, a rule language customers can write in, infrastructure-as-code checks, maintainability or code-health scores over time, false-positive rates or benchmarks published, and each finding explained with its data flow and a fix.

10 — Analysis a large polyglot codebase relies on: deep interprocedural analysis across many languages with the depth stated per language, independent benchmark results, quality and security trends per team and hotspot, and every rule documented with examples and its precision.

Report an error

The Skeptic

This is the question I always ask first — which languages get real data-flow — and the answer is documented: tainted input is tracked across multiple files for twelve languages including Java, TypeScript, Python, C# and Go, and within single files only for seven more (Swift, Kotlin, Dart, Elixir and friends), with custom SAST rules, infrastructure-as-code checks via Checkov, and fixes carrying confidence scores. The captured pages give different figures for false-positive reduction — 90% on two pages, 99% on the homepage — and I found no independent benchmark or per-rule precision data behind either number. Findings adjust to context (sensitive repositories upgraded, test files downgraded), and the vendor openly states SAST will not catch logic or authorization bugs that do not match known patterns. 17 2 6 1 8 5

Report an error

Dependencies (SCA), licences & secrets

How this is scored

What comes from outside or should never be committed: software composition analysis of direct and transitive dependencies with the ecosystems and lockfiles supported, the vulnerability database and how quickly it is updated, reachability analysis, licence detection and policies, SBOM export (CycloneDX, SPDX), malicious and typosquatted package detection, end-of-life components, automatic upgrade pull requests, container image scanning, and secret detection in code and git history with the number of detectors, validity checks and revocation guidance.

0 — No dependency or secret scanning of any kind.

3 — Known-vulnerability alerts for dependencies in one or two ecosystems or a basic secret pattern check; transitive dependencies, licences, SBOMs and git history are basic or not described.

5 — SCA for the main ecosystems including transitive dependencies, licence detection with policies, SBOM export in a standard format, upgrade suggestions or pull requests, and secret detection in commits with the detector list described.

8 — Reachability analysis that shows whether vulnerable code is called, malicious-package detection, the vulnerability database and its sources documented, end-of-life components flagged, secrets checked for validity and scanned across the full git history, and push protection that stops a secret before it lands.

10 — Supply-chain coverage a regulated software maker can file: every ecosystem the company builds with, reachability for each, SBOM and VEX output for customers, licence obligations explained per licence, secrets found outside git (tickets, chat, containers) with automated revocation, and the database's coverage and latency evidenced.

Report an error

The Skeptic

Reachability is layered and specific — dependency-level, function-level, and contextual runtime analysis — with malicious-package detection backed by a database of 12k+ known malicious packages across npm, PyPI, GitHub Actions and Maven, and every vulnerability source named one by one (NVD, GitHub Advisory, Debian, Ubuntu, Alpine, Amazon Linux plus Aikido's own pre-CVE feed). Licence handling, EOL detection, SBOM generation and export, container scanning and backported package fixes without breaking changes are all documented. Secrets are checked for liveness and scanned across the entire git history; the detector count and a push-protection mechanism in the SCM itself are the pieces I could not find on the captured pages. 3 7 20 17 4 19 5

Report an error

Developer workflow, quality gates & fixes

How this is scored

Whether developers see and act on the findings where they work: pull and merge request comments and status checks, quality gates that block a merge on new issues, a focus on new code against a baseline, IDE plugins with the same rules as the server, CLI and CI integrations (GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, Bitbucket Pipelines), pre-commit hooks, triage, suppression and ignore rules with reasons, deduplication, fix suggestions and AI autofix with the model behind it, and scan times.

0 — Findings only in a separate report; no pull request, IDE or CI integration.

3 — A CI step or a dashboard of findings; pull request comments, gates, IDE plugins and triage are basic or not described.

5 — Pull or merge request comments and status checks on the common platforms, a configurable quality gate that can fail a build, a new-code baseline, IDE plugins for the common editors, CI integrations documented, and findings that can be ignored or marked as false positives.

8 — IDE results that match the server rules, gates per branch or project with thresholds per severity, pre-commit or push-time checks, deduplicated findings across tools, fix suggestions or AI autofix as a reviewable change with the model provider stated, and typical scan times documented.

10 — A workflow that keeps noise low on a large team: findings routed to the owning team, every suppression audited with a reason and expiry, autofix with its acceptance rates published, and the gate's behaviour on every supported platform documented with its limits.

Report an error

The Skeptic

Gates block merges by severity and type with inline line-level comments in the SCM, IDE plugins cover a long list of editors with in-editor AutoFix and secret warnings before commit, snooze and ignore require reasons with an approval inbox for requests, and deduplication reuses stable issue IDs on every rescan — auto-merge behaviour is even documented per platform including the Bitbucket manual-merge limit. My sticking point: the AI behind AutoFix, Deep Review and AI pentests is never named — no model provider, no statement of where it runs — and we found no public information on a new-code baseline or on autofix acceptance rates. A vendor that wants my repository for its agent has to say whose model sees the code. 2 6 21 24 25 22 5

Report an error

Platforms, deployment & administration

How this is scored

How the tool fits the company: the code hosts supported (GitHub, GitLab, Bitbucket, Azure DevOps) cloud and self-managed, a self-hosted or on-premise edition or a scanner that runs inside the customer's network, a documented REST API and webhooks, issue tracker integrations (Jira), single sign-on (SAML or OIDC) and SCIM, roles and permissions per project and team, portfolio reports across repositories, audit logs, export of findings (SARIF, CSV), and partner or multi-organisation accounts.

0 — One repository at a time with no integrations and no administration.

3 — A web dashboard and one code host; the API, roles, SSO and self-hosted options are basic or not described.

5 — GitHub, GitLab and Bitbucket or Azure DevOps supported, a documented REST API, Jira integration, roles per organisation and project, single sign-on, reports across repositories, and export of findings in a standard format.

8 — Self-managed code hosts supported, a self-hosted edition or an in-network scanner documented, SCIM provisioning, audit logs, granular roles per team, portfolio dashboards with trends, SARIF import and export, and webhooks for findings.

10 — Administration that scales across many teams and business units: every setting reachable by API with parity stated, an air-gapped deployment documented, SSO enforced with SCIM, audit logs exportable to a SIEM, and multi-organisation or partner management.

Report an error

The Skeptic

Four code hosts plus self-managed Bitbucket Data Center, downloadable local scanners for on-prem work, a documented public API with webhooks covering issues, SBOM exports, users, teams and autofix history, Jira/Linear sync, audit trails exportable as CSV or JSON, and a role system granular down to team-only users and per-action rights. We found no public information on single sign-on, SCIM provisioning, or SARIF export, and reporting tops out at trend and PDF reports rather than portfolio dashboards with per-team trends. The broker for internal apps and SIEM integration landing in the Advanced plan is the right shape for enterprises. 2 23 10 8 24 25 9

Report an error

Source-code handling, security & compliance

How this is scored

What the vendor does with the customer's source code and how it holds up in an audit: whether code leaves the customer's network or only results do, where and how long code and findings are stored, whether code or findings are used to train AI models and how to opt out, encryption, the vendor's own certifications (ISO 27001, SOC 2) with their scope, a stated availability or SLA and a public status page, audit logs, and reports mapped to OWASP, CWE, PCI DSS, ISO 27001 or the EU Cyber Resilience Act.

0 — Nothing on how source code is handled, secured or retained.

3 — A security page with general claims; code retention, AI training, certifications and the status page are basic or not described.

5 — How source code is accessed and whether it is stored is described, encryption in transit and at rest, SOC 2 or ISO 27001 stated, a public status page, a statement on whether code trains AI models, and compliance reports mapped to OWASP or CWE.

8 — Code retention periods stated, an option where code never leaves the customer's network, AI features documented with their model provider and an opt-out, certifications with scope and reports available on request, an SLA published, and reports mapped to several standards including PCI DSS or the Cyber Resilience Act.

10 — Source-code handling evidenced end to end: a data-flow diagram of what is sent where, zero retention options, independent audits published with scope, AI processing that can run on the customer's own models, and compliance evidence an auditor can export without asking the vendor.

Report an error

The Skeptic

Source handling is stated plainly and verifiably: git clones run in a fresh ephemeral Docker container per repository, wiped and terminated after analysis, code is not stored, and for GitHub no access or refresh tokens sit in the database under read-only scope by default. SOC 2 Type II, ISO 27001:2022, ISO 42001 and FedRAMP Moderate are stated with unusual honesty about scope — the uncovered SOC 2 criteria (Confidentiality, Processing Integrity, Privacy) are listed outright — and compliance reports map to thirteen frameworks including PCI DSS v4.0 and DORA, with a public status page showing real uptime. What I could not find: any statement on whether code or findings train AI models or how to opt out (an AI Penetration Testing Addendum is listed among the legal documents but its contents are not shown), the model provider, or encryption in transit and at rest. 26 10 25 11 15 18

Report an error

European sovereignty

How this is scored

Who the contracting entity and the parent company are, where source code, findings, SBOMs, account and usage data are stored and processed, and who the subprocessors are (hosting, AI models used for autofix and triage, vulnerability data sources, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Public vulnerability databases and package registries the scanner queries are part of what the product does and are not counted against it; where the customer's code and findings are stored and who processes them is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (AI models, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps code and findings on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The Skeptic

The contracting entity is Belgian to the bone — Aikido Security BV in Ghent with VAT BE0792914919, Belgian governing law and exclusive Belgian jurisdiction — and a data processing agreement plus standard contractual clauses for EEA transfers are published. But the captured privacy policy names both the United States and the European Union as storage locations without saying which a European customer gets, the hosting infrastructure goes unnamed, and a subprocessor list is referenced without the captured pages showing the list or the subprocessors' locations. Until the default region and the chain behind the AI features are on paper, a Belgian entity alone does not make this a sovereign purchase. 15 13 3 26

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per developer, contributor, committer or line of code and per plan, how contributors are counted, what the free tier and open-source plan include, which scanners (SAST, SCA, secrets, containers) and features (SSO, self-hosting, AI autofix, compliance reports) cost extra, limits on repositories, scans or lines of code, minimum seats, monthly versus annual terms, and VAT.

0 — No public prices at all; every customer is a sales call.

3 — A starting price exists, but how developers or lines of code are counted and what the add-ons cost is unclear.

5 — Plans are public with their price per developer or per lines of code and main inclusions, but at least one commonly needed piece (SSO, self-hosting, an extra scanner, AI autofix or the enterprise tier) is unpriced or "contact sales".

8 — Every plan priced publicly with its counting rule (active contributors, lines of code) explained, scanners and add-ons priced, limits on repositories and scans stated, a free or open-source tier with its limits, and monthly and annual terms and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of developers, repositories and lines of code, with every scanner, add-on, self-hosted licence and support level priced and the cancellation and data-export terms published.

Report an error

The Skeptic

Prices are public and flat — Basic $350 / month, Pro $700 / month, Advanced $1,050 / month, each including 10 users, Developer at $0 / free forever including 2 users — with fair-use limits per plan for repositories (10 to 500), cloud accounts, domains and protected requests, and a stated free-tier rescan interval of every 3 days. But the enterprise tier is 'tailored pricing', the Aikido Max AI add-on carries no price at all, and we found no public information on how users beyond the included ten are counted or priced, on annual versus monthly terms, or on VAT treatment. I can price year one for a ten-person team; I cannot price the second developer added or the AI credits consumed. 9

Report an error

European sovereignty — proven facts

3 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Outside the EU unverified
Why unverified?

The policy names both the United States and the European Union as storage locations and is silent on which is the default.

0/4 pts 15 Report an error
Hosting options Self-hostable unverified
Why unverified?

Only the local scanners run on-premises; the Aikido platform itself is otherwise delivered as a cloud service.

1/1 pts 10 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Aikido Security

Is Aikido Security European?

Yes. whats-best.ai classifies Aikido Security as EU-Made. Its vendor, Aikido Security BV, is incorporated in Belgium, per the vendor’s page captured 6 Nov 2026.

Where does Aikido Security store data?

Aikido Security stores customer data outside the EU by default, per the vendor’s page captured 6 Nov 2026.

Does Aikido Security have a free plan?

Yes. Aikido Security has a free plan, per the vendor’s page captured 6 Nov 2026.

What are the best alternatives to Aikido Security?

As of 19 Nov 2026, the panel rates SonarQube (3.5/5), Endor Labs (3.5/5) and Qodana (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: Aikido Security alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (26)

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

  1. 1 Vendor homepage www.aikido.dev Checked 6 Nov 2026 Details →
  2. 2 Features page (SAST) www.aikido.dev Checked 6 Nov 2026 Details →
  3. 3 Features page (SCA) www.aikido.dev Checked 6 Nov 2026 Details →
  4. 4 Features page (secrets detection) www.aikido.dev Checked 6 Nov 2026 Details →
  5. 5 Features page (AI autofix) www.aikido.dev Checked 6 Nov 2026 Details →
  6. 6 Features page (CI/CD gating) www.aikido.dev Checked 6 Nov 2026 Details →
  7. 7 Documentation help.aikido.dev Checked 6 Nov 2026 Details →
  8. 8 API documentation apidocs.aikido.dev Checked 6 Nov 2026 Details →
  9. 9 Pricing page www.aikido.dev Checked 6 Nov 2026 Details →
  10. 10 Security / trust page www.aikido.dev Checked 6 Nov 2026 Details →
  11. 11 Public status page status.aikido.dev Checked 6 Nov 2026 Details →
  12. 12 About page www.aikido.dev Checked 6 Nov 2026 Details →
  13. 13 Terms of service www.aikido.dev Checked 6 Nov 2026 Details →
  14. 14 Terms of service (master subscription agreement) www.aikido.dev Checked 6 Nov 2026 Details →
  15. 15 Privacy policy www.aikido.dev Checked 6 Nov 2026 Details →
  16. 16 Data processing agreement (dpa) www.aikido.dev Checked 6 Nov 2026 Details →
  17. 17 Code analysis (SAST & code quality) — found from sitemap help.aikido.dev Checked 6 Nov 2026 Details →
  18. 18 Code analysis (SAST & code quality) — found from sitemap www.aikido.dev Checked 6 Nov 2026 Details →
  19. 19 Dependencies (SCA), licences & secrets — found from sitemap help.aikido.dev Checked 6 Nov 2026 Details →
  20. 20 Dependencies (SCA), licences & secrets — found from sitemap help.aikido.dev Checked 6 Nov 2026 Details →
  21. 21 Developer workflow, quality gates & fixes — found from sitemap help.aikido.dev Checked 6 Nov 2026 Details →
  22. 22 Developer workflow, quality gates & fixes — found from sitemap help.aikido.dev Checked 6 Nov 2026 Details →
  23. 23 Platforms, deployment & administration — found from sitemap help.aikido.dev Checked 6 Nov 2026 Details →
  24. 24 Platforms, deployment & administration — found from sitemap help.aikido.dev Checked 6 Nov 2026 Details →
  25. 25 Source-code handling, security & compliance — found from sitemap help.aikido.dev Checked 6 Nov 2026 Details →
  26. 26 Source-code handling, security & compliance — found from sitemap www.aikido.dev Checked 6 Nov 2026 Details →