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

Polyspace Code Prover vs Veracode 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

Polyspace Code Prover
Ranking in Application Security Tools
26th
Average Rating
7.2
Reviews Sentiment
2.3
Number of Reviews
7
Ranking in other categories
No ranking in other categories
Veracode
Ranking in Application Security Tools
3rd
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
208
Ranking in other categories
Static Application Security Testing (SAST) (2nd), Container Security (8th), Software Composition Analysis (SCA) (3rd), Static Code Analysis (1st), Dynamic Application Security Testing (DAST) (1st), Application Security Posture Management (ASPM) (1st)
 

Mindshare comparison

As of March 2026, in the Application Security Tools category, the mindshare of Polyspace Code Prover is 1.3%, up from 1.1% compared to the previous year. The mindshare of Veracode is 4.6%, down from 10.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Security Tools Mindshare Distribution
ProductMindshare (%)
Veracode4.6%
Polyspace Code Prover1.3%
Other94.1%
Application Security Tools
 

Featured Reviews

reviewer2760282 - PeerSpot reviewer
General Manager at a manufacturing company with 10,001+ employees
Has struggled with performance and integration but supports critical safety verification
Execution speed of the tests and generally the integration into AWS-driven CI work chains or workflows represent how it can be improved in my opinion. Performance issues plus license costs are two main driving factors. The CI environments that we use employ up to around 40,000 virtual CPUs per day in peak, running at the same time. We always have problems distributing licenses accordingly with other products. I can talk to the experts doing the integration, but as far as I know, I was involved with Polyspace Code Prover and we had a lot of difficulties integrating it into our Bazel-driven CI toolchain, plus integrating it on the AWS environments in Linux that we use. It was much more straightforward using Code Sonar there. The reason is the execution speed, integration with Azure and stuff, and pricing. The CI integration and maybe a better-suited license model for CI-driven execution are other areas I recommend improving. That's something we discussed with all of the software companies whose products we use, such as compilers. We have a lot of parallel builds, and each call to a license server is actually problematic in the long run.
reviewer2703864 - PeerSpot reviewer
Head of Security Architecture at a healthcare company with 5,001-10,000 employees
Onboarding developers successfully while improving code security through IDE integration
Regarding room for improvement, we have some problems when onboarding new projects because the build process has to be done in a certain way, as Veracode analyzes the binaries and not the code by itself alone. If the process is not configured correctly, it doesn't work. That's one of the things that we are discussing with Veracode. Something positive that we've been able to do is submit formal feature requests to them, and they are working on them; they've already solved some of them. This encourages us to propose new ideas and improvements. Another improvement that we asked for this use case is to be able to configure how Veracode Fix proposes and fixes because sometimes it makes proposals using libraries that go against our architecture design made by the enterprise architecture team. For example, we want them to propose using another library, and that's something we already asked Veracode, and they are working on it. We want to specify when you see this kind of vulnerability, you can only propose these two options.

Quotes from Members

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

Pros

"Efficiency and speed are the advantages I see in Code Sonar over Polyspace Code Prover."
"When we work on safety modules, it is mandatory to fulfill ISO 26262 compliance. Using Prover helps fulfill the standard on top of many other quality checks, like division by zero, data type casts, and null pointer dereferences."
"Polyspace Code Prover has made me realize it differs from other static code analysis tools because it runs the code. So it's quite distinct in that aspect."
"The product detects memory corruptions."
"Polyspace Code Prover is a very user-friendly tool."
"The outputs are very reliable."
"The visibility into application status helps reduce risk exposure for our software. Today, any findings provided by the DAST are reviewed by the developers and we have internal processes in place to correct those findings before there can be a release. So it absolutely does prevent us from releasing weak code."
"I contacted the solution's technical support during the automation part, and it went well, after which I never faced any issues."
"It is scalable and quick to deploy into the site and the pipelines. The reports and analytics are good, and the false positive rate is low. It gives true results."
"Wide range of platforms and technology assessments."
"One of the valuable features is that it gives us the option of static scanning. Most tools of this type are centered around dynamic scanning. Having a static scan is very important."
"The SAST and DAST modules are great."
"Developer Sandboxes help move scanning earlier within the SDLC."
"Their dashboard is really good, overall. In my opinion, it's one of the best in the market, and I say that because we have used other service providers."
 

Cons

