Skip to main content
Backends change the infrastructure and transport RMUX uses under the hood. They do not change the main RMUX model.

​
What Never Changes

Across every backend, RMUX still gives you:
  • one environment per project directory
  • /workspace as the main remote project root
  • tmux-backed workspaces
  • named workspaces for parallel work

​
What Actually Changes

BackendWho owns itUser authAttachSync
awsYour AWS accountAWS credentialsAWS SSM Session Managerrsync over an SSM-backed SSH tunnel
gcpYour GCP projectgcloud authgcloud compute sshrsync over gcloud compute ssh
e2bYour E2B accountE2B API keyE2B PTY APIDirect archive upload
managedRMUX control planeRMUX_API_KEYAWS SSM through the control planeDeployment-managed archive staging

​
Two Different Docs For Two Different Jobs

  • Use Supported Clouds when you want the canonical list of cloud backends RMUX supports.
  • Use the backend guides when you already know the backend and need setup details.
https://mintcdn.com/autocomputer/yKfOiNAxoK1vYP3l/images/aws.png?fit=max&auto=format&n=yKfOiNAxoK1vYP3l&q=85&s=7d3d90dd74628fc121a225aa9ef3fd0c

AWS BYOC

Direct AWS ownership and AWS-native auth.
https://mintcdn.com/autocomputer/yKfOiNAxoK1vYP3l/images/gcp.png?fit=max&auto=format&n=yKfOiNAxoK1vYP3l&q=85&s=b3126d7ece12f973e6ff96e694ebf25b

GCP BYOC

Direct GCP ownership with gcloud.
https://mintcdn.com/autocomputer/yKfOiNAxoK1vYP3l/images/e2b.png?fit=max&auto=format&n=yKfOiNAxoK1vYP3l&q=85&s=610d567691b5ad0480b823a741a505bf

E2B

Sandbox-backed runtimes with API-key auth.

Managed Cloud

Operator-owned infrastructure and the simplest user setup.

Projects

See how RMUX uses the current directory, rmux.conf, and .rmux/state.json.

Supported Clouds

Use the backend support overview when you want the complete supported list.
Last modified on March 21, 2026