GitGuardian Freemium

Secret scanning that catches leaked API keys before attackers do

GitGuardian is a secrets-detection platform that scans Git repositories, CI pipelines and messaging apps for leaked API keys, tokens and passwords. It is free for up to 25 developers, and pricing moves to roughly $25 per developer per month on the Business tier.

What is GitGuardian?

GitGuardian watches for the moment someone commits an AWS secret key, a Stripe live key or a database URI into a repo. It parses commits (not just the current file state) so a secret deleted three commits later still gets flagged.

Detection runs against a pattern library of about 450 credential types plus entropy checks. Every alert carries a validity check: GitGuardian will actually call the provider to see whether the key still works.

How does GitGuardian’s free tier work?

Free for 25 developers, unlimited repositories, on public and private GitHub, GitLab and Bitbucket. Historical scan of up to 8,000 commits per repo on signup. You also get the honeytoken feature — a decoy key you plant and get alerted on when someone uses it.

The paid Business plan (about $25/dev/month at low volume) opens up unlimited commit history, alert auto-assignment, SSO and a longer audit trail. Enterprise adds on-prem and air-gapped scanning.

Product Features

  • Commit-level scanning — catches secrets in history, not only in HEAD.
  • Validity checks — confirms whether a leaked key is live before it wakes you up.
  • ggshield CLI — ggshield secret scan pre-commit blocks a commit locally before it leaves the laptop.
  • Pre-receive hooks — server-side blocking for GitHub Enterprise and GitLab self-hosted.
  • Honeytokens — decoy credentials, 1M characters of decoy volume on free.
  • Chat scanning — Slack and Teams message scanning for pasted credentials on paid plans.

Product Highlights

  • The pre-commit hook is the practical win — most leaks never reach the remote.
  • Validity checking cuts alert noise, which is the usual reason teams ignore secret scanners.
  • Free tier covers a full 25-developer team, not a toy trial.
  • Alert payloads include the commit author, repo and rotation instructions.

Who is it for, and what are the limits?

Fit: any team with a public repo or contractors. One leaked key can cost more than a year of the license, so the math is easy.

Less of a fit: solo developers who keep everything in a private monorepo and already use GitHub’s built-in secret scanning. GitHub’s version is free and now catches around 100 provider patterns, so the overlap is real.

Two honest complaints. First, custom internal patterns require the CLI config, not a dashboard toggle. Second, on the free plan you cannot bulk-close history alerts, and the 8,000-commit backfill will not cover an old monorepo.

Where teams use GitGuardian

  • Blocking a hardcoded Stripe key at the pre-commit stage.
  • Auditing an acquired codebase for old AWS credentials before the migration.
  • Alerting security when a former contractor’s token shows up in a fork.
  • Planting honeytokens in a config file to detect insider access.
  • Clearing SOC 2 evidence requests about secret management controls.

Quick Summary

  • GitGuardian detects leaked API keys, tokens and passwords across Git history, CI and chat.
  • Free for 25 developers with unlimited repos; paid Business is around $25/dev/month.
  • Validity checks plus the pre-commit hook make it quieter and more useful than plain regex scanners.
  • Weaker case for solo devs already relying on GitHub’s built-in secret scanning.