PVS
pvs.csl.sri.com
- Free plan
- Windows
- macOS
- Linux
What PVS is
PVS is a mechanized environment for writing formal specifications and checking whether they meet their requirements. Its language is based on typed higher-order logic and supports predicate subtypes, dependent types, and parameterized theories. The environment combines predefined theories, a type checker, an interactive theorem prover, a symbolic model checker, libraries, utilities, documentation, and examples. Proof tools cover induction, rewriting, simplification, abstraction, decision procedures, and symbolic model checking, with command-line tools for batch re-proving theories and libraries. PVS also integrates the Yices SMT solver, supports evaluation of ground expressions through PVSio, and can run random testing during proofs. PVSio includes input/output, floating-point arithmetic, exception handling, and parsing. Typical applications include mathematical formalization, hardware and algorithm verification, and use as a backend for computer algebra and code verification systems. The integrated interface uses GNU or X Emacs, with Tcl/Tk for proof trees and theory hierarchies. Noncommercial use is free; the Allegro runtime has a separate click-through license, and commercial entities need a current PVS license or must contact SRI about licensing.
Who it suits
PVS suits people formalizing mathematics or verifying hardware and algorithms, as well as teams using verification backends. Users should be comfortable with its formal specification and theorem-proving approach.
Good to know, and what to watch
- Supports typed higher-order logic specifications.
- Includes an interactive theorem prover and model checker.
- Command-line tools support batch re-proving.
- Integrates Yices and random testing during proofs.
- Free for noncommercial use.
- Commercial use requires a current license or licensing contact.
- Allegro runtime has a separate click-through license.
- VSCode interface is described as experimental.
- Builds from GitHub sources can depend on platform environment.
Plans
Every plan and pricePVS (commercial)
PVS (noncommercial)
Free plan
Getting started
- Visit the PVS website and review the system, language, and prover guides.
- Choose the noncommercial plan if that applies, and accept the Allegro runtime click-through license when required.
- Install PVS for Linux, macOS, or Windows as a self-hosted environment.
- Use GNU or X Emacs as the integrated interface.
- Explore the linked NASA PVS Library or VSCode plugin; the VSCode interface is experimental.
Limits to check
The noncommercial plan is free, but the Allegro runtime requires acceptance of a separate click-through license. Commercial entities need a current PVS license or must contact SRI for licensing.
The Club's review
PVS is a self-hosted environment for specifying systems and checking their properties with formal methods. It is best suited to researchers and technical teams working on mathematical formalization or hardware and algorithm verification. Its combination of interactive proof, symbolic model checking, and batch workflows is substantial, but commercial users should resolve licensing before adopting it.
Overview
PVS brings a specification language, type checker, predefined theories, libraries, examples, and verification tools into one environment. Its language is based on typed higher-order logic, with predicate subtypes, dependent types, and parameterized theories for expressing detailed properties. That breadth serves demanding formal work; it is not a general-purpose development environment for teams seeking a lightweight way to check ordinary application code.
Typical applications include mathematical formalization, hardware and algorithm verification, and use as a backend for computer algebra and code verification systems. PVS supports theorem proving and symbolic model checking, with counterexamples and proof artifacts as part of its verification capabilities.
Key features
The interactive prover offers procedures for induction, rewriting, simplification, and decision procedures, as well as symbolic model checking. This gives users several ways to approach proof obligations, while still requiring familiarity with formal specification and proof work. Proof scripts and command-line tools can re-prove theories and libraries in batch mode, a practical fit for repeatable verification runs alongside interactive sessions.
Evaluation and testing broaden the workflow: PVS supports the Yices SMT solver, evaluation of ground expressions, and random testing during proofs. PVSio adds evaluation and animation capabilities, including input/output, floating-point arithmetic, exception handling, and parsing. Together these features let users examine behavior as well as construct proofs, though they remain part of a specialized formal-methods environment.
GNU or X Emacs serves as the integrated interface, and Tcl/Tk can display proof trees and theory hierarchies. Users comfortable with that toolchain may value the dedicated proof views; teams expecting a conventional standalone IDE may find the interface a meaningful adjustment. The downloads page links a VSCode plugin, but its interface is described as experimental.
Pricing
PVS (noncommercial): free. This plan is for noncommercial use and requires accepting a separate click-through license for the Allegro runtime. The free price makes it accessible for eligible noncommercial projects, but it does not remove the runtime agreement.
PVS (commercial): custom pricing. Commercial entities need a current PVS license or should contact SRI for licensing before downloading the Allegro runtime. Businesses should settle those terms before building PVS into a workflow; the noncommercial plan is not a substitute for commercial authorization.
Platforms
PVS supports Linux, macOS, and Windows and is self-hosted. Building from GitHub sources can be sensitive to the platform environment, so teams planning a source build should account for platform-specific setup. The site provides system, language, and prover guides, tutorials, examples, and release notes, although the manuals may not cover newer features.
Who it's for
PVS is a strong candidate for researchers, formal-methods practitioners, and engineering teams verifying mathematical specifications, hardware, or algorithms. Its combination of expressive logic, proof automation, model checking, evaluation, and batch re-proving serves projects that need rigorous, repeatable reasoning. It is a less natural choice for teams seeking a conventional IDE experience or businesses unwilling to work through separate runtime licensing.
Pros and cons
- Pro: The typed higher-order logic language supports predicate subtypes, dependent types, and parameterized theories, giving formal-methods users room to express sophisticated specifications.
- Pro: Interactive proof, symbolic model checking, batch re-proving, evaluation, and random testing support several complementary verification workflows.
- Pro: Libraries, examples, guides, tutorials, and community support channels provide resources for learning and ongoing work.
- Con: The GNU or X Emacs-centered interface may not suit teams that expect a conventional IDE; the linked VSCode interface is experimental.
- Con: Commercial use requires a current license or contact with SRI, and the Allegro runtime has a separate click-through license.
- Con: Source builds can depend on platform environment, adding setup uncertainty for teams compiling from GitHub.
Alternatives
Formal Verification Tools is the broader category directory for readers comparing approaches beyond PVS.
Choose Rocq if you want a free interactive theorem prover that also supports dependently typed programming. UPPAAL is worth considering when its freemium model and eligible academic license fit your use. Alloy Analyzer offers a free, self-contained executable for readers who prefer that packaging. Z3 is a free, MIT-licensed option to consider when solver use is the priority. CBMC is a free, BSD-licensed alternative; Isabelle is another free theorem-proving option with open-source licensing. SPIN provides free source and executables under a BSD 3-Clause license. ACL2 is another free alternative.
Verdict
Choose PVS if your work needs an expressive formal specification language, interactive and batch proof, and complementary evaluation and model-checking tools in a self-hosted environment. Its breadth is the main reason to adopt it; its Emacs-centered workflow and separate commercial runtime licensing are the strongest reasons to look elsewhere.
The verdict
PVS offers a broad formal specification and verification toolkit for technical users, including interactive and batch proof workflows. Check the licensing terms, runtime agreement, and platform-sensitive build guidance before proceeding.
Questions people ask
Is PVS free?
The noncommercial plan costs nothing. The Allegro runtime has a separate click-through license.
Can commercial entities use PVS?
Commercial entities need a current PVS license or should contact SRI about licensing before downloading the Allegro runtime.
Which platforms does PVS support?
PVS is available for Linux, macOS, and Windows, and is self-hosted.
Is PVS open source?
PVS sources are under GPL. The Allegro runtime has a separate click-through license.
Does PVS have a VSCode integration?
The downloads page links to a VSCode PVS plugin, and the documentation describes its interface as experimental.
What can PVS be used for?
Listed applications include mathematical formalization, hardware and algorithm verification, and use as a backend for computer algebra and code verification systems.
What the maker publishes
- Additional capabilities
- PVS supports the Yices SMT solver, PVSio evaluation of ground expressions, and random testing during proofs. source
- Batch proving
- PVS includes proof scripts and command-line tools to re-prove theories and libraries in batch mode. source
- Build limitation
- The download page says building from GitHub sources can be sensitive to the platform environment. source
- Commercial licensing limit
- Commercial entities need an existing current PVS license or should contact the licensing address before downloading the Allegro runtime. source
- Core components
- PVS includes a specification language, predefined theories, a type checker, an interactive theorem prover, a symbolic model checker, utilities, documentation, libraries, and examples. source
- Documentation
- The site provides system, language, and prover guides, tutorials, examples, and release notes, while noting that manuals may not cover newer features. source
- Evaluation and testing
- PVS includes a ground evaluator, random testing capability, and integration with the Yices SMT solver. source
- Founded
- 1946 source
- Headquarters
- Menlo Park, California, USA source
- Integration
- The downloads page links a VSCode PVS plugin and the NASA PVS library; the documentation describes the VSCode interface as experimental. source
- Integrations and libraries
- The downloads page links to a NASA PVS Library and a VSCode PVS Plugin. source
- License and commercial use
- PVS sources are under GPL; commercial entities without a current PVS license are directed to contact PVS licensing. source
- Licensing
- PVS sources are under GPL, and the Allegro runtime has a separate click-through license; noncommercial entities may freely download it subject to that agreement. source
- Platforms
- The download page lists current 64-bit versions for Linux and MacOSX and says Windows may run PVS 7.1 or later through Vagrant and VirtualBox. source
- Platforms
- Current listed releases target 64-bit Linux and macOS; the site says Windows can run PVS 7.1 or later through Vagrant and VirtualBox. source
- Proof automation
- The prover includes inference procedures for induction, rewriting, simplification using decision procedures, abstraction, and symbolic model checking. source
- Proof capabilities
- The interactive prover includes inference procedures for induction, rewriting, simplification, decision procedures, and symbolic model checking. source
- Purpose
- PVS is a mechanized environment for formal specification and verification. source
- Purpose
- PVS is a verification system combining a specification language, support tools, and a theorem prover. source
- PVSio
- PVSio supports evaluation and animation with features including input/output, floating-point arithmetic, exception handling, and parsing. source
- Security contact
- The PVS developers' contact address is listed for licensing questions, security concerns, feature requests, and suggestions. source
- Specification language
- Its language is based on typed higher-order logic and supports predicate subtypes, dependent types, and parameterized theories. source
- Support
- Users can report bugs by email or GitHub and ask questions through a Google Group or moderated help mailing list. source
- Support
- Support is offered through developer and bug-report email addresses, GitHub issues, Google Groups, and moderated mailing lists. source
Checked against the maker's pages on 30 Sept 2026.