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.

We have moved to a new office! See phot…

We have moved to a new office! See photos below...

Mar 21 2013

Our team has moved to a new office situated at the following address: Office 308, 39 Revolyutsii St., Tula, Russia, 300034. It's this address that mail should be sent to, while our registered address remains the same: 70-1-88 Metallurgov St., Tula, Russia, 300027. Now we invite everyone to look at the photos of our new workplace!

We have many computers and monitors, of course.


But we've put the cases on special stands so that they don't clutter the desks.


Thanks to a duct for the local and electrical networks, we can now do without awful webs of wiring and extension cords spread on the floor.


By the way, as you can see, case stands are convenient to put bags and backpacks on.

It's nice when you have plenty of space on your desk.


Some prefer laptops.


When visiting programmer teams, you are always sure to find books by Knuth in their bookcase - and network equipment behind it.


Aluminum window blinds and an air conditioner protect us from the sun and its heat.


Besides computers we need a recreation room, of course.


This room is also used to hold some conversations, so we have diplomas, achievement awards, and some funny stuff on the walls.


Did you notice the circle in the middle? You think it's a shaman drum?


That's right. The guys from Intel presented it to us. It helps when you need to fix a bug (at least, this is what the inscriptions on it promise).

It's the place where we extract water.


And this is where we warm up food.


One more present from Intel by the door.


The inscription reads: "A horseshoe nailed to your computer case protects your code from bugs."

Many of you are perhaps astonished to know that we are a small company. For some reason many believe that we are a part of some large corporation or that we have a large staff and a marketing department. No, we don't. We just collect the most talented people and work in this small team to create something unique. And this is good for our users because they always get answers to their questions from those directly involved in product development and coding.

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

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 →