The solution is scalable. Part of the product is checking the measure rules. It's actually configurable. You can configure which rules you want.

We're only developing in C language. I'm not sure what it offers for different coding languages, however, it likely can scale across languages as well.

We are a multinational corporation and have about 1,500 engineers using the solution. 

Regarding scalability, Klocwork isn't precisely like Acunetix because Klocwork is a static analysis solution for source code, while Acunetix is a web application testing solution that tests your URLs. You can compare Klocwork stability-wise with Coverity, particularly for a small team that's expanding, and in that case, Klocwork is scalable and very simple to upgrade.

I have not issues with scalability. I was able to analyze the Juliet test cases on my baseline machine in three days, and I have got eight processors with 8Gs of memory. However, when I tried to do the same analysis with Fortify, my system died.

I was able to run Fortify's Juliet test cases, but I had to use a big Linux machine. It took 498Gs of memory and a week and a half to finish the analysis.

I didn't have the chance to test it deeply.

It is very scalable.

In our organization, we have 50 users.

It is used on a daily basis. It's one of the most important tools that every developer has.

Scalability is good, from small teams to multisite project teams.

This is a scalable solution and can be deployed to suit any requirement of a customer. We have customers using 1,200 Klocwork licenses, which is served through only one license server.

One can increase the number of vendors, so the solution is scalable. We currently have around 3,000 users.

We have not tried to scale yet, but it was sufficient for our current projects.

We have been trying to scale up this particular tool. We are not only using Klocwork. We are also using other SAST solutions because security cannot be handled by only using one particular tool. Klocwork is the oldest one, but we are using SonarQube and Coverity to filter out more and more defects from our source code. So, it's not really scalable itself, but with the help of other tools, we managed to scale to organization needs.

Currently, we have nine users who are using it in our organization. It is used once a week to give the reports to our security team, and they act on those reports to filter out all the vulnerabilities.

Klocwork has almost all the features what an advanced Static code analyser should have. 

We have a server license here for two servers and ten users.