{
  "manifest_version": "1",
  "slug": "opensandbox",
  "title": "OpenSandbox",
  "headline": "Self-host an OpenSandbox server",
  "description": "Run the OpenSandbox server with Docker on an exe.dev VM: sandboxes for AI agents behind exe.dev login, desktops in your browser, models without keys.",
  "category": "ai-agents",
  "tags": [
    "opensandbox",
    "opensandbox server",
    "opensandbox docker",
    "self-hosted sandbox",
    "ai agent sandbox",
    "code execution sandbox",
    "e2b alternative",
    "mcp sandbox",
    "novnc desktop",
    "docker sandboxes"
  ],
  "url": "https://exe.dev/deploy/opensandbox",
  "markdown_url": "https://exe-staging.dev/deploy/opensandbox.md",
  "upstream": {
    "website": "https://open-sandbox.ai",
    "source": "https://github.com/opensandbox-group/OpenSandbox",
    "docs": "https://open-sandbox.ai/getting-started/",
    "license": "Apache-2.0"
  },
  "example_vm_name": "my-opensandbox",
  "time": "5 minutes",
  "stack": [
    {
      "name": "OpenSandbox server 1.2.1",
      "detail": "the lifecycle API, a systemd service from PyPI, with an API key",
      "port": 8080,
      "data": "~/.opensandbox/opensandbox.db"
    },
    {
      "name": "Sandboxes",
      "detail": "Docker containers with OpenSandbox's execd inside, each on a host port from 4000-4999"
    },
    {
      "name": "Egress sidecar",
      "detail": "opensandbox/egress, added to sandboxes created with a network policy"
    },
    {
      "name": "SDK, CLI and MCP server",
      "detail": "opensandbox, osb and opensandbox-mcp, for scripts and agents on the VM",
      "data": "~/opensandbox"
    }
  ],
  "access": [
    {
      "url": "https://my-opensandbox.exe.xyz:8080/",
      "who": "private",
      "what": "the OpenSandbox API, for you and for SDK clients with a VM token and the API key"
    },
    {
      "url": "https://my-opensandbox.exe.xyz:4000/",
      "who": "private",
      "what": "each sandbox's execd and its ports (4000-4999), with the same exe.dev login or token"
    },
    {
      "url": "ssh my-opensandbox.exe.xyz",
      "who": "private",
      "what": "the VM itself, where agents use the server through MCP"
    }
  ],
  "delivers": [
    "The OpenSandbox server 1.2.1 with the Docker runtime, an API key, and a service that starts at boot",
    "The API and every sandbox endpoint behind exe.dev login, reachable from scripts anywhere with a VM token",
    "A first Python sandbox created, run, and deleted, in about a second once the image is pulled",
    "A `desktop.py` script that opens an XFCE desktop in a sandbox in your browser tab, through noVNC",
    "Sandboxes kept away from the API, from each other, and from the VM's exe.dev integrations",
    "Claude Code and Codex on the VM using the server through OpenSandbox's MCP server"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe-staging.dev/new?prompt=Set%20up%20OpenSandbox%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Fopensandbox.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-opensandbox.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-opensandbox.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20The%20OpenSandbox%20server%201.2.1%20with%20the%20Docker%20runtime%2C%20an%20API%20key%2C%20and%20a%20service%20that%20starts%20at%20boot%0A-%20The%20API%20and%20every%20sandbox%20endpoint%20behind%20exe.dev%20login%2C%20reachable%20from%20scripts%20anywhere%20with%20a%20VM%20token%0A-%20A%20first%20Python%20sandbox%20created%2C%20run%2C%20and%20deleted%2C%20in%20about%20a%20second%20once%20the%20image%20is%20pulled%0A-%20A%20%60desktop.py%60%20script%20that%20opens%20an%20XFCE%20desktop%20in%20a%20sandbox%20in%20your%20browser%20tab%2C%20through%20noVNC%0A-%20Sandboxes%20kept%20away%20from%20the%20API%2C%20from%20each%20other%2C%20and%20from%20the%20VM%27s%20exe.dev%20integrations%0A-%20Claude%20Code%20and%20Codex%20on%20the%20VM%20using%20the%20server%20through%20OpenSandbox%27s%20MCP%20server%0A%0ARun%20%22Set%20up%20by%20hand%22%20from%20%22On%20the%20VM%22%20%28skip%20creating%20the%20VM%29%2C%20then%0Adownload%20hello.py%20and%20run%20it%20as%20in%20%22Run%20your%20first%20sandbox%22%2C%20and%20check%0Afor%20its%20%22hello%20from%20Python%22%20line.%20Download%20desktop.py%20next%20to%20it%2C%20but%0Adon%27t%20run%20it%3A%20it%20starts%20a%20desktop%20for%2030%20minutes.%20Run%20the%20%60exeuntu%0Aconfigure%60%2C%20%60claude%20mcp%20add%60%20and%20%60codex%20mcp%20add%60%20commands%20from%20%22Let%20an%0Aagent%20use%20it%22%20and%20check%20that%20%60claude%20mcp%20list%60%20says%20Connected%3B%20skip%0Athe%20example%20prompts.%20Don%27t%20print%20the%20API%20key%20in%20your%20final%0Amessage%3A%20say%20it%20is%20in%20~%2Fopensandbox%2Fenv.%20Leave%20INTEGRATIONS%20in%0Afirewall.sh%20at%20block%20unless%20the%20owner%20asks%20otherwise.%20Never%20make%20the%20VM%0Apublic%20or%20point%20port%208000%20at%20the%20API.%20Finish%20with%20the%20API%27s%20URL%2C%20using%0Athis%20VM%27s%20name%2C%20and%20the%20commands%20from%20%22Use%20it%20from%20your%20computer%22.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe-staging.dev/deploy/opensandbox/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up OpenSandbox on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/opensandbox.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-opensandbox. This VM's name is the output of `hostname`: use it wherever the recipe writes my-opensandbox. Skip the step that creates the VM; you are on it.\n\nYou are done when all of these are true. Check each one yourself:\n- The OpenSandbox server 1.2.1 with the Docker runtime, an API key, and a service that starts at boot\n- The API and every sandbox endpoint behind exe.dev login, reachable from scripts anywhere with a VM token\n- A first Python sandbox created, run, and deleted, in about a second once the image is pulled\n- A `desktop.py` script that opens an XFCE desktop in a sandbox in your browser tab, through noVNC\n- Sandboxes kept away from the API, from each other, and from the VM's exe.dev integrations\n- Claude Code and Codex on the VM using the server through OpenSandbox's MCP server\n\nRun \"Set up by hand\" from \"On the VM\" (skip creating the VM), then\ndownload hello.py and run it as in \"Run your first sandbox\", and check\nfor its \"hello from Python\" line. Download desktop.py next to it, but\ndon't run it: it starts a desktop for 30 minutes. Run the `exeuntu\nconfigure`, `claude mcp add` and `codex mcp add` commands from \"Let an\nagent use it\" and check that `claude mcp list` says Connected; skip\nthe example prompts. Don't print the API key in your final\nmessage: say it is in ~/opensandbox/env. Leave INTEGRATIONS in\nfirewall.sh at block unless the owner asks otherwise. Never make the VM\npublic or point port 8000 at the API. Finish with the API's URL, using\nthis VM's name, and the commands from \"Use it from your computer\".\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe-staging.dev/deploy/opensandbox/prompt.txt"
  },
  "updated": "2026-11-19",
  "verified": "2026-11-19",
  "related": [
    "sandbox",
    "python-sandboxes",
    "code-interpreter",
    "linux-desktop",
    "computer-use",
    "docker-host"
  ],
  "alternatives": [
    "E2B",
    "Daytona"
  ],
  "files": [
    "https://exe-staging.dev/deploy/opensandbox/desktop.py",
    "https://exe-staging.dev/deploy/opensandbox/hello.py",
    "https://exe-staging.dev/deploy/opensandbox/setup.sh"
  ]
}
