Customer support
Lifetime Release Policy
OpenRules puts you in control of your upgrade strategy, making it easier to plan and budget for product upgrades while relying on stable, thoroughly tested releases.
Built for continuity
Product stability without standing still.
Our Long-Term-Support releases are designed to be stable and reliable. They undergo extensive testing and are regularly updated with bug fixes so they remain optimized for use over an extended period of time.
This stability is crucial for larger businesses and organizations that rely on OpenRules for critical day-to-day operations. When it is time to upgrade, licensed customers have rights to major product releases—combining product stability with OpenRules’ continuing advances in decision intelligence technology.
Long-term support
A predictable path for every customer.
OpenRules designates selected releases as Long-Term-Support (LTS) releases after their essential real-world use in production environments by OpenRules customers. The current LTS release is 10.4.*. OpenRules intends to make future LTS releases every two or three years.
Non-LTS releases usually introduce new capabilities and implementation enhancements to the most recent LTS release. OpenRules produces three to four non-LTS releases per year; see the release history.
Customers may choose not to upgrade to non-LTS releases and remain on the latest LTS release or another preferred release. Once a new LTS release becomes available, any previous non-LTS release is considered superseded. This policy provides continued support and peace of mind for your business.
Release validation
Security checks are part of every build.
OpenRules uses SonarQube for automated source-code analysis, integrated into the build pipeline with Maven’s Sonar plugin. Every codebase change is peer reviewed, and developers apply secure coding practices outlined in the OWASP Secure Coding Guide.
To verify that the software adheres to industry standards for Systems/Software Development Lifecycle security, every new release build uses a Maven plugin connected to the National Vulnerability Database, the official U.S. government repository. It validates third-party packages for known vulnerabilities and helps ensure that secured versions are used.
OpenRules reviews its applications for security vulnerabilities and does not build a new release without performing OWASP-based secure coding checks and NVD dependency validation.
Plan your deployment
Choose the release path that fits your business.
Talk with the OpenRules team about long-term support, upgrades, and the right subscription for your production decision services.