"Because we had difficulties in efficiently integrating Polyspace Code Prover into our CI toolchain, these tests are mostly run manually and only occasionally."
"Using Code Prover on large applications crashes sometimes."
"I'd like the data to be taken from any format."
"One of the main disadvantages is the time it takes to initiate the first run."
"The tool has some stability issues."
"Automation could be a challenge."
"The JIRA integration automation aspect of it could be improved significantly. We want to have a way to create tickets that are going to allow people to work through those flaws that we're finding. We don't want people to feel like they're missing out on something or that they're not following directions in the right way."
"Some important languages are not supported."
"We connected with Veracode's support a couple of times, and we got a different answer each time."
"There is much to be desired of UI and user experience. The UI is very slow. With every click, it just takes a lot of time for the pages to load. We have seen this consistently since getting this solution. The UI and UX are very disjointed."
"The current version of the application does not support testing for API."
"It would be nice if Veracode were bundled with some preferred vendors like Salesforce and offered at a discount."
"In some cases we use their APIs; they're not as rich as I would like."
"Because our application is large, it takes a long time to upload and scan."
 

Pricing and Cost Advice

"We use the paid version."
"I think the pricing is in line with the rest of the tools. I think you get what you pay for. It is certainly not inexpensive, but the value proposition is there. There are certainly cheaper tools, but I don't think we'd be getting the support that we get with those, and that is what separates this product from the others."
"We use this product per project rather than per developer... Your development model will really determine what the best fit is for you in terms of licensing, because of the project-based licensing. If you do a few projects, that's more attractive. If you have a large number of developers, that would also make the product a little more attractive."
"Negotiate some, but their prices are reasonable."
"No issues, the pricing seems reasonable."
"Veracode is one of the more expensive solutions in the market, but it is worth the expense because of the eLearning and the security consultations; everything is included in the license."
"Depending on the number of users, my company makes payments toward the solution's licensing costs."
"I think licensing needs to be changed or updated so that it works with adjustments. Pricing is expensive compared to the amount of scanning we perform."
"The cost of scanning code is cheaper. It's typically $0.50 per line of code. However, it's expensive to run a high-level process that would normally require a human security expert. For example, penetration testing costs about $1,000 per application for penetration testing. The cost of these features may be too high for smaller organizations. On the other hand, Veracode's interactive application security testing is fast and cheaper compared to other software."
report
Use our free recommendation engine to learn which Application Security Tools solutions are best for your needs.
884,076 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
36%
Computer Software Company
8%
Aerospace/Defense Firm
6%
Healthcare Company
4%
Financial Services Firm
16%
Computer Software Company
12%
Manufacturing Company
10%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Midsize Enterprise1
Large Enterprise6
By reviewers
Company SizeCount
Small Business69
Midsize Enterprise45
Large Enterprise114
 

Questions from the Community

What needs improvement with Polyspace Code Prover?
Execution speed of the tests and generally the integration into AWS-driven CI work chains or workflows represent how it can be improved in my opinion. Performance issues plus license costs are two ...
What is your primary use case for Polyspace Code Prover?
It is validation for Functional Safety applications in automotive.
What advice do you have for others considering Polyspace Code Prover?
We are actually trying to consolidate everything into one solution. To reduce, that might also be a new solution, but we're not currently actively looking for that. It's just that we'd prefer to fi...
Which gives you more for your money - SonarQube or Veracode?
SonarQube is easy to deploy and configure, and also integrates well with other tools to do quality code analysis. SonarQube has a great community edition, which is open-source and free. Easy to use...
What do you like most about Veracode Static Analysis?
I like its integration with GitHub. I like using it from GitHub. I can use the GitHub URL and find out the vulnerabilities.
What is your experience regarding pricing and costs for Veracode Static Analysis?
My experience with pricing, setup cost, and licensing for Veracode is that it is fairly moderate.
 

Comparisons

 

Also Known As

No data available
Crashtest Security , Veracode Detect
 

Overview

 

Sample Customers

Alenia Aermacchi, CSEE Transport, Delphi Diesel Systems, EADS, Institute for Radiological Protection and Nuclear Safety, Korean Air, KOSTAL, Miracor, NASA Ames Research Center
Manhattan Associates, Azalea Health, Sabre, QAD, Floor & Decor, Prophecy International, SchoolCNXT, Keap, Rekner, Cox Automotive, Automation Anywhere, State of Missouri and others.
Find out what your peers are saying about Polyspace Code Prover vs. Veracode and other solutions. Updated: March 2026.
884,076 professionals have used our research since 2012.