> ## 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

<Steps>
  <Step title="Release">
    We prepare a new release on our side.
  </Step>

  <Step title="Receive">
    The controller in your environment receives the update.
  </Step>

  <Step title="Apply">
    The controller applies the changes to the application.
  </Step>

  <Step title="Done">
    You don't need to do anything - updates are handled automatically.
  </Step>
</Steps>

## 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

<img src="https://mintcdn.com/tensor9/HaGjLSV3qkF08S3C/images/diagrams/update-process-dark.svg?fit=max&auto=format&n=HaGjLSV3qkF08S3C&q=85&s=24274c42f1058a958d64e833b23800df" className="block dark:hidden" alt="The update process: a release flows from our systems to your environment, and your environment confirms back to us" width="1600" height="1100" data-path="images/diagrams/update-process-dark.svg" />

<img src="https://mintcdn.com/tensor9/HaGjLSV3qkF08S3C/images/diagrams/update-process-light.svg?fit=max&auto=format&n=HaGjLSV3qkF08S3C&q=85&s=326a869fed78c5aae5737975f5efbcfc" className="hidden dark:block" alt="The update process: a release flows from our systems to your environment, and your environment confirms back to us" width="1600" height="1100" data-path="images/diagrams/update-process-light.svg" />

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.