Try our new research platform with insights from 80,000+ expert users

GitGuardian Platform vs GitGuardian Public Monitoring comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 8, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

GitGuardian Platform
Ranking in Application Security Tools
13th
Ranking in Static Application Security Testing (SAST)
9th
Ranking in Data Loss Prevention (DLP)
9th
Average Rating
8.8
Reviews Sentiment
7.4
Number of Reviews
27
Ranking in other categories
Software Supply Chain Security (6th), DevSecOps (5th)
GitGuardian Public Monitoring
Ranking in Application Security Tools
22nd
Ranking in Static Application Security Testing (SAST)
19th
Ranking in Data Loss Prevention (DLP)
23rd
Average Rating
9.0
Reviews Sentiment
7.0
Number of Reviews
2
Ranking in other categories
Threat Intelligence Platforms (18th)
 

Mindshare comparison

As of June 2025, in the Application Security Tools category, the mindshare of GitGuardian Platform is 0.6%, up from 0.3% compared to the previous year. The mindshare of GitGuardian Public Monitoring is 0.2%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Security Tools
 

Featured Reviews

Joan Ging - PeerSpot reviewer
It dramatically improved our ability to detect secrets, saved us time, and reduced our mean time to remediation
While they do offer some basic reporting, more comprehensive reporting would be beneficial in the long run. This would allow me to demonstrate the value of the product over time to continue to effectively budget for this subscription, especially as they add features that may come at an additional cost. I appreciate the improvements made to reporting over the past year, but continued development in this area will be appreciated. We have encountered occasional difficulties with the Single Sign-On process. There is room for improvement in its current implementation. It works, but was not quite as smooth as the rest of the GitGuardian experience.
Theo Cusnir - PeerSpot reviewer
Detects and alerts us about leaks quickly, and enables us to filter and prioritize occurrences
One thing I really like about it is the fact that we can add search words or specific payloads inside the tool, and GitGuardian will look into GitHub and alert us if any of these words is found in a repository. For example, if I put "Payfit" in the tool, I will be alerted every time someone is committing with that word in the code. It's really useful for internal domain names, to detect if someone is leaking internal code. With this capability in the tool, we have good surveillance over our potential blind spots. It can detect a leak in 10 minutes. We had an experience with one of our engineers who had leaked a secret, and 10 minutes afterward we had a warning from GitGuardian about the leak. It's very effective. We looked at the commit date and the current date with hours and minutes and we could see that the commit had been made 10 minutes ago. As a result, we are sure it is pretty fast. Another feature, one that helps prioritize remediation, is that you can filter the findings by criticality. That definitely helps us to prioritize which secrets we should rotate and delete.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The breadth of the solution detection capabilities is pretty good. They have good categories and a lot of different types of secrets... it gives us a great range when it comes to types of secrets, and that's good for us."
"What is particularly helpful is that having GitGuardian show that the code failed a check enables us to automatically pass the resolution to the author. We don't have to rely on the reviewer to assign it back to him or her. Letting the authors solve their own problems before they get to the reviewer has significantly improved visibility and reduced the remediation time from multiple days to minutes or hours. Given how time-consuming code reviews can be, it saves some of our more scarce resources."
"The most valuable feature is the general incident reporting system."
"It's fantastic. We have checked a couple of other vendors and seen their results, which are quite inferior to the amount of detail that the GitGuardian Platform provides. With instantaneous notifications connected to our Slack platform, it allows us to deal quickly with incidents."
"Some of our teams have hundreds of repositories, so filtering by team saves a lot of time and effort."
"The secrets detection and alerting is the most important feature. We get alerted almost immediately after someone commits a secret. It has been very accurate, allowing us to jump on it right away, then figure out if we have something substantial that has been leaked or whether it is something that we don't have to worry about. This general main feature of the app is great."
"GitGuardian has many features that fit our use cases. We have our internal policies on secret exposure, and our code is hosted on GitLab, so we need to prevent secrets from reaching GitLab because our customers worry that GitLab is exposed. One of the great features is the pre-receive hook. It prevents commits from being pushed to the repository by activating the hook on the remotes, which stops the developers from pushing to the remote. The secrets don't reach GitLab, and it isn't exposed."
"I like that GitGuardian automatically notifies the developer who committed the change. The security team doesn't need to act as the intermediary and tell the developer there is an alert. The alert goes directly to the developer."
"One thing I really like about it is the fact that we can add search words or specific payloads inside the tool, and GitGuardian will look into GitHub and alert us if any of these words is found in a repository... With this capability in the tool, we have good surveillance over our potential blind spots."
"The Explore function is valuable for finding specific things I'm looking for."
 

Cons

