---
title: "Upgrading SaaS Instances"
slug: "upgrading-saas-instances"
updated: 2026-02-20T18:44:36Z
published: 2026-02-20T22:00:01Z
canonical: "help.hyperscience.ai/upgrading-saas-instances"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Upgrading SaaS Instances

Hyperscience manages the upgrade process for SaaS instances. Your Hyperscience representative will let you know when a new major version of the application is available and work with you to coordinate the upgrade.

## Upgrade processes

To learn more about Hyperscience upgrades, in general, review our [How Upgrades Work in Hypercell](/deployment/docs/how-upgrades-work-in-hypercell#upgrade-process-overview). While the article describes the upgrade process for on-premise / private cloud instances of Hyperscience, it helps you understand the work Hyperscience will complete on your behalf and the types of model-training tasks you will be asked to assist with.

The SaaS upgrade process differs based on the Hyperscience version and the changes it includes. See [Hyperscience Release Process](/deployment/docs/hyperscience-release-process) for more information.

### Major version upgrades

When upgrading from one major version of the Hyperscience application to another (e.g., from v41.x.x to v42.x.x), Hyperscience works with you to complete the following steps:

1. Your Hyperscience representative lets you know that a new version is available and schedules the upgrade of your pre-production environments.
2. Hyperscience upgrades the pre-production environments.
3. Your Hyperscience representative works in partnership with you to train new models, update flows, and perform any necessary testing of the models in pre-production.
4. Your Hyperscience representative contacts you to schedule the upgrade of your production environment.
5. Hyperscience completes the upgrade in your production environment.

### Minor version upgrades

After releasing a major version, Hyperscience works on new features and improvements for that version and releases them in minor versions (e.g., v42.2.0 would be a minor version of v42).

When a new minor version becomes available, Hyperscience completes the following steps:

1. Your Hyperscience representative lets you know that a minor version is available, and they will tell you the maintenance window in which they will upgrade your pre-production and production environments.
2. Hyperscience upgrades your pre-production environments during a maintenance window.
3. Hyperscience upgrades your production environment during a maintenance window one week after upgrading the pre-production environments.

### Patch version upgrades

After releasing a minor version, Hyperscience works on fixes and security updates for that version and releases them in patch versions (e.g., v42.x.2 would be a patch version of v42).

When a new patch version becomes available, Hyperscience completes the following steps:

1. Hyperscience upgrades your pre-production environments during a maintenance window.
2. Hyperscience upgrades your production environment during a maintenance window one week after upgrading the pre-production environments.