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

# Backends

> Choose the RemoteMux backend that matches your cloud ownership and team workflow.

Backends control which infrastructure and transport RemoteMux uses. The core model stays the same: one environment per project directory, `/workspace` as the remote root, `tmux`-backed workspaces, and named workspaces for parallel work.

## Compare The Backends

| Backend   | Who owns the cloud      | User auth                          | Attach transport        |
| --------- | ----------------------- | ---------------------------------- | ----------------------- |
| `aws`     | Your AWS account        | AWS credentials                    | AWS SSM Session Manager |
| `gcp`     | Your GCP project        | `gcloud` auth or a credential file | `gcloud compute ssh`    |
| `e2b`     | Your E2B account        | E2B API key                        | E2B PTY API             |
| `managed` | RemoteMux control plane | RemoteMux OAuth or service token   | E2B PTY API             |

## Which One To Pick

<Tabs>
  <Tab title="I want direct control of my AWS infrastructure">
    Choose **`aws`**. Provisioning, credentials, and runtime resources stay in your AWS account. RemoteMux orchestrates through the hosted control plane.
  </Tab>

  <Tab title="My org is already on GCP">
    Choose **`gcp`**. Keeps the workflow aligned with `gcloud`, Compute Engine, and GCP-native networking.
  </Tab>

  <Tab title="I want fast, sandboxed environments">
    Choose **`e2b`**. Lightweight E2B sandboxes with API-key auth. No cloud account needed.
  </Tab>

  <Tab title="I want the fewest moving parts for users">
    Choose **`managed`**. Users only need RemoteMux auth and a project directory. Operators own the cloud complexity.
  </Tab>
</Tabs>

## Backend Guides

<CardGroup cols={2}>
  <Card icon="https://mintcdn.com/autocomputer/yKfOiNAxoK1vYP3l/images/aws.png?fit=max&auto=format&n=yKfOiNAxoK1vYP3l&q=85&s=7d3d90dd74628fc121a225aa9ef3fd0c" title="AWS BYOC" href="/guides/aws" width="114" height="114" data-path="images/aws.png">
    Direct AWS ownership and AWS-native auth.
  </Card>

  <Card icon="https://mintcdn.com/autocomputer/yKfOiNAxoK1vYP3l/images/gcp.png?fit=max&auto=format&n=yKfOiNAxoK1vYP3l&q=85&s=b3126d7ece12f973e6ff96e694ebf25b" title="GCP BYOC" href="/guides/gcp" width="192" height="192" data-path="images/gcp.png">
    Direct GCP ownership with `gcloud`.
  </Card>

  <Card icon="https://mintcdn.com/autocomputer/yKfOiNAxoK1vYP3l/images/e2b.png?fit=max&auto=format&n=yKfOiNAxoK1vYP3l&q=85&s=610d567691b5ad0480b823a741a505bf" title="E2B" href="/guides/e2b" width="32" height="32" data-path="images/e2b.png">
    Sandbox-backed runtimes with API-key auth.
  </Card>

  <Card icon="server" title="Managed Cloud" href="/guides/managed">
    Operator-owned infrastructure and the simplest user setup.
  </Card>
</CardGroup>