Klocwork vs Polyspace Code Prover comparison

Perforce and MathWorks are both solutions in the Application Security Tools category. Perforce is ranked #23 with an average rating of 8.3, while MathWorks is ranked #18 with an average rating of 7.8. Perforce holds a 1.4% mindshare in AS, compared to MathWorks’s 1.1% mindshare. Additionally, 91% of Perforce users are willing to recommend the solution, compared to 83% of MathWorks users who would recommend it.

Klocwork

Read 20 Klocwork reviews

2,935 Views
1,748 Comparison Views

91% willing to recommend

Polyspace Code Prover

Read 6 Polyspace Code Prover reviews

1,609 Views
1,029 Comparison Views

83% willing to recommend

Klocwork

Polyspace Code Prover

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Oct 8, 2024

Klocwork and Polyspace Code Prover are leading tools in the static code analysis category. Polyspace seems to have the upper hand for its comprehensive analysis capabilities, despite a higher price point.

Features: Klocwork provides integration capabilities with existing development tools, handles large codebases with speed, and offers responsive customer support. Polyspace Code Prover offers deep formal verification, advanced analysis capabilities, and comprehensive code insights, appealing to those seeking detailed software reliability insights.

Room for Improvement: Klocwork could improve the accuracy of its vulnerability detection algorithms, enhance user interface intuitiveness, and provide more comprehensive reporting tools. Polyspace needs to offer a more accessible learning curve, improve integration flexibility with other tools, and streamline its deployment process to reduce setup complexity.

Ease of Deployment and Customer Service: Klocwork is noted for straightforward deployment with seamless integration into existing environments. Its responsive customer service aids in smoother adoption. Polyspace offers extensive documentation and support but may require a more rigorous setup process, preferred by users willing to invest the time for thorough reliability insights.

Pricing and ROI: Klocwork provides a cost-effective solution with favorable ROI for projects requiring rapid integration. Polyspace, with a higher initial investment, offers significant ROI through detailed code verification, appealing to those prioritizing thoroughness over cost.

To learn more, read our detailed Klocwork vs. Polyspace Code Prover Report (Updated: January 2025).

Buyer's Guide

Klocwork vs. Polyspace Code Prover

January 2025

Download the complete report

Helped 831,265 peers since 2012

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

Klocwork

Ranking in Application Security Tools

23rd

Average Rating

8.2

Reviews Sentiment

7.2

Number of Reviews

Ranking in other categories

Static Application Security Testing (SAST) (16th), Static Code Analysis (6th)

Polyspace Code Prover

Ranking in Application Security Tools

18th

Average Rating

7.8

Reviews Sentiment

8.8

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of January 2025, in the Application Security Tools category, the mindshare of Klocwork is 1.4%, down from 1.5% compared to the previous year. The mindshare of Polyspace Code Prover is 1.1%, up from 0.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Application Security Tools

Featured Reviews

AnirbanSarkar

Head - Solution Management Group at Meteonic Innovation Pvt. Ltd.

Lets you find defects during the development phase, so you don't have to wait till the development is over to find and address flaws

What needs improvement in Klocwork, compared to other products in the market, is the dashboard or reporting mechanisms that need to be a bit more flexible. The Klocwork dashboard could be improved. Though it's good, it's not as good as some of the other products in the market, which is a problem. The reporting could be more detailed and easier to sort out because sorting in Klocwork could be a bit more time-consuming, mainly when sorting defects based on filters, compared to how it's done on other tools such as Coverity. What I'd like added in the next release of Klocwork is the peer code review Cahoots which used to be a part of Klocwork, and the architecture analysis and both have been taken out of Klocwork. I found the two critical for specific deployments, so if those can be brought back to Klocwork, that would be very good.

Read full review

Aman Singla

Senior Engineer at a manufacturing company with 10,001+ employees

Easy to setup with reliable outputs and good reliability

