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

# Deployment Modes

> Choose local development mode or full mode.

Cloud Adapter has two deployment modes. **Full mode** can serve development or production environments. **Local development mode** runs against your own cloud resources; it is separate from the in-memory emulator.

| Mode | Runtime | What you operate |
| - | - | - |
| [Local development mode](https://docs.tensor9.com/cloud-adapter-early-access/deployment/single-binary.md) | The Tensor9 CLI launches one serving container image by digest in Docker. This launcher is pending. | Your local Docker runtime, endpoint and target-cloud resources. |
| [Full mode](https://docs.tensor9.com/cloud-adapter-early-access/deployment/provisioned.md) | `tensor9 adapt cloud install` creates the target-cloud fabric that hosts the serving image. | The installed fabric, target-cloud resources and their lifecycle. |

> [!NOTE]
>
> The container launcher for local development mode is planned. The current local quickstarts use the existing foreground `tensor9 adapt svc run` command. They do not demonstrate the new container workflow. Tensor9 owns the launcher delivery and will update the quickstarts when that release is available.

Both modes use the same service implementations. A deployment mode does not expand a mapping's supported API operations. The local emulator uses in-memory backends instead of your cloud services.

Acquisition, setup and license renewal require [Tensor9 CLI authentication with `T9_API_KEY`](https://docs.tensor9.com/cloud-adapter-early-access/getting-started/install-and-authenticate). Local development mode retains the license requirement.

## Identity and networking

The application must reach the adapter, and the adapter must reach its target services. Give each connection its own network and authentication design. Private placement alone does not authenticate a caller.

The planned local launcher exchanges cloud credentials for short-lived credentials and hands them to the container as files. It does not mount your cloud credential home directories. Keep provisioning credentials separate from serving credentials and use the least privilege needed for each operation.

## State and availability

Inventory application data and adapter state separately. Give each an owner, backup policy and recovery procedure. Stopping a local container does not delete or back up your target-cloud data.

For production in full mode, verify the selected service mapping, network controls, backups and failure recovery. A successful local quickstart does not establish production availability or scaling.


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