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.

How to contact us

How to contact us

Sep 03 2012

If you want to ask us a question concerning PVS-Studio, its capabilities or ways to purchase it, we'll be glad to answer it. If you have any suggestions or you have noticed a bug in PVS-Studio, we are interested to know it. Well, write to us if you have any questions or suggestions in general. We like participating in discussions. But please give us a chance to answer! It sounds very strange, I know. Let me explain what I mean.

It's very simple to write us a letter! There are two ways to do it:

  • Send a letter to the e-mail address
  • Use the feedback form. This is the best way because it allows both you and us to track the letter history in a convenient way.

Perhaps you'll find this text meaningless. But I'm writing it not without reason. It is both funny and sad. You see, people sometimes choose such non-standard and inconvenient ways of providing feedback that they manage to surprise me all the time. And after that they get upset because they don't receive the answer.

These are the ways I strongly recommend you NOT to use.

  • One of the most horrible ideas is to ask a question in Twitter using the tag @Code_Analysis. While your answer can well fit into 140 characters, the answer cannot. Besides, twitter gets cluttered with correspondence uninteresting to other subscribers.
  • Asking a question to one of our workers in a social network. First, we appear not to be fans of social networks and visit them rarely. Second, a particular worker may not know an answer to your question and he/she will have to play the role of a phone redirecting questions and answers. This is quite inconvenient. Moreover, it makes it very difficult to track our correspondence.
  • Asking a question to one of our workers on a forum or website he/she is registered on (we mean the function "send a private message"). This method implies the same drawbacks as the previous case.
  • Asking a question in comments to our articles published on a third-party website. Unfortunately, subscription mechanisms don't work well on many websites, so we may even not be informed about your comments. Note that on some websites our articles are published by bots (not ours). We may not even know of them.
  • As practice shows, phone calls are also of no use. 100% of phone calls end up with writing letters. We arrange that all agreements, papers concerning payment, etc. will be sent/received via e-mail. The most unreasonable thing is to try discussing a question related to code via phone. You'd better start with a letter right away.
  • Please don't use ICQ, Skype and other IM-programs. Especially when a person you want to contact is offline. We might easily miss your message or you might choose a wrong addressee.

Writing letters to the e-mail address or though the feedback form will significantly simplify our communication. Use these ways and you'll receive the answer very soon. Thanks for understanding.

Popular related articles
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…
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…
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…
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…
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…
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…
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 Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
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…

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 →