To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (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.

OOO "Program Verification Systems&…

OOO "Program Verification Systems" is renamed to PVS-Studio LLC

Aug 18 2020

Some people wonder why our site is named Viva64, the product is called PVS-Studio, and the company's name is OOO "Program Verification Systems". It's really weird, so it's time to set things right. Renaming the company will be the first step. For sure, many people are interested in the question why there is such a variety of names. Short explanation: due to historical reasons. This article is a more detailed story of how it happened.


It all started in 2006 with the idea of creating a small code analyzer to search for 64-bit errors in C and C++ code. At that time, the migration of x86-64 applications was just beginning (everyone called it AMD64 back then).The idea of a startup to create an auxiliary tool seemed genius. There was no immediate success, but the product gradually began to sell and developed.

The tool was named "Viva64". This symbolized something in the spirit of "Long live the 64-bit world!". Logical enough, the site was named "". So in those days, it all was fair enough.

As time passed, the static analyzer has been actively developing. Eventually it has comprised not only 64-bit diagnostics. In 2009, the product was renamed to PVS-Studio, derived from the company's English name "Program Verification Systems". And the Viva64 analyzer has become just a set of 64-bit rules in this new product.

By the way, everything is complicated with the company name. The company is registered in Russia and according to the current rules, its name in English was OOO "Program Verification Systems". This is loan translation from the name of the legal form among commercial organizations. The presence of this OOO is terrible.

This is awful because the abbreviation OOO coincides with the abbreviation "Out of Office", which has repeatedly led to misunderstandings in when communicating by email :).

That's how it turned out:

  • Product: PVS-Studio
  • Website:
  • Company: OOO "Program Verification Systems"

Therefore, the time has come to change the company's name in Russian, and specifically write in the corporate charter how it will be called in English. Basically, we had to put the names in order.

We started by renaming the company. Now it's all very simple. The company name now matches the product name: PVS-Studio LLC.

The next step is to move the site to domains and

So that's the story. Thank you for your attention. Some day I will tell you the story of how our logo became a unicorn and what transformations took place with its image.

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

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 →