It is easy to set up the solution. We can actually modify it using script also. It's pretty easy to link it with our in-house toolchain with the Polyspace configuration settings. If we have small amounts of data, it's quick and you can set it up within ten to 15 minutes. However, depending on the size of the data and the variables, it could take a while since you have to provide a range for all variables. If you have, for example, 500 variables, you'll be configuring a lot. However, the input extremes can be fed using an Excel file or some other format.

Read full review

Quotes from Members

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

Pros

"Klocwork's most valuable feature is the static code analysis feature. It detects the potential problem earlier to allow the developer to receive feedback quickly and then address it before it becomes a problem."

"Technical support is quite good."

"The most valuable feature is the Incremental analysis."

"We like using the static analysis and code refactoring, which are very valuable because of our requirements to meet safety critical levels and reliability."

"The reporting helps us understand the trend of our results and whether we improve over time. We can see the history within Klocwork's server architecture and know that we're making things better. It creates a great story for our management. We can demonstrate value and how our software is developing over time."

"The tool helps the team to think beforehand about corner cases or potential bugs that might arise in real-time."

"I like not having to dig through false positives. Chasing down a false positive can take anywhere from five minutes for a small easy one, then something that is complicated and goes through a whole bunch of different class cases, and it can take up to 45 minutes to an hour to find out if it is a false positive or not."

"One can increase the number of vendors, so the solution is scalable."

More Klocwork pros

"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 outputs are very reliable."

"Polyspace Code Prover is a very user-friendly tool."

"The product detects memory corruptions."

"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."

Cons

"Klocwork has to improve its features to stay ahead of other free solutions."

"This solution could be improved if they offered support of more languages including Ada and Golang. They currently only support seven languages."

"Now the only issue we have is that whenever we need to get the code we have to build it first. Then we can get the report."

"We'd like to see integration with Agile DevOps and Agile methodologies."

"The way to define the rules is too complex. The definition/rules for static analysis could be automated according to various SILs, so as to avoid confusion."

"The main problem is that since it only parses the code, the warnings or the problems that are given as a result of the report can sometimes require a lot of effort to analyze."

"I hope that in each new release they add new features relating to the addition of checkers, improving their analysis engines etc."

"Klocwork does have a problem with true positives. It only found 30% of true positives in the Juliet test case."

More Klocwork cons

"Using Code Prover on large applications crashes sometimes."

"Automation could be a challenge."

"One of the main disadvantages is the time it takes to initiate the first run."

"The tool has some stability issues."

"I'd like the data to be taken from any format."

Pricing and Cost Advice

"The pricing for Klocwork is very competitive if you compare it from apple to apple. It has competitive pricing regarding the licensing model and the per-license cost. Klocwork isn't a high-end investment for anyone deploying it; even SMBs can afford it. The Klocwork cost per user would depend on the license type, so I'm unable to mention a ballpark figure because it would depend on the type of installation and how the deployment will be, and the nodes to give an accurate calculation or figure. The total price depends on the package, so my company could never publish pricing for Klocwork on the website. My team first collects information from potential clients on the deployment scenario, project environment, etc., before suggesting a package for Klocwork. My rating for Klocwork in terms of pricing is a five because of its flexible license models. There's a license model for every type of organization, whether small, midsize, or enterprise, so it's a five out of five for me."

"Klocwork should not to be quite so heavy handed on the licensing for very specific programs."

"When it comes to licensing, the solution has two packages, one for a fixed and the other for a floating server, with the former being more cost effective than the latter."

"Klocwork is still tight on their licensing. If Klocwork would loosen up on the licensing, and where the license could be used, and how many different programs could be run on it, then we have several development programs that I would love to be able to use it for going forward."

"Licensing fees are paid annually, but they also have a perpetual license."

"There are other solutions on the market such as Microsoft Visual Studio. They have been adding more static code analysis features that come for free. It is getting better all the time. That is one of the possibilities is that we've been considering that we may stop using the Klocwork because it doesn't give us any added value."

"This solution offers competitive pricing."

"The limitation that we have is that Klocwork is licensed to certain programs, and if you want to license them to other programs, you have to pay more money."

