# Managed Sandboxes

> A managed sandbox is a VM the platform runs for you. It boots with belt, connects outbound as an ordinary remote, and shows under Resources → Remotes once it is online. Use it for harness sessions a...

**URL:** https://inference.sh/docs/extend/managed-sandboxes
**Last updated:** 2026-10-31

---

A **managed sandbox** is a VM the platform runs for you. It boots with belt, connects outbound as an ordinary [remote](/docs/extend/remote), and shows under **Resources** → **Remotes** once it is online. Use it for harness sessions and commands without your own machine.

Sandboxes are available in every workspace unless the workspace's `feature:sandboxes` entitlement is turned off; then create and start are refused and the Sandboxes pages say so.

→ [Sandboxes API](/docs/api/rest/sandboxes) · [Remotes](/docs/extend/remote)

---

## In the workspace

Open **Resources** → **Sandboxes** ([`/sandboxes`](https://app.inference.sh/sandboxes)). The list shows each sandbox's status, size, placement and remote; click a row to open it.

**create sandbox** takes a name, vCPUs, memory and disk, within the [API limits](/docs/api/rest/sandboxes#create-sandbox) (defaults 2 vCPU, 4 GB memory, 10 GB disk). The box starts right away and appears as a remote when its daemon connects.

The sandbox page shows the same fields as the API and links to its remote. Its owner can:

| Action | What it does |
|--------|--------------|
| **Start** | Boots on a fresh disk as the same remote. Files from the last run are gone. |
| **Stop** | Shuts the VM down and drops its disk. Agent sessions on its remote end. |
| **Delete** | Stops the box, then removes the sandbox and its remote. |

A sandbox is not a private [engine](/docs/private/why): engines run apps and agents from the task queue, and a sandbox is a VM that registers as a remote.