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

# Provisioned

> Let the local Tensor9 CLI install and operate the adapter in the target cloud.

<Frame>
  <img className="block dark:hidden" src="https://mintcdn.com/tensor9/3qwgIru3kCfHriJC/images/diagrams/cloud-adapter-provisioned-light.svg?fit=max&auto=format&n=3qwgIru3kCfHriJC&q=85&s=9341e0b25e0a2e0d5d7d10688ec12b4a" alt="The Tensor9 CLI provisions a Cloud Adapter and its supporting resources into a target environment." width="1200" height="600" data-path="images/diagrams/cloud-adapter-provisioned-light.svg" />

  <img className="hidden dark:block" src="https://mintcdn.com/tensor9/3qwgIru3kCfHriJC/images/diagrams/cloud-adapter-provisioned-dark.svg?fit=max&auto=format&n=3qwgIru3kCfHriJC&q=85&s=3c71bc07d5b20c7b857eeb4ea694efa4" alt="The Tensor9 CLI provisions a Cloud Adapter and its supporting resources into a target environment." width="1200" height="600" data-path="images/diagrams/cloud-adapter-provisioned-dark.svg" />
</Frame>

The **provisioned** deployment lets the local Tensor9 CLI create and operate the cloud resources that run your adapter. The adapter remains your application’s origin-cloud API surface; the CLI coordinates its placement, identity, networking and lifecycle in the target cloud.

## When to use it

Use a provisioned deployment when you want repeatable installation, cloud-native networking and an explicit infrastructure lifecycle without hand-assembling every runtime resource.

## Installation flow

1. Supply a [configuration file](/cloud-adapter/configuration/files), or answer the guided setup questions to generate one.
2. Review the proposed resources, identities and network paths.
3. Let the CLI provision the target-cloud resources and start the adapter.
4. Verify the endpoint with a small request before directing application traffic.

The generated configuration is the durable input to the deployment. Store it with the same review and change controls as infrastructure configuration.

## Updates and ownership

The local CLI coordinates compatible configuration updates, migrations and rolling restarts. It blocks changes that would require an unsupported live migration, such as changing a backend with no migration plan. You own the provisioned resources, credentials, data and cloud billing; Tensor9 supplies the adapter implementation and orchestration behavior.