> For the complete documentation index, see [llms.txt](https://docs.auterion.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.auterion.com/vehicle-operation/auterion-suite-fleet-management/fleet-management/fleet-deploy.md).

# Fleet Deploy

Fleet deploy provides a way for Suite users to install + update applications and firmware on multiple vehicles fleet-wide. After selecting an eligible software product along with an available release and one or more vehicles, users can queue a deployment- the specified product will then be installed on the included vehicles over the air.

### Requirements For a Deployment <a href="#requirements-for-a-deployment" id="requirements-for-a-deployment"></a>

* **OTA** installation must be enabled for vehicles intended to be used in a deployment - this is defined on a **vehicle model** basis and needs to be set by the manufacturer via the [Vehicle Models](https://suite.auterion.com/manufacturer/models) tab.

In order to construct a fleet deployment, the following must be true:

* The release for the target product to be deployed must be set as **available** by its manufacturer. The release *cannot* be vehicle-specific, (i.e. a release that applies to one or more *individual* vehicles).
* If the target product is **licensed**, a license must be assigned to all vehicles intended to be included in the deployment.

<figure><img src="https://3329189600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFW1Ge1p1f6WHyiYCb146%2Fuploads%2FWOYtK5oe1suD2zShXwGl%2FScreenshot%202025-09-15%20at%201.51.20%E2%80%AFPM.png?alt=media&amp;token=dee068aa-688d-43bc-a7c6-21b8e27872e7" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The requirements above are also summarized in the **Fleet Deploy** page info tooltip, pictured below.
{% endhint %}

<figure><img src="https://3329189600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFW1Ge1p1f6WHyiYCb146%2Fuploads%2FdOorHCXYWq5pW8kFQtjx%2FScreenshot%202025-09-18%20at%202.12.14%E2%80%AFPM.png?alt=media&amp;token=18582f6e-ad79-4ebd-b184-c4a8eba13484" alt=""><figcaption></figcaption></figure>

### How to Queue a Deployment <a href="#how-to-queue-a-deployment" id="how-to-queue-a-deployment"></a>

1. To queue a deployment, navigate to the [Fleet Deploy](https://suite.auterion.com/fleet-deploy) page under **Fleet Management**.
2. Select the **‘+ New Deployment’** button in the top right corner to navigate to the [deployment builder](https://suite.auterion.com/bulk-release-deployments/create).
3. Select the **product**, **release** and set of **vehicles** to be included in the deployment. If you do not see a product, release, or vehicle option you are expecting, check the requirements [above](https://www.notion.so/Fleet-wide-Operations-2159af1fb77f80a5ba16f3767b649705?pvs=21) to ensure the component is valid.
4. Click **Queue Deployment**. The specified product release will now be deployed to each of the selected vehicles the next time they come **online**.

<div align="left"><figure><img src="https://3329189600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFW1Ge1p1f6WHyiYCb146%2Fuploads%2F8Na0HR2xgpGnGAFxWIJF%2Ftrigger-deployment.gif?alt=media&amp;token=71692fde-ae45-4788-aa65-1b0dfd2f44ff" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note**: An individual vehicle release deployment will remain **pending** until the vehicle comes **online**.
{% endhint %}

## Viewing Deployment Statuses

You can view the status of queued fleet deployments via the **Active** and **Finished** tabs on the [Fleet Deploy](https://suite.auterion.com/fleet-deploy) page.

### Active Deployments

**Active** deployments are listed in the [Active](https://suite.auterion.com/bulk-release-deployments?tab=active) tab. Users can view the **product** deployed, **time** that the deployment was triggered, and completion progress within each entry. Additionally, hovering on the info ℹ️ icon will display a list of vehicles and their respective deployment statuses.

<div align="left"><figure><img src="https://3329189600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFW1Ge1p1f6WHyiYCb146%2Fuploads%2FCCCQpMj2mN33AjcAjDRb%2Fin-progress.gif?alt=media&amp;token=b44d1e82-51b5-4946-943c-d5e97ca4d427" alt=""><figcaption></figcaption></figure></div>

#### Finished Deployments <a href="#finished-deployments" id="finished-deployments"></a>

**Completed** deployments are listed in the [Finished](https://suite.auterion.com/bulk-release-deployments?tab=finished) tab. Users can view **product** deployed, **time** of deployment completion, and a summary of the resulting deployment (counts of `deployed`, `cancelled`, and `failed` vehicle deployments). Like the active deployment list, hovering on the info ℹ️ icon will display a list of vehicles and their respective deployment statuses.

<div align="left"><figure><img src="https://3329189600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFW1Ge1p1f6WHyiYCb146%2Fuploads%2FokvXTXYyPh0EFgcJhhWe%2Ffinished-deploy.gif?alt=media&amp;token=536d9aa1-0f26-42c3-bba9-e4f312be6565" alt=""><figcaption></figcaption></figure></div>

### Canceling Deployments

At this time, cancelation can only be done on a *vehicle by vehicle* basis- users must navigate to an individual vehicle’s **Software** tab, locate the target product, and click the **Cancel** button.

{% hint style="info" %}
**Tip**: Individual vehicle software pages are linked within the vehicle deployment status info popover within a deployment entry for easy navigation.
{% endhint %}

<div align="left"><figure><img src="https://3329189600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFW1Ge1p1f6WHyiYCb146%2Fuploads%2FgbMBJuq1Chz17Z3OVNLl%2Fcancel-deploy.gif?alt=media&amp;token=7b766692-06b1-4f6f-809d-d6a93cf84a34" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
The cancelation steps are also summarized in the **Fleet Deploy** page info tooltip, pictured below.
{% endhint %}