What types of licenses for PVS-Studio do you have?

There are two license types for PVS-Studio:

  • License for a team consisting of one to nine persons.
  • Enterprise License for a large department or even a company (10 persons and more).

What does the license include?

  • the right to use the tool for 1 year;
  • the right to use the product in a team of up to 9 persons, the program being installed only on one computer of each user;
  • if you purchase the Enterprise License, the product can be used by all the developers of your department/division;
  • free updates (including major-versions) for 1 year;
  • user support via e-mail for 1 year.

Can I use the standard license on a build server?

Yes, a build server is an ordinary computer and it needs a licensed tool to be installed on it as well. Our standard license for a team of up to nine developers can be applied to a build server. If you have several build servers and a large developer team, then consider purchasing the Enterprise License.

Are these licenses named licenses (registered to concrete users)?

The license is a pair "name/value" into which some additional information is encoded (including the date). One and the same license is used on all the computers both in case of the standard license (for a team of up to nine persons) and the Enterprise License.

Do you have floating-licenses?

No - because we have very handy Enterprise Licenses. If you think that you need a floating-license, just have a look at our Enterprise Licenses.

Is the license a lifetime one or a limited one?

The license is valid for one year. After that you have to renew it at a discount price for one more year. Renewal process described here.

What will happen after the license expires? Will the program stop working or will I just not be able to get updates?

The program will stop working completely.

Why don't you sell unlimited time licenses?

Because it is not profitable for our business, of course. But this phrase implies more than just our greed.

Static analysis tools require continual maintenance. New compiler versions appear (including service packs), new development environment versions appear, new operating systems and even hardware appear - all this makes us work constantly to develop our product. And our users always get updates.

Besides, we constantly communicate with our users to give them advice on how to harness static analysis in their projects best of all, comment on error messages, explain issues they find in their codes and so on. We have competent developers to handle the user support.

All this demands high expenses and we cannot afford selling unlimited licenses.

OK, sounds convincing, but why don't you let the program work normally and only quit providing updates and user support when the license expires (as some vendors do)?

There are programs which you can buy once and not bother much about updating it. For instance, some dictionary with 20 000 words in version 7 will hardly change greatly and appear to have 40 000 words in version 8. That's why it's not quite reasonable to force users to update to the new version of the dictionary.

Static analysis tools are quite a different thing. The main direction of development of these tools is improving error diagnosis, addition of new diagnostics, elimination of false positives produced by existing diagnostics, etc. That's why we find it strange when somebody tells that he/she wants to use an obsolete set of diagnostic rules without update (there is a big resemblance to antiviruses). We can't make updates free forever (this point was clarified in the previous question).

Static analysis tool developers have two ways to choose here. The first way is to hold back new diagnostics until a major-update and sell it together with them. The second way is to constantly produce updates, including major-releases, during some period of time - for instance, one year. This is how antivirus developers do. This is how we decided to do, too.

I'm not convinced anyway! If the program worked after the license expiration, I would buy it, but not on these terms of yours

Our experience shows that the following thing usually happens. If a user likes our program and it has helped him/her to find interesting errors in a code, he/she will most likely renew it. It doesn't matter for him/her if it will work without renewal. And if a user doesn't like the program (we are not gods and cannot please everybody), again it doesn't matter if the program will work without renewal, as he/she won't use it anyway.

Your prices are too high!

No, they are not. Compare them to Parasoft, Klocwork, Coverity and other static analysis tool developers. But don't compare them to Visual Studio! Even the people from Microsoft themselves tell that their developer tool department is loss-making.

How can I renew the license?

Just write us.

I want to buy Single User License but I can't find it. Why?

You need the license for a team. The reasons are explained in the answer to the question: "Licensing of PVS-Studio: why don't we have Single User License?".

Is there a demo-version of PVS-Studio? Can I download it?

Yes, there is. You can download it. The demo-version's limitations are described here.

The analyzer includes several different rule sets. Can I buy only some of them?

No, you cannot. The analyzer can't be divided.

Where do I enter the registration information after purchasing PVS-Studio?

On the PVS-Studio settings page on the "Registration" tab, as shown here.

Do you work with resellers?

If it is more convenient for you to deal with us through partners, ask your reseller to contact us.

Do you make errors in the code?

Check your code
with PVS-Studio

Static code analysis
for C, C++ and C#

goto PVS-Studio;