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.

PVS-Studio team is ready to do regular …

PVS-Studio team is ready to do regular audit of your code

Mar 31 2017

Our team is ready to do the audit of your project code and fix all the found issues on a paid basis. We are talking specifically about C# and C++ projects. However, one-time audit is not the best way to improve the quality and reliability of the code. Thus, we suggest discussing long-term cooperation on the regular audit of your projects.


We are ready to check the projects written in C#, C and C++, but C# projects have a higher priority. Below will be the explanation why it is so. Our specialists can do the analysis of your code, fix all the detected errors and then continue the analysis and bug fixes on a regular basis.

We have the experience of doing this and continue this kind of work. Some projects fall under NDA, which means that I cannot reveal the details about them. Speaking about public projects, here is the example of our collaboration with Epic Games company: How the PVS-Studio Team Improved Unreal Engine's Code.

We also work with a company that has a large code base and various tasks for the work. For example, we ported the code of its projects to the 64-bit platform and fixed the issues there: How to Port a 9 Million Code Line Project to 64 bits?

All the projects were related only to the C++ language, that is why now we are mostly interested in extending this kind of work to the direction of C# language. It is important for us not only to develop the C# analyzer, but to actively use it. We can do this only really working on the code. The one-time check of open source projects is great, but still, not enough.

We have an intention to combine two useful steps: get additional ways of income and improve PVS-Studio.

We offer the companies, who take the quality and reliability of the code seriously, use our services. Each project is unique, that is why the details will be discussed via e-mail and Skype-meetings.

In general, the process will be as follows:

We fix all the errors that will be possible to find for us. Those few errors that we will not be able to fix ourselves, we will report to your developers, who are more familiar with the code. Along the way, we will set up the analyzer in such a way that it does not issue false positives for your code.

We will do this work in parallel with your development process; run your tests ourselves on the code base, so that it does not distract your developers from the main tasks. As a result you will get fixes of hundreds or thousands errors and thus, more reliable and qualitative code.

Further on, we will do regular analysis (every day or every week) and fix newly written issues. There are additional services available: for several companies we developed a new coding standard or renewed the current coding standard.

If this offer sounds interesting for your company, please contact us at to discuss the workload, details and prices.

Popular related articles
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
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…
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…
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…
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…
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…
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…
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…
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…

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 →