Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

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

by Endor Labs Inc. · www.endorlabs.com

Report an error on this page Is this your product? →

Link to this page

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

Endor Labs at a glance

Vendor
Endor Labs Inc.
Headquarters
Not stated on the vendor’s pages as of 6 Nov 2026
Data hosting
Outside the EU by default source, captured 6 Nov 2026
Free plan
Not stated on the vendor’s pages as of 6 Nov 2026
Panel verdict
The AI panel rates Endor Labs 3.5/5, the mean of 6 judges. Endor Labs — reachability SCA, AI SAST and secrets detection — scores strongest on trust and compliance at 8-9, on a published inventory of what each scan sends — identifiers, file paths, line numbers — and the statement that function bodies and tokens never leave the build machine. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Endor Labs alternatives, European ones first →

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

The Lead Developer

Weighted verdict

Lead developer at a web agency in Cologne with fourteen developers building Laravel, TypeScript and React Native projects for clients on GitHub and GitLab. Wants every merge request checked for bugs, injection flaws and vulnerable packages before review, comments in the merge request rather than a separate dashboard, the same rules in VS Code and PhpStorm, few false positives, and a bill that does not jump each time a freelancer pushes a commit.

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

Scored by The Lead Developer

Panel median The Lead Developer 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 Lead Developer
Code analysis (SAST & code quality) 3 of 5 3.5 of 5
Dependencies (SCA), licences & secrets 4 of 5 4 of 5
Developer workflow, quality gates & fixes 4 of 5 4 of 5
Platforms, deployment & administration 3.5 of 5 3.5 of 5
Source-code handling, security & compliance 4 of 5 4 of 5
European sovereignty 3 of 5 3 of 5
Pricing transparency 1 of 5 1 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 Lead Developer

For a PHP and TypeScript shop this is compelling on the security side: AI SAST traces user-controlled data source-to-sink across multi-file architectures, each finding carries the code location, the data flow trace, a CWE classification with context-based severity, a concrete exploit payload and a suggested fix, and agents pre-classify findings as true or false positive with a written explanation — with a rule-based engine underneath. What the captured pages do not show is a published rule catalogue mapped to OWASP, frameworks listed per language, any duplication, complexity, coverage or maintainability metrics, or independent benchmark results — the multiplier claims are the vendor's own. Deep on taint analysis and false-positive handling, thinner on the quality-metrics half of the question. 1 3 14 15

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

The reachability story is the strongest I have seen documented: dependency-level by default for all supported languages, pre-computed from manifests alone for transitive dependencies, and function-level via call graphs on direct and transitive dependencies — plus malicious package detection with a searchable threat centre, container scanning with code-to-image reachability, SBOM and VEX export, upgrade impact analysis and automatic fix pull requests. Secrets get the full treatment: every branch and commit in git history, validation against the underlying service, pre-commit blocking, and custom rules with validators, entropy and allowlists. The vulnerability database is named but its sources and update speed are not described, and licence handling is SPDX identifiers and summaries — we found no public information on licence policies or per-licence obligations. 2 4 16 17 23

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

Merge gating works the way I want it: an action policy with a Break the Build action plus a required status check, pull request comments on violations, incremental PR scans that surface only new findings against a baseline, and the gating behaviour on GitHub and Azure DevOps documented down to edge cases like neutral checks and status resets. Triage is genuinely good — ignore entries carry a reason and an expiry date, live in a file in the repo, developers can request exceptions in the PR, and thumbs-up/down feedback feeds later scans. The IDE integrations are listed but we found no public information on them running the same rules as the server-side scans, and typical scan times are not documented. 3 15 18 19 21

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

All four code hosts have SCM apps, and GitHub Enterprise Server runs through Outpost, an on-premises scheduler in our own Kubernetes cluster that keeps source code inside our network, alongside a hybrid model where analysis happens in our CI and only metadata leaves. Webhooks are documented in real depth — HMAC signing on by default, Go templates, aggregation modes, namespace propagation — with a REST API, the endorctl CLI, MCP endpoints and Jira. We found no public information on single sign-on beyond identity-provider group claims, SCIM provisioning, audit logs, per-team roles, portfolio reports across repositories or SARIF export. 9 15 20 21 22

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

Unusually good transparency: a per-resource inventory of exactly what a scan sends — identifiers, file paths and line numbers, and the docs state function bodies and tokens never leave the build machine — cloud scans delete source after each scan, AI features are off by default with the model providers named and a written no-training commitment. On the audit side, SOC 2, FedRAMP and ISO 42001 are stated with audit reports at a trust centre, an SLA is published as an exhibit, findings map to PCI DSS and the Cyber Resilience Act, and customer data is deleted within ninety days of request. We found no public information on encryption in transit and at rest, a public status page, or how long findings themselves are retained. 8 9 22 23

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

