With Polyspace R2026a, MathWorks introduces a release focused on making embedded software verification easier to adopt across modern development workflows. Whether you already use Polyspace® or are exploring it for the first time, R2026a brings static code analysis, dynamic testing, and developer workflows closer together.
A Unified Workflow for Static and Dynamic Verification
One of the most visible changes in R2026a is that the Polyspace Platform UI becomes the default user interface, providing a single environment to work with both static analysis and dynamic testing to enable common configuration, tool execution, and analysis review. The same UI is also presented in Polyspace Access™. This unified experience is designed to reduce context switching and help teams review, understand, and act on verification results more efficiently, especially as projects scale across teams and CI pipelines.
Polyspace Platform UI
New Products That Meet Developers Where They Work
R2026a introduces two new Polyspace products that encourage earlier verification:
Polyspace as You Code™ enables developers to identify coding standard violations and software defects directly from their IDE.
Polyspace Copilot™ complements Polyspace as You Code by helping users understand and address code analysis findings. It provides contextual explanations and suggested fixes based on the surrounding code and grounded by Polyspace documentation, directly within the Polyspace plugin in Visual Studio Code.
Together, these tools support a shift-left approach, bringing verification closer to everyday coding tasks.
Polyspace Copilot in Visual Studio Code
Stronger Compliance and Customization for Critical Software
For teams working in environments that require custom coding rules, R2026a strengthens Polyspace compliance capabilities. The Polyspace Query Language (PQL) allows teams to define custom rules and guidelines, enabling verification strategies that reflect internal standards or project-specific requirements.
Keeping Pace with Modern Testing Practices
For dynamic testing, new capabilities such as sanitizer-based profiling provide additional insight into runtime behavior. This feature checks for runtime robustness by executing the code under test to complement Polyspace Bug Finder™ and Polyspace Code Prover™ analysis.
Summary
Polyspace R2026a is not just about adding features, it’s about making software verification more approachable, more integrated, and more actionable. For existing users, it enhances productivity and workflow continuity. For new users, it offers multiple entry points—from lightweight IDE-based analysis to comprehensive static and dynamic verification—so teams can adopt Polyspace at their own pace and grow as their needs evolve.
