Sold by
GitGuardian Platform
The end-to-end secrets security platform for enterprises. Scan and fix hardcoded secrets in source code, CI CD pipelines, and productivity tools with GitGuardian code security platform.
Reviews (300)
Rahul K.
Fast, Clear Secret Detection with Easy GitHub Integration
Reviewed on Aug 10, 2026
Review provided by G2
What do you like best about the product?
What I like best about GitGuardian is how quickly it detects exposed secrets and sensitive credentials before they become a security issue. The alerts are clear, and it integrates well with GitHub, making it easy to catch mistakes during development. I also like the dashboard because it gives a good overview without being too complicated. It has definitely helped improve our security practices with very little setup.
What do you dislike about the product?
One thing I don't like is that some alerts can be a bit noisy at times, especially when you're working across multiple repositories. It takes a little time to fine-tune everything and decide which findings need immediate attention. The interface is good overall, but I think navigating historical incidents could be a bit more intuitive. Other than that, I haven't had any major issues with it.
What problems is the product solving and how is that benefiting you?
GitGuardian helps us detect accidentally exposed secrets like API keys, tokens, and passwords before they become a real security risk. Instead of manually checking repositories, we get alerts quickly, which saves time and reduces the chance of sensitive information being leaked. It has also helped improve our development workflow by making developers more aware of secure coding practices. Overall, it gives us more confidence that our repositories are staying secure.
Mir Shahzad Mubeen
Continuous secret monitoring has improved our code security and protected critical workflows
Reviewed on Aug 07, 2026
Review from a verified AWS customer
What is our primary use case?
GitGuardian Platform provides security through secret detection and broader code security. The main benefit is ensuring that secrets are properly managed across our organization.
Honeycomb has many repositories, multiple agents, multiple backends, numerous React frontends, AWS Lambda integrations, automations, third-party APIs, and multiple developers. To manage all of this, we maintain hundreds of secrets to ensure that developers do not commit environment files and that everything is properly secured. GitGuardian Platform scans every commit, branch, pull request, and the entire repository history, which informs us about security gaps and code issues. Because it continuously monitors our system rather than performing just one scan, when a developer pushes code, we receive alerts that are generated immediately. This continuous monitoring capability has made GitGuardian Platform our main solution.
What is most valuable?
GitGuardian Platform offers numerous integrations, including GitHub, GitLab, AWS, email, Jira, and Slack. The continuous monitoring system that watches for pushes as soon as developers commit code is also a valuable feature.
Integration with Slack and Jira allows developers to be notified immediately when a secret is detected, so they can revoke or rotate credentials before they are abused. Jira integration helps us track issues effectively through resolution by automatically creating tickets and assigning ownership.
GitGuardian Platform has provided accurate and reliable output for detecting common secrets and credentials. Most alerts provide sufficient context to investigate and remediate issues properly. From a security perspective, no exposed credentials are shared between branches. When credentials are shared, they are detected easily, and developer awareness around secret management has improved.
What needs improvement?
The automated checks encourage developers to remove or rotate exposed credentials before code is merged. GitGuardian Platform is working well for our organization, and I currently see no needs for improvements. However, deeper integrations with AI development workflows and services would be useful because security is a main concern with the use of AI agents.
I rate GitGuardian Platform a nine out of ten because there is a slight learning curve in integration, and I would have preferred integration with AI-native development workflows. With the increase of AI-focused workflows and incident prioritizations, AI agents need a security system that can flag security leaks. Apart from AI workflow considerations, the platform performs well.
For how long have I used the solution?
I have been using GitGuardian Platform for approximately two years.
What do I think about the stability of the solution?
GitGuardian Platform is stable.
What do I think about the scalability of the solution?
GitGuardian Platform demonstrates good scalability and is well suited for organizations managing multiple repositories and multiple developers with centralized monitoring.
Which solution did I use previously and why did I switch?
We have not used any solution before GitGuardian Platform.
How was the initial setup?
I was not directly involved in evaluating pricing, but the setup from a technical perspective was straightforward.
What was our ROI?
I do not have quantified ROI figures because our team has not tracked them separately. For us, the return is more about reducing security risks and avoiding costs than achieving a direct, measurable financial benefit.
What other advice do I have?
For others considering GitGuardian Platform, I recommend starting by connecting your most critical repositories and running a historical scan to identify any existing exposures. I also recommend integrating it with your pull request workflow and notification tools such as Slack or Jira, so any detected issues are addressed early. Establishing a clear process is crucial, and GitGuardian Platform delivers the most value when it is incorporated into the development workflow rather than used only for occasional scans. I rate this product a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Shemanti P.
Proactive Secrets Detection That Fits Developers’ Workflow
Reviewed on Aug 03, 2026
Review provided by G2
What do you like best about the product?
What I like best about GitGuardian is its proactive approach to developer security. Instead of treating security as a final checkpoint, GitGuardian helps developers detect and remediate exposed secrets early in the development lifecycle. I also appreciate the company's strong focus on developer experience, practical security solutions, and commitment to open-source contributions, which makes security easier to adopt without slowing down development.
What do you dislike about the product?
One limitation is that GitGuardian is primarily focused on secrets detection and remediation. While it integrates well into broader security workflows, organizations still need additional tools for areas like vulnerability management, code quality, or broader application security. That's not necessarily a flaw, but it does mean GitGuardian is one part of a larger security stack rather than a complete security platform.
What problems is the product solving and how is that benefiting you?
GitGuardian solves the problem of exposed secrets—such as API keys, passwords, and tokens—that can accidentally be committed to source code or shared in repositories. These leaks are a common cause of security incidents and can be difficult to detect manually. By continuously scanning repositories and providing remediation guidance, GitGuardian helps teams identify and fix exposed secrets before they can be exploited. As a developer, I benefit from faster feedback, greater confidence when collaborating on code, and a smoother way to incorporate security into the development workflow without relying solely on manual reviews.
Rohit P.
Seamless Workflow Integration with Fast, Reliable Secret Detection
Reviewed on Jul 31, 2026
Review provided by G2
What do you like best about the product?
What I like most about GitGuardian is how seamlessly it fits into our development workflow while making secret detection simple and reliable. The interface is clean and easy to navigate, the integrations with our repositories were straightforward to set up, and scans run quickly without affecting our development process. The alerts provide enough context to understand the issue and fix it efficiently, which has helped us prevent accidental credential leaks before they become security incidents. The documentation and onboarding made it easy to get started, and overall the value it provides in reducing security risks and saving developer time makes it well worth the investment.
What do you dislike about the product?
One area that could be improved is reducing occasional false positives, as some alerts still require manual verification before taking action. I would also like to see more customization options for notification rules and reporting, especially for larger teams managing multiple repositories. While the platform is easy to use overall, some advanced settings can take a bit of time to discover, and more in-app guidance for those features would make the experience even better.
What problems is the product solving and how is that benefiting you?
GitGuardian helps solve the problem of accidentally exposing sensitive credentials like API keys, tokens, and passwords in source code. Instead of relying on manual code reviews to catch these issues, it automatically detects and alerts us early in the development process. This has reduced the risk of security incidents, saved time during reviews, and given our team greater confidence that we're protecting sensitive information before code is merged or deployed.
Antonio Tirado Peña
Automated secret detection has eliminated code leaks and enforces secure commits in pipelines
Reviewed on Jul 30, 2026
Review provided by PeerSpot
What is our primary use case?
I use GitGuardian Platform mainly to prevent and detect exposed credentials, API keys, database connection strings, cloud credentials, and SSH keys within our repository and within the CI/CD pipelines. It works as a safety net that automates everything to ensure the code is clean and can reach production properly and that there are no credential leaks.
When we have made a commit with some secret hardcoded in the code, it has automatically notified us by email saying that the Git commit cannot be done because it has exposed secrets.
We trust it and we see that it is really working. It detects if there is any code leakage, and it is very useful when you have public repositories.
What is most valuable?
The best features offered by GitGuardian Platform are historical scanning, since it incorporates all existing repositories and all legacy repositories. The ability to analyze histories is amazing. It brings to light exposed credentials in old commits, forgotten branches, and it is a pretty good, quite complete standard scanner. It has real-time detection and CI/CD integration. It intercepts secrets in the pipeline itself or through a pre-commit hook. This is useful because you do not even get to make the commit; instead, you detect the leak beforehand. It directly notifies the specific developer so they can fix the problem, which is great.
Regarding CI/CD integration and real-time detection, it has impacted the number of incidents or security leaks we have in the company. In the company we have ISO 27000 and the National Security Scheme, and one of the KPIs we have specifically is security leaks or security breaches. Since we have GitGuardian Platform, secrets in code are better monitored.
The reduction of security leaks since we implemented GitGuardian Platform has been drastic and we have brought the indicator down to zero percent of secrets revealed within the code.
What needs improvement?
GitGuardian Platform has the occasional false positive in testing. Sometimes it detects simulated or dummy keys that are put into unit tests. The management of custom patterns could be a bit more streamlined or a bit more automated, as it detects certain formats with internal tokens.
For how long have I used the solution?
I have been using this tool for two or three years.
What do I think about the stability of the solution?
GitGuardian Platform is super stable, a ten out of ten. It works without any latency, everything working in real time, without penalizing compilation time.
What do I think about the scalability of the solution?
It scales without problems across multiple repositories and developer accounts without loss of performance at peak working hours.
How are customer service and support?
I have not needed to use GitGuardian Platform support.
Which solution did I use previously and why did I switch?
We did not use any similar solution previously.
How was the initial setup?
For costs, we are on the free version for up to twenty-five developers, so we are totally covered. As for the implementation, it is super simple. You open GitHub, open the GitGuardian Platform connector, configure the repositories you want it to monitor, and it is running. The learning curve and monitoring are almost zero. We use GitGuardian Platform's SaaS. What we did was configure it with the GitHub connector, which took just a few clicks, and you just set it to work and notifications and responses start arriving about all your repositories that you share.
What about the implementation team?
We did not evaluate other options initially. We discovered GitGuardian Platform and since the implementation was very fast, the license we use for the number of developers we have in the company is the free one, and everything worked the first time and everything is working perfectly, we have not evaluated other options.
What was our ROI?
I have seen a return on investment by the reduction of security incidents. We have reduced security incidents related to secret leaks.
What's my experience with pricing, setup cost, and licensing?
For costs, we are on the free version for up to twenty-five developers, so we are totally covered.
Which other solutions did I evaluate?
We did not evaluate other options initially. We discovered GitGuardian Platform and since the implementation was very fast, the license we use for the number of developers we have in the company is the free one, and everything worked the first time and everything is working perfectly, we have not evaluated other options.
What other advice do I have?
GitGuardian Platform is a ten. I give GitGuardian Platform a ten because it is super stable, it has no service interruptions, the webhooks and real-time analysis respond with total consistency, without penalizing pull request compilation times. It is very scalable; it has grown as our team has grown. It protects us and we are quite happy with it.
They should try it without any doubt. It is a marvel that fulfills everything it promises. If you are applying shift-left security policies within your company and you want to put a hard stop to credential leaks within your microservices architecture or your cloud infrastructure, GitGuardian Platform is one of the most effective tools I have found on the market. It covers the gap between DevSecOps and development very well. As long as you dedicate some initial time to adjusting exceptions in test environments, it works wonderfully.
I give GitGuardian Platform an overall rating of ten out of ten.
Aquib J.
Great at Catching Accidental Secrets in MRs
Reviewed on Jul 30, 2026
Review provided by G2
What do you like best about the product?
It’s good at finding secrets that have accidentally been included in MRs.
What do you dislike about the product?
It’s not very good at finding SAST static issues in the MR.
What problems is the product solving and how is that benefiting you?
We integrated GitGuardian with our GitLab and local systems, and it has helped a lot with identifying and resolving sensitive data that was being pushed to the repository.
Aswin K.
Seamless GitHub Secret Scanning with High Signal-to-Noise Alerts
Reviewed on Jul 25, 2026
Review provided by G2
What do you like best about the product?
As a small startup where developers move fast and security isn't always the first thing on everyone's mind, GitGuardian fills a gap that genuinely needed filling. The moment you connect it to your repositories, it starts doing something valuable, quietly watching every commit for exposed API keys, tokens, credentials, and secrets that should never have made it into code in the first place.
The automatic scanning of commits and real-time alerts for potential threats are the standout features, and the integration with GitHub is seamless, slotting into our existing workflow without requiring developers to change how they work. That last part matters more than it sounds. Security tools that demand behavioral change from developers tend to get worked around, GitGuardian just sits in the background and does its job.
Software Finder
The true positive rate is impressively high, and the smart alert grouping helps reduce fatigue by consolidating related incidents rather than flooding your inbox with noise. For a lean startup team that can't have someone dedicated to triage all day, that signal-to-noise ratio is genuinely important.
Real-time incident detection and reporting also increase confidence that potential leaks are caught quickly, minimizing the window between a secret being exposed and someone acting on it.
The automatic scanning of commits and real-time alerts for potential threats are the standout features, and the integration with GitHub is seamless, slotting into our existing workflow without requiring developers to change how they work. That last part matters more than it sounds. Security tools that demand behavioral change from developers tend to get worked around, GitGuardian just sits in the background and does its job.
Software Finder
The true positive rate is impressively high, and the smart alert grouping helps reduce fatigue by consolidating related incidents rather than flooding your inbox with noise. For a lean startup team that can't have someone dedicated to triage all day, that signal-to-noise ratio is genuinely important.
Real-time incident detection and reporting also increase confidence that potential leaks are caught quickly, minimizing the window between a secret being exposed and someone acting on it.
What do you dislike about the product?
The mixed experience mostly comes down to three things, false positives, UI friction, and pricing opacity.
False positives are the most consistent frustration, some alerts are overly sensitive, flagging things that aren't actual secrets, which clutters the dashboard and creates extra manual review work. For a small team already stretched thin, spending time validating whether an alert is real or a false flag is friction you didn't budget for.
The UI could be more intuitive, especially in high-stress moments when you've just received an alert and need to quickly understand what leaked and exactly where to fix it. That's precisely the moment you need clarity, and the interface doesn't always deliver it fast enough.
Pricing is another sticking point, it's not always clear upfront what features sit at which price tier, which makes planning and budgeting harder than it needs to be. For a startup watching every dollar, vague pricing tables create unnecessary friction before you've even committed.
TrustRadius
The purchasing process itself can also be convoluted, getting a quote and finalising payments has been known to take longer than expected, which feels out of step with a product aimed at developer teams who expect things to just work.
False positives are the most consistent frustration, some alerts are overly sensitive, flagging things that aren't actual secrets, which clutters the dashboard and creates extra manual review work. For a small team already stretched thin, spending time validating whether an alert is real or a false flag is friction you didn't budget for.
The UI could be more intuitive, especially in high-stress moments when you've just received an alert and need to quickly understand what leaked and exactly where to fix it. That's precisely the moment you need clarity, and the interface doesn't always deliver it fast enough.
Pricing is another sticking point, it's not always clear upfront what features sit at which price tier, which makes planning and budgeting harder than it needs to be. For a startup watching every dollar, vague pricing tables create unnecessary friction before you've even committed.
TrustRadius
The purchasing process itself can also be convoluted, getting a quote and finalising payments has been known to take longer than expected, which feels out of step with a product aimed at developer teams who expect things to just work.
What problems is the product solving and how is that benefiting you?
The core problem it solves is one every startup faces but rarely talks about openly, developers accidentally committing secrets into repositories. It happens faster than anyone expects, especially under deadline pressure, and the consequences of an exposed API key or database credential sitting in a public or even private repo can be severe.
GitGuardian mitigates sensitive data exposure by detecting credentials early, reducing security-related bugs, and bridging the gap between development speed and security discipline, without requiring heavy manual intervention from a security team.
For a small startup without a dedicated security engineer, that kind of automated safety net is genuinely valuable. It catches mistakes before they become incidents and nudges developers toward better habits without being heavy-handed about it.
Bottom line: GitGuardian is worth having in your security stack, especially at startup scale where developer speed and security rigour are constantly in tension. Just go in prepared for some alert tuning, a UI that rewards patience, and a pricing conversation that takes longer than it should.
GitGuardian mitigates sensitive data exposure by detecting credentials early, reducing security-related bugs, and bridging the gap between development speed and security discipline, without requiring heavy manual intervention from a security team.
For a small startup without a dedicated security engineer, that kind of automated safety net is genuinely valuable. It catches mistakes before they become incidents and nudges developers toward better habits without being heavy-handed about it.
Bottom line: GitGuardian is worth having in your security stack, especially at startup scale where developer speed and security rigour are constantly in tension. Just go in prepared for some alert tuning, a UI that rewards patience, and a pricing conversation that takes longer than it should.
Banking
GitGuardian Helps Catch Secrets and PII Before They Reach Remote Repos
Reviewed on Jul 24, 2026
Review provided by G2
What do you like best about the product?
GitGuardian is very helpful for finding secrets and PII that might otherwise get pushed to remote repositories. I think yes
What do you dislike about the product?
It does not currently provide the option to run SAST scans, so having static code analysis available here would be a nice addition.
What problems is the product solving and how is that benefiting you?
Gitguardian offers both a local setup and CI integration, so developers can feel confident that no PII code gets pushed, while the CI pipeline continues to run as expected.
Eleonora B.
User-Friendly, Responsive, and Reliable—Highly Recommended
Reviewed on Jul 24, 2026
Review provided by G2
What do you like best about the product?
Idee friendly website responsive and reliable
Very natural interview
Very natural interview
What do you dislike about the product?
nothing everything works very well, highly recommended
What problems is the product solving and how is that benefiting you?
Job interview
PeterHenggeler
Automated alerts have prevented secret leaks and save us time cleaning repository history
Reviewed on Jul 20, 2026
Review provided by PeerSpot
What is our primary use case?
My main use case for GitGuardian Platform is secret detection.
Every time we open a pull request, it scans the pull request and ensures that we did not accidentally put a database password in a pull request. That process has worked very well for my team as it has caught several things, it is very helpful, and it is easy to use.
What is most valuable?
The best features GitGuardian Platform offers include notification directly to the engineer who created the pull request.
The direct notification feature has helped my engineers and my workflow overall by being effective. It is nice to know that no matter what happens, day or night, if someone puts up a change, they will get an alert, and the security team will get an alert.
GitGuardian Platform has positively impacted our organization as it helps us reduce the number of secrets that we would accidentally commit into source code. We have definitely saved time, as we do not have to go clean out Git history because we can just rotate the secret quickly.
What needs improvement?
I do not have real feedback on how GitGuardian Platform can be improved as I think the team does a good job.
For how long have I used the solution?
I have been using GitGuardian Platform for four years.
What other advice do I have?
My advice to others looking into using GitGuardian Platform is that it is a very quick win to set up and very easy to configure. I would rate this review a 10.