Run the workers in your own AWS account.
Sandscale workers can run in your own AWS account, through a role you create with an external ID. No long-lived keys, and your data stays in your account.
Your own cloud
Sandscale workers can run in your own AWS account, through a role you create with an external ID. No long-lived keys, and your data stays in your account.
StepWhat happens
Create the roleA guided CloudFormation setup, with an external ID from Sandscale
ConnectSandscale assumes the role; no long-lived keys
RunWorkers start in your account and talk to Sandscale over mTLS
PlaceYour organisation’s sandboxes run on your workers
- Clouds
- AWS. Azure and Google Cloud coming soon
- Credentials
- A cross-account role; no long-lived keys
- Connection
- mTLS with short-lived worker certificates
- Isolation and audit
- The same as hosted sandboxes
How it works
What happens, in order.
01Set up
Create a role in your AWS account with the guided setup.
02Connect
Sandscale assumes it with an external ID and launches workers.
03Run
Your sandboxes run in your account, with the same isolation and audit.
Which plans
Your own cloud comes with Enterprise. Azure and Google Cloud are coming soon.
See pricing →Give every agent
a box of its own
Start free with 100 vCPU-hours a month. Upgrade when your agents need more.
A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI