GitLab Premium vs Klocwork comparison

"The main benefits I received from GitLab Premium are that I save money and streamline my management process of applications."

"The biggest benefit from GitLab Premium is that both repository management systems are good, as both GitHub and GitLab are valuable, and the main advantage is that GitLab Premium has community support, making it good in all aspects for small organizations."

"The main benefits from advanced CI/CD capabilities in GitLab Premium include automation to pull and merge the codes together, and it's all done automatically."

"GitLab Premium is much more reliable, quicker, faster, and basically easier to operate compared to GitHub."

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

"It's integrated into our CI, continuous integration."

"The most valuable feature of Klocwork is finding defects while you're doing the coding. For example, if you have an IDE plug-in of Klocwork on Visual Studio or Eclipse, you can find the faults; similar to using spell check on Word, you can find out defects during the development phase, which means that you don't have to wait till the development is over to find the flaws and address the deficiencies. I also find language support in Klocwork good because it used to support only C, C++, C#, and Java, but now, it also supports Java scripts and Python."

"The best advantage of Klocwork is the reduced setup time."

"Technical support is quite good."

"The ability to create custom checkers is a plus."

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

"There is a central Klocwork server at our headquarter in France so we connect the client directly to the server on-premises remotely."

"The biggest drawbacks of GitLab Premium are GUI and configuration. GUI is the primary concern, but other aspects are good."

"The automation part could be improved. Nowadays AI is being actively used, and if we could integrate something like ChatGPT with GitLab Premium, it would be easier for us to check logs and debug faster."

"Klocwork sometimes provides too many additional warnings which require expertise to manage."

"Even though it does the job, there's room for feature enhancements, such as integrations with Git for better tracking and notifications."

"Under NIST cybersecurity standards, we must address vulnerabilities within a specified time after discovering them. When we try to propagate those updates and fixes through the system, it would be nice if the clients could reconnect to the existing server or have the server dynamically updated in some way. I know that isn't easy, but maybe processes could be enhanced to make that more streamlined from a DevOps perspective."

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

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

"Customers using different static analysis tools report more issues than with Klocwork, indicating that Klocwork's engine is not as superior."

"There are too many warnings, and it requires expertise to determine the correct category for them."

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

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

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

"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 should not to be quite so heavy handed on the licensing for very specific programs."

"This solution offers competitive pricing."

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

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