GitGuardian

Name: GitGuardian
Brand: GitGuardian
Rating: 4.8 (318 reviews)

The end-to-end platform for Secrets Security.

Est 2017|Valuation $276.5M|Raised $108M|28 Ref Customers

LinkedIn 16K|Web traffic 8K|FTEs 150|HQ Paris, France

MarketsSecret Scanning

01Common complaints

1. Organizations that primarily want a free/DIY toolchain and have engineering capacity to build triage workflows should consider open-source scanners such as **Gitleaks** or **TruffleHog OSS**. 2. Organizations seeking a single consolidated AppSec suite (SAST + SCA + IaC + Containers + Secrets) with unified procurement should evaluate **Snyk** or **GitHub Advanced Security** first. 3. Organizations with strict data handling requirements that cannot accommodate SaaS scanning or external APIs. Although GitGuardian offers self-hosted options at Enterprise, that may not align with all budgets or operational models. 4. Small teams that are sensitive to alert volume and cannot allocate time for tuning, since initial alert noise and false positives are reported by multiple users. 5. Organizations that require SCIM support beyond Okta and Microsoft Entra ID as documented; this may limit identity automation for some environments.

Known limitations from public docs / sources

SCIM scope: documented support for Okta and Microsoft Entra ID.
EU hosting migration: the vendor’s EU hosting announcement indicated migration from US to EU was not offered at that time.
Closed-source detection engine: ggshield is open-source, but the underlying detection engine used by the vendor’s public API and platform is described as closed-source.

Common limitations reported by users

False positives and alert fatigue
UI/UX improvements desired (navigation and incident sorting)
Some users request more automated remediation or smoother coordination between security and application teams

02Why they buy

Supported by customer feedback and observable signals

Rapid detection with contextual data is frequently mentioned in reviews (line-level pinpointing and rapid alerts).
Developer workflow integration (ggshield hooks, CI usage) is emphasized in documentation and user reports.

Claims requiring verification

The vendor reports a high proportion of true positives and large-scale scanning metrics. Prospective purchasers should request measurement methodology, sampling approach, and details on how feedback is collected.

Where competitors have advantages

Open-source tools: provide transparency and local control without vendor dependencies.
Broader AppSec platforms: may reduce vendor sprawl by covering multiple security categories under one vendor and procurement process.

01Common complaints

Organizations that primarily want a free/DIY toolchain and have engineering capacity to build triage workflows should consider open-source scanners such as Gitleaks or TruffleHog OSS.
Organizations seeking a single consolidated AppSec suite (SAST + SCA + IaC + Containers + Secrets) with unified procurement should evaluate Snyk or GitHub Advanced Security first.
Organizations with strict data handling requirements that cannot accommodate SaaS scanning or external APIs. Although GitGuardian offers self-hosted options at Enterprise, that may not align with all budgets or operational models.
Small teams that are sensitive to alert volume and cannot allocate time for tuning, since initial alert noise and false positives are reported by multiple users.
Organizations that require SCIM support beyond Okta and Microsoft Entra ID as documented; this may limit identity automation for some environments.

Known limitations from public docs / sources

SCIM scope: documented support for Okta and Microsoft Entra ID.
EU hosting migration: the vendor’s EU hosting announcement indicated migration from US to EU was not offered at that time.
Closed-source detection engine: ggshield is open-source, but the underlying detection engine used by the vendor’s public API and platform is described as closed-source.

Common limitations reported by users

False positives and alert fatigue
UI/UX improvements desired (navigation and incident sorting)
Some users request more automated remediation or smoother coordination between security and application teams

02Why they buy

Supported by customer feedback and observable signals

Rapid detection with contextual data is frequently mentioned in reviews (line-level pinpointing and rapid alerts).
Developer workflow integration (ggshield hooks, CI usage) is emphasized in documentation and user reports.

Claims requiring verification

The vendor reports a high proportion of true positives and large-scale scanning metrics. Prospective purchasers should request measurement methodology, sampling approach, and details on how feedback is collected.

Where competitors have advantages

Open-source tools: provide transparency and local control without vendor dependencies.
Broader AppSec platforms: may reduce vendor sprawl by covering multiple security categories under one vendor and procurement process.

GitGuardian

01Common complaints

Known limitations from public docs / sources

Common limitations reported by users

02Why they buy

Supported by customer feedback and observable signals

Claims requiring verification

Where competitors have advantages

03Field reports

04Best fit

05The pitch

01Common complaints

Known limitations from public docs / sources

Common limitations reported by users

02Why they buy

Supported by customer feedback and observable signals

Claims requiring verification

Where competitors have advantages

03Field reports

04Best fit

05The pitch