To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (an extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at

If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

Licensing of PVS-Studio: why don't we h…

Licensing of PVS-Studio: why don't we have Single User License?

Mar 11 2012

PVS-Studio has a rather simple licensing scheme now - the basic (usual) version is licensed for a team consisting of up to five developers. There is also the site license for large teams, but we won't dwell upon it here.

This article is out of date. You may find actual information here.

There is no Single User License, and we will try to explain here why.

Let's discuss those cases when a person feels he/she needs Single User License.

One or two persons developing a small project

In this case, there is no sense in buying the PVS-Studio tool. It's not that it does some harm or is not useful; it's just that in case of a small code written by 1-2 programmers you can fight errors manually. The point is that the programmer is familiar with the whole project; it doesn't contain any old unfamiliar legacy code; there are no unskilled programmers participating in development; you don't need to hurry when developing your code.

In this case, using a static analyzer is a decorative component rather than a necessity. Moreover, the trial version of PVS-Studio will be enough, as the project is of a small size. The trial version has a restriction regarding the number of transfers to the code. But you can as well perform navigation through the necessary project fragments without using clicks. It is not very convenient, but since the project is small, this way of navigation will do. Besides, there will be few errors in a small project, so you won't need to pass to the warnings too often.

It appears that you can well use PVS-Studio for free in a small project.

One person maintaining old projects

A person improves already existing projects. Regarding this case, we believe that he/she needs to purchase the team license.

The fact that it's just one or two programmers maintaining a project does not necessarily mean that the project is small. Note that static code analysis tools are often licensed depending on the number of lines in a project. We don't want to make our users count the number of code lines, get into negotiations with sales managers, etc. We want to offer our tool for a certain price, with definite licensing policy, so that it could be easily bought.

Thus, if you maintain an old project, it means there are many code lines in it. I'm sure it was being written by a team of programmers for a long time. So, you need to buy the team license to analyze such a project with PVS-Studio. The project was created by a team, and it doesn't matter that there is only one person to maintain it now. We believe that purchasing the team license is fair in this case.

One programmer or consultant enhancing the quality of code of a large project

It is not a rare situation when one of the team members is given the task to integrate PVS-Studio to analyze a large project. In this case, people often want to buy Single User License proceeding from the idea that only one person is going to use the tool.

Yes, perhaps it is only one person who will use the tool. But the project is a collective one, so the team license should be purchased if you want to check it. In this case, the situation is similar to the one discussed in the previous paragraph. Since the code is big and it is being created by a team of developers, then the PVS-Studio Team License should be purchased.

Creating a lot of small applications to order

We can't imagine a situation when the C++ language can be needed for the purpose of creating many small projects. There are plenty of other languages which are more suitable for quick application development. I can think of only one case when it can be needed: a student who writes term papers to order. But we are not interested in such a case and we don't consider it.

Limited purchasing Single User License "to evaluate"

There can be a situation when a large company studies various tools before buying many licenses (or one big license) and integrating the tool into the software development process. One of the ways is to buy Single User License in order to evaluate the tool.

It's meaningless in case of PVS-Studio: you can easily download it from our website and install on your computer. There are no obstacles for you to overcome like preliminary negotiations with managers and so on. The version you have downloaded is fully operational! There is only one restriction regarding the number of errors you can fix. It means that the trial version is absolutely enough for you to study the product with in every detail.

If you want to find and eliminate all the errors in your project using Single User License, it's not studying but full-scale work. You should purchase the full license to be able to do that.

We want to emphasize once again that the trial version of PVS-Studio provides you with full functionality to study the tool. Technical support is also provided at full extent - just write to us.


If you want to purchase Single User License and haven't found a paragraph describing your case in this article, please write to us. We will consider your situation and try to find a mutually beneficial way of cooperation.

Popular related articles
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →