Hyperscience provides platform releases (On-prem and SaaS), SaaS innovation releases, and patch versions. Each serves a different purpose and follows a release process designed to balance access to new capabilities with application stability and predictable maintenance. The available releases and patches depend on your deployment type. In this article, you’ll learn more about Hyperscience’s release model, including:
release types
cadence
support windows.
Release types
Release type | Availability | Release cadence | Customer value |
|---|---|---|---|
Platform release | On-prem and SaaS | Twice a year | Gives you a predictable schedule for planning upgrades and adopting improvements. |
SaaS innovation release | SaaS | Between platform releases | Gives you access to forward-compatible capabilities and improvements through the managed SaaS release process. |
Patch releases versions | On-prem and SaaS | Typically every two weeks or as needed for critical issues | Provides application and security fixes. |
Platform releases
Platform releases are available for on-prem and SaaS instances. Hyperscience provides two platform releases each year, giving you a predictable schedule for planning upgrades and adopting new capabilities and improvements.
Platform releases contain new capabilities and improvements. Before a platform release becomes available for on-prem instances, Hyperscience performs extra validation cycles on internal instances.
Upgrading an on-prem instance to another platform release may require you to review and update its flows or models. The required actions depend on the versions used in your instance and the compatibility supported by the target version.
For compatibility information, see Compatibility Across Application, Flow, and Model Versions.
SaaS innovation releases
SaaS innovation releases deliver forward-compatible capabilities and improvements between platform releases. They are available only for SaaS instances.
Hyperscience schedules and deploys SaaS innovation releases. You do not download or install these updates. This process gives you access to improvements without requiring a customer-managed application upgrade.
For major SaaS innovation releases (e.g., X.0.0) flows and models may require update. You are responsible for deploying updated flows and models to production instances before your scheduled Hyperscience application upgrade.
When an update requires customer action or affects service availability, we communicate the relevant information through the established release-notification process.
Patch versions
Patch versions provide targeted application and security fixes for on-prem and SaaS instances. For example, patching from v43.0.7 to v43.0.8 applies the updates included in v43.0.8 without moving the instance to another platform or SaaS innovation release.
Patch versions are compatible with the flows and models supported by their associated major release version. For example, v43.0.8 will be compatible with flows and models belonging to v43.x.y. Applying a patch does not require you to update any flows or models.
Patching process
Hyperscience deploys patches for all SaaS instances.
Customers apply patches to their on-prem testing and production instances with assistance from Hyperscience Support.
For patching guidance, see Patching Hyperscience.
Patch cadence
Hyperscience typically releases scheduled patches every two weeks. A fix must complete the applicable development, testing, security, and approval activities before we include it in a patch.
Hyperscience may release an on-demand patch for a critical issue. Other fixes normally follow the scheduled patch process.
Confirm patch availability with your Hyperscience representative before scheduling a production change.
Release notes
Hyperscience publishes release notes for every platform release, SaaS innovation release, and patch version.
Release notes may describe:
New capabilities and improvements
Application fixes and security improvements
Affected deployment types or configurations
Compatibility considerations
Review the relevant information for your instances in the Release Notes section.
Support window
Support differs between on-prem and SaaS instances.
Platform release support
Each on-prem platform release receives up to two years of support:
Support phase | Duration | Coverage |
|---|---|---|
Full support | 12 months, starting from the General Availability (GA) date | Application and security fixes. |
Extended support | An additional 12 months, starting after the end of full support | Critical security issues (Critical application issues at Hyperscience discretion). |
Limited | After extended support ends | No new fixes available. Hyperscience support team will troubleshoot and provide guidance. Upgrade to the latest application version for full support. |
When your platform release enters extended support, begin planning your move to the latest supported application version.
For the current support status of each platform release, see Supported Versions.
SaaS innovation release support
SaaS instances receive continuous, forward-compatible updates scheduled and deployed by Hyperscience. Individual SaaS innovation releases do not follow the same support window as on-prem platform releases.
Hyperscience schedules and deploys SaaS innovation releases, so you don’t need to schedule or perform application updates. Contact your Hyperscience representative for more information.
Plan your next upgrade
Before updating your instance:
Review Supported Versions to confirm the support status of your version.
Review Release Notes to understand the included changes, compatibility considerations, and required actions.
See Compatibility Across Application, Flow, and Model Versions when planning a platform-release upgrade.
See Patching Hyperscience when applying a patch to an on-prem instance.
Contact your Hyperscience Representative if you are unsure which update applies to your instance or need assistance planning your next change.