For an EU tenant the docs name the EU infrastructure — MongoDB Atlas on Azure West Europe, BigQuery in Frankfurt — serve AI models from EU regions, publish a data processing agreement with standard clauses, and list subprocessors with locations and change notification. The contracting party is still Endor Labs Inc. under California law with arbitration in San Francisco (a Netherlands office appears on the about page, but not as the contracting entity), and support, CRM and notification subprocessors sit in the United States while diagnostic logs from our own CI land in a non-EU bucket unless remote logging is switched off. Workable for many clients, but Outpost keeps source local while scan metadata still flows to the hosted tenant, so this is not a sovereign chain end to end. 7 9 13 22

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

The tiers are named — open source and code lines in core and pro, package firewall, agent governance, SBOM hub — and the counting rule is documented: seats are Code Contributors measured over ninety days, with per-seat scan credits under fair-usage limits and extra contributors invoiced quarterly in arrears at the contract rate; a free-forever developer tier and a trial exist. But we found no public price figure for any plan — every amount lives in an Order Form, in USD on net thirty terms with taxes excluded. With quarterly in-arrears overage per contributor, a freelancer who starts committing can move the bill, and I cannot precompute that from public pages. 1 5 9 22

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

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

Hosting location Outside the EU unverified
Why unverified?

The Trust & Compliance documentation says the tenant region (United States or European Union) is only set at onboarding and a dedicated EU-residency environment exists, so this U.S. statement from the privacy policy does not describe EU tenants and no default region is stated there.

0/4 pts 11 Report an error
Hosting options Not determined unverified
Why unverified?

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

— uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

The DPA text is published on the vendor's legal pages but it forms part of the Master Services Agreement and takes effect through the Order Form rather than an online acceptance flow, and the excerpt is truncated before signature or acceptance mechanics.

1/1 pts 12 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Endor Labs

Is Endor Labs European?

No. whats-best.ai classifies Endor Labs as Rest of world.

Where does Endor Labs store data?

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

Does Endor Labs have a free plan?

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

What are the best alternatives to Endor Labs?

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

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

  1. 1 Vendor homepage www.endorlabs.com Checked 6 Nov 2026 Details →
  2. 2 Features page (reachability SCA) www.endorlabs.com Checked 6 Nov 2026 Details →
  3. 3 Features page (SAST) www.endorlabs.com Checked 6 Nov 2026 Details →
  4. 4 Features page (secrets) www.endorlabs.com Checked 6 Nov 2026 Details →
  5. 5 Documentation docs.endorlabs.com Checked 6 Nov 2026 Details →
  6. 6 Pricing page www.endorlabs.com Checked 6 Nov 2026 Details →
  7. 7 About page www.endorlabs.com Checked 6 Nov 2026 Details →
  8. 8 Legal documents www.endorlabs.com Checked 6 Nov 2026 Details →
  9. 9 Terms of service www.endorlabs.com Checked 6 Nov 2026 Details →
  10. 10 Service level agreement www.endorlabs.com Checked 6 Nov 2026 Details →
  11. 11 Privacy policy www.endorlabs.com Checked 6 Nov 2026 Details →
  12. 12 Data processing agreement (dpa) www.endorlabs.com Checked 6 Nov 2026 Details →
  13. 13 Subprocessor list www.endorlabs.com Checked 6 Nov 2026 Details →
  14. 14 Code analysis (SAST & code quality) — found from sitemap docs.endorlabs.com Checked 6 Nov 2026 Details →
  15. 15 Code analysis (SAST & code quality) — found from sitemap docs.endorlabs.com Checked 6 Nov 2026 Details →
  16. 16 Dependencies (SCA), licences & secrets — found from sitemap docs.endorlabs.com Checked 6 Nov 2026 Details →
  17. 17 Dependencies (SCA), licences & secrets — found from sitemap docs.endorlabs.com Checked 6 Nov 2026 Details →
  18. 18 Developer workflow, quality gates & fixes — found from sitemap docs.endorlabs.com Checked 6 Nov 2026 Details →
  19. 19 Developer workflow, quality gates & fixes — found from sitemap docs.endorlabs.com Checked 6 Nov 2026 Details →
  20. 20 Platforms, deployment & administration — found from sitemap docs.endorlabs.com Checked 6 Nov 2026 Details →
  21. 21 Platforms, deployment & administration — found from sitemap docs.endorlabs.com Checked 6 Nov 2026 Details →
  22. 22 Source-code handling, security & compliance — found from sitemap docs.endorlabs.com Checked 6 Nov 2026 Details →
  23. 23 Source-code handling, security & compliance — found from sitemap docs.endorlabs.com Checked 6 Nov 2026 Details →