"We use the paid version."

See which vendors are best for you

Use our free recommendation engine to learn which Application Security Tools solutions are best for your needs.

See recommendations

831,265 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Educational Organization

42%

Manufacturing Company

19%

Computer Software Company

Financial Services Firm

Manufacturing Company

38%

Computer Software Company

13%

Transportation Company

Government

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

Questions from the Community

What do you like most about Klocwork?

It's integrated into our CI, continuous integration.

See all answers

What is your experience regarding pricing and costs for Klocwork?

Our purchasing department is responsible for tracking costs. It's one of the most widely used tools in our organization. It likely does not have a high price point. I don't have insights into licen...

See all answers

What needs improvement with Klocwork?

The main problem is that since it only parses the code, the warnings or the problems that are given as a result of the report can sometimes require a lot of effort to analyze. It will show all poss...

See all answers

What do you like most about 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,...

See all answers

What is your experience regarding pricing and costs for Polyspace Code Prover?

We use the paid version.

See all answers

What needs improvement with Polyspace Code Prover?

I'm still trying to use constraints with range propagation, but I can't get it to work properly, and I haven't found any documentation. It require support. There could be an issue with range propag...

See all answers

Comparisons

SonarQube Server (formerly SonarQube) vs Klocwork

Compared 40% of the time

Coverity vs Klocwork

Compared 31% of the time

Checkmarx One vs Klocwork

Compared 3% of the time

CodeSonar vs Klocwork

Compared 3% of the time

Parasoft SOAtest vs Klocwork

Compared 3% of the time

More Klocwork Competitors

SonarQube Server (formerly SonarQube) vs Polyspace Code Prover

Compared 28% of the time

Coverity vs Polyspace Code Prover

Compared 28% of the time

CodeSonar vs Polyspace Code Prover

Compared 8% of the time

Parasoft SOAtest vs Polyspace Code Prover

Compared 5% of the time

Veracode vs Polyspace Code Prover

Compared 3% of the time

More Polyspace Code Prover Competitors

Product Reports

Buyer's Guide

Klocwork

January 2025

Download Klocwork product report

Buyer's Guide

Polyspace Code Prover

January 2025

Download Polyspace Code Prover product report

Learn More

Perforce

Video not available

MathWorks

Overview

Klocwork detects security, safety, and reliability issues in real-time by using this static code analysis toolkit that works alongside developers, finding issues as early as possible, and integrates with teams, supporting continuous integration and actionable reporting.

Polyspace Code Prover is a sound static analysis tool that proves the absence of overflow, divide-by-zero, out-of-bounds array access, and certain other run-time errors in C and C++ source code. It produces results without requiring program execution, code instrumentation, or test cases. Polyspace Code Prover uses semantic analysis and abstract interpretation based on formal methods to verify software interprocedural, control, and data flow behavior. You can use it on handwritten code, generated code, or a combination of the two. Each operation is color-coded to indicate whether it is free of run-time errors, proven to fail, unreachable, or unproven.

Sample Customers

ACCESS Co Ltd, Risk-AI, Winbond Electronics, Bristol-Myers Squibb Pharmaceutical Research Institute, University of Southern California, Alebra Technologies, SIMULIA, Risk Management Solutions, Brigham Young University, SRD, HRL

Alenia Aermacchi, CSEE Transport, Delphi Diesel Systems, EADS, Institute for Radiological Protection and Nuclear Safety, Korean Air, KOSTAL, Miracor, NASA Ames Research Center

Buyer's Guide

Klocwork vs. Polyspace Code Prover

January 2025

Free Report: Klocwork vs. Polyspace Code Prover

Find out what your peers are saying about Klocwork vs. Polyspace Code Prover and other solutions. Updated: January 2025.

DOWNLOAD NOW

831,265 professionals have used our research since 2012.

See our Klocwork vs. Polyspace Code Prover report.

See our list of best Application Security Tools vendors.

We monitor all Application Security Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.