"We have been somewhat confused by the dashboard at times."
"The purchasing process is convoluted compared to Snyk, the other tool we use. It's like night and day because you only need to punch in your credit card, and you're set. With GitGuardian, getting a quote took two or three weeks. We paid for it in December but have not settled that payment yet."
"There are some features that are lacking in GitGuardian. The more we grow and the more engineers we have, the more it will become difficult to assign an incident because the assignment is not automatic. I know they are working on that and we are waiting for it."
"GitGuardian's hook and dashboard scanners are the two entities. They should work together as one. We've seen several discrepancies where the hook is not being flagged on the dashboard. I still think they need to do some fine-tuning around that. We don't want to waste time."
"An area for improvement is the front end for incidents. The user experience in this area could be much better."
"The analytics in GitGuardian Platform have a significant opportunity to better reflect the value provided to security teams and demonstrate actual activity occurring."
"GitGuardian could have more detailed information on what software engineers can do. It only provides some highly generic feedback when a secret is detected. They should have outside documentation. We send this to our software engineers, who are still doing the commits. It's the wrong way to work, but they are accustomed to doing it this way. When they go into that ticket, they see a few instructions that might be confusing. If I see a leaked secret committed two years ago, it's not enough to undo that commit. I need to go in there, change all my code to utilize GitHub secrets, and go on AWS to validate my key."
"One improvement that I'd like to see is a cleaner for Splunk logs. It would be nice to have a middle man for anything we send or receive from Splunk forwarders. I'd love to see it get cleaned by GitGuardian or caught to make sure we don't have any secrets getting committed to Splunk logs."
"I'm excited about the possibility of Public Postman scanning being integrated with GitGuardian in the future. Additionally, I'm interested in exploring the potential use of honeytokens, which seems like a compelling approach to lure and identify attackers."
"I would like to see improvement in some of the user interface features... When one secret is leaked in multiple files or multiple repositories, it will appear on the dashboard. But when you click on that secret, all the occurrences will appear on the page. It would be better to have one secret per occurrence, directly, so that we don't have to click to get to the list of all the occurrences."
 

Pricing and Cost Advice

"The pricing for GitGuardian is fair."
"It's competitively priced compared to others. Overall, the secret detection sector is expensive, but we are very happy with the value we get."
"I compared the solution to a couple of other solutions, and I think it is very competitively priced."
"We don't have a huge number of users, but its yearly rate was quite reasonable when compared to other per-seat solutions that we looked at... Having a free plan for a small number of users was really great. If you're a small team, I don't see why you wouldn't want to get started with it."
"It's not cheap, but it's not crazy expensive either."
"The internal side is cheap per user. It is annual pricing based on the number of users."
"GitGuardian is on the pricier side."
"I am only aware of the base price. I do not know what happened with our purchasing team in discussions with GitGuardian. I was not privy to the overall contract, but in terms of the base MSRP price, I found it reasonable."
"It's a bit expensive, but it works well. You get what you pay for."
report
Use our free recommendation engine to learn which Application Security Tools solutions are best for your needs.
856,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
23%
Government
15%
Media Company
7%
Financial Services Firm
7%
Government
21%
Computer Software Company
14%
Energy/Utilities Company
14%
Comms Service Provider
11%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about GitGuardian Internal Monitoring ?
It's also worth mentioning that GitGuardian is unique because they have a free tier that we've been using for the first twelve months. It provides full functionality for smaller teams. We're a smal...
What is your experience regarding pricing and costs for GitGuardian Internal Monitoring ?
It's fairly priced, as it performs a lot of analysis and is a valuable tool.
What needs improvement with GitGuardian Internal Monitoring ?
We'd love to see notification updates in Slack, as the system does not provide feedback on updates to incidents, which can be problematic when developers resolve issues. ie. if a developer commits ...
What do you like most about GitGuardian Public Monitoring?
The Explore function is valuable for finding specific things I'm looking for.
What needs improvement with GitGuardian Public Monitoring?
I'm excited about the possibility of Public Postman scanning being integrated with GitGuardian in the future. Additionally, I'm interested in exploring the potential use of honeytokens, which seems...
What is your primary use case for GitGuardian Public Monitoring?
We use GitGuardian Public Monitoring for code that is exposed in public.
 

Also Known As

GitGuardian Internal Monitoring
No data available
 

Overview

 

Sample Customers

Automox, 66degrees (ex Cloudbakers), Iress, Now:Pensions, Payfit, Orange, BouyguesTelecom, Seequent, Stedi, Talend, Snowflake... 
Align Technology, Automox, Fred Hutch, Instacart, Maven Wave, Mirantis, SafetyCulture, Snowflake, Talend
Find out what your peers are saying about GitGuardian Platform vs. GitGuardian Public Monitoring and other solutions. Updated: June 2025.
856,873 professionals have used our research since 2012.