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

# Updates and Upgrades

After initial deployment, we ship updates to the application running in your environment. Here's how that works.

## How Updates Work

**1. Release**

We prepare a new release on our side.

**2. Receive**

The controller in your environment receives the update.

**3. Apply**

The controller applies the changes to the application.

**4. Done**

You don't need to do anything - updates are handled automatically.

## What Gets Updated

* **Application code** - New features, bug fixes, performance improvements
* **Application infrastructure** - If the update requires changes to supporting resources (a new database table, a modified IAM policy), the controller applies those via Terraform in your environment
* **Configuration** - Updated environment variables, resource limits, or other application settings

## What Doesn't Change Without Notice

* **Your infrastructure** - We don't modify your VPC, subnets, or security groups without telling you
* **Your permissions** - We don't change the controller's role or bindings silently
* **Your secrets** - We never touch secrets you created

## Your Control

You always have the option to:

* **Pause updates** - Freeze your deployment at a specific version for as long as needed
* **Review changes** - See exactly what's in an update before it's applied
* **Roll back** - If an update causes issues, the controller can revert to the previous version
* **Configure release windows** - Schedule when updates can be applied to your environment
* **Manage upgrades** - View available releases and control the upgrade process

You can manage all of these from the **Releases**, **Release Windows**, and **Manage Upgrades** sections of your Customer Portal.

## Infrastructure Changes

Occasionally, an update may require changes to supporting infrastructure (e.g., a new S3 bucket, an additional IAM policy). When this happens:

* We coordinate with you before making the change
* The controller applies the Terraform changes in your environment
* You can review the Terraform plan before it's applied

## The Update Process

![A vendor-driven application-rollout example: our systems prepare a release, your controller receives and applies the update, the application restarts with the new version, and deployment confirmation returns to our systems. Arrows show the logical sequence and reported status.](https://mintcdn.com/tensor9/fPouCk-zoygb1ljG/images/diagrams/managed-update-rollout-wide-dark.svg?fit=max\&auto=format\&n=fPouCk-zoygb1ljG\&q=85\&s=e5d482e9522982b7e1c6351c5bc2bb0c)

![A vendor-driven application-rollout example: our systems prepare a release, your controller receives and applies the update, the application restarts with the new version, and deployment confirmation returns to our systems. Arrows show the logical sequence and reported status.](https://mintcdn.com/tensor9/fPouCk-zoygb1ljG/images/diagrams/managed-update-rollout-wide-light.svg?fit=max\&auto=format\&n=fPouCk-zoygb1ljG\&q=85\&s=28d2dadffaa3da484ac27189b0c62ead)

![A vendor-driven application-rollout example: our systems prepare a release, your controller receives and applies the update, the application restarts with the new version, and deployment confirmation returns to our systems. Arrows show the logical sequence and reported status.](https://mintcdn.com/tensor9/fPouCk-zoygb1ljG/images/diagrams/managed-update-rollout-stacked-dark.svg?fit=max\&auto=format\&n=fPouCk-zoygb1ljG\&q=85\&s=fab4334ccba23ceb6ab6d22ae33eab2c)

![A vendor-driven application-rollout example: our systems prepare a release, your controller receives and applies the update, the application restarts with the new version, and deployment confirmation returns to our systems. Arrows show the logical sequence and reported status.](https://mintcdn.com/tensor9/fPouCk-zoygb1ljG/images/diagrams/managed-update-rollout-stacked-light.svg?fit=max\&auto=format\&n=fPouCk-zoygb1ljG\&q=85\&s=cdb8f65412303413bc46c3a464b5424d)

This example follows a vendor-driven application rollout, from preparing a release through controller deployment and reported confirmation. Solid arrows show work within your environment; dashed arrows show the release and its deployment status.

No credentials are exchanged during this process. The controller already has the permissions it needs (from the initial installation) to deploy and manage the application.

## Upgrade Frequency

Release cadence varies by application. Contact us for details about the update schedule for your specific deployment.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.