--- title: RemoteHost: sandboxes for coding agents description: Persistent, hardware-isolated microVMs for Claude Code, Codex, or any coding agent. Runtime usage displayed in compute-hours, run from one control plane, for your team or your users. url: https://remotehost.ai/ --- # RemoteHost Compute infrastructure to run coding agents beyond the laptop. Give every developer a persistent, isolated computer, provision ephemeral sandboxes on demand, and control every environment through one API. 4 vCPU · 8 GB · hardware-isolated · from $0.033/hr ## Install the CLI macOS and Linux: ```sh curl -fsSL https://remotehost.ai/install | sh ``` Windows (PowerShell): ```powershell irm https://remotehost.ai/install.ps1 | iex ``` ## Why remotehost - **Persistent.** A sandbox lasts until you delete it. Sleep one and the whole machine is snapshotted, memory included; wake it days later and the agent picks up mid-thought. Nothing here times out and takes the work with it. - **Lowest published price.** From $0.033/hr for a 4 vCPU / 8 GB machine, with runtime usage displayed in compute-hours. That is below every comparable agent-sandbox price sheet we checked on 2026-09-11; the table is in the Pricing section below. - **Secure.** Every sandbox is its own hardware-isolated microVM, not a container sharing a kernel with strangers. That is the strongest isolation on offer anywhere, and here it is the default, not the upgrade. ## Where it runs Every sandbox we run is in `us-east4`, US East (N. Virginia). So is the control plane that drives it, and the US-resident storage its snapshots and templates live in. That leaves one region and one jurisdiction to name when a compliance review asks for them. The standard sandbox is 4 vCPU, 8 GB of memory and 80 GB of disk, on its own hardware-isolated Firecracker microVM. Enterprise can run sandboxes on its own hardware instead, in its own datacenter or VPC: the Firecracker hosts are yours and your source code never leaves your network, while identity, roles, audit, and billing keep running in RemoteHost. If your data has to live somewhere else, tell us: https://remotehost.ai/contact. ## What a sandbox is - **Ready when you attach.** A microVM typically boots in under a second. The harness is up, your repo is cloned, and a tmux session is waiting: work in progress, never an empty box. - **Root.** Full systemd, Docker, background processes, real ports, its own filesystem. Anything that needs a machine rather than a request handler runs here unchanged. - **Stocked.** Docker, the GitHub and Linear CLIs, language servers, and the runtimes a repo expects ship in the image. The agent's first move is the work, not twenty minutes of apt. - **Nothing is thrown away.** Ephemeral sandboxes take the work with them when they go. These stop and resume from their own snapshot: same filesystem, same branch, same half-finished dev server. - **Any client, one fleet.** The CLI, the TUI, the desktop app, and the web console all attach to the same live sandbox and read the same fleet. The API drives any of it from your own code. - **Many people, one session.** A teammate attaches to the sandbox you are already in and lands in the same session: your panes, your scrollback, your running processes. No screen share, no second copy. ## Previews Remote development keeps the local development loop. Start `pnpm dev` and open localhost from the sandbox exactly as you would on your laptop. RemoteHost detects the port, opens the app in your browser, and keeps hot reload intact. No tunnel, port configuration, or new workflow. Sleep the sandbox with the server up and it is still serving when you wake it. [Start a sandbox](https://console.remotehost.ai?mode=signup) · [Preview documentation](https://docs.remotehost.ai/docs/platform#show-them-their-app) - **Same commands.** Start Next, Vite, Storybook, Rails, or another dev server the usual way. RemoteHost detects every bound port automatically. - **Same feedback loop.** Hot reload and its WebSocket travel through the preview connection, so the page updates as the agent saves. - **Easier to share.** Every preview has an authenticated HTTPS URL for your team. Public links have their own expiry and can be revoked without disrupting the sandbox. Agents can mint one themselves through the MCP server's `create_preview_url`. ## Who it is for - **For your team.** Each engineer gets as many sandboxes as they have work in flight, on one org, one bill, and one fleet you can see all of. They last between sessions, so an agent picks up where it stopped rather than where it started. - **For your product.** Provision a sandbox per user, per session, or per task straight from the API. Each one is its own hardware-isolated microVM, so code you did not write and cannot vet never shares a kernel with the next customer's. Ephemeral for a task, persistent for a workspace. ## Command line `remote new` is the base primitive. Add an agent name and Claude Code or Codex boots inside the sandbox as it provisions, so it's ready the moment you `remote attach`. | Command | What it does | | --- | --- | | `remote new` | Create a fresh sandbox | | `remote new claude` | Create a sandbox with Claude Code booting inside it | | `remote new codex` | Create a sandbox with Codex booting inside it | | `remote ls` | Show active sandboxes | | `remote attach` | Attach to a sandbox by name | | `remote stop` | Stop a sandbox and stop usage billing | Operating model: - Usage starts when the sandbox is running - Stopped sandboxes do not accrue runtime charges - Business orgs have shared billing and team controls - Audit logs track sandbox lifecycle events ## Pricing Starter lets a single engineer prove the workflow before rolling it out. Team turns RemoteHost into shared agent infrastructure with org controls and audit logs. Overage is off until you turn it on, and a machine-hour cap can be set on the org or on a single project below that. Full details: https://remotehost.ai/pricing.md ### What an hour costs One sandbox with 4 vCPU and 8 GB, running for an hour, at each provider's published rate as read on 2026-09-11. Compute only (CPU plus memory, by the clock); disk is left out because some providers include it and some meter it, and ours is included. Cloudflare and Vercel bill CPU only while it is busy, so their rows are the price at full load. A RemoteHost sandbox that is asleep is billed nothing. | Provider | Per hour | × ours | Published rate | | --- | --- | --- | --- | | **RemoteHost, Central EU** | $0.033/hr | — | Agent Standard profile in Germany, France, 80 GB disk included | | **RemoteHost, East US** | $0.033/hr | — | Agent Standard profile in North Virginia, 80 GB disk included | | **RemoteHost, Canada Central** | $0.033/hr | — | Agent Standard profile in Quebec, 80 GB disk included | | Box (EU only) | $0.036/hr | 1.1× | $20 buys 2,000,000 seconds of 4 vCPU / 8 GB, in Germany, Finland, or France; read at box.ascii.dev/ | | Northflank | $0.133/hr | 4.0× | $0.01667 per vCPU-hour + $0.00833 per GB-hour; read at northflank.com/pricing | | E2B | $0.331/hr | 10× | $0.000014 per vCPU-second + $0.0000045 per GiB-second; read at e2b.dev/pricing | | Blaxel | $0.331/hr | 10× | $0.0000115 per GB of RAM per second, CPU included; read at blaxel.ai/pricing | | Daytona | $0.331/hr | 10× | $0.0504 per vCPU-hour + $0.0162 per GiB-hour; read at www.daytona.io/pricing | | Cloudflare Sandboxes | $0.360/hr | 11× | $0.00002 per vCPU-second while busy + $0.0000025 per GiB-second; read at developers.cloudflare.com/containers/pricing/ | | Modal Sandboxes | $0.476/hr | 14× | $0.00003942 per core-second (a core is 2 vCPU) + $0.00000667 per GiB-second; read at modal.com/pricing | | Fly Sprites | $0.630/hr | 19× | $0.07 per CPU-hour + $0.04375 per GB-hour; read at fly.io/pricing/ | | Runloop | $0.634/hr | 19× | $0.108 per CPU-hour + $0.0252 per GB-hour; read at runloop.ai/pricing | | Vercel Sandbox | $0.682/hr | 21× | $0.128 per active-CPU-hour + $0.0212 per GB-hour; read at vercel.com/docs/sandbox/pricing | ## Links - Console (sign in / sign up): https://console.remotehost.ai - Docs: https://docs.remotehost.ai - Docs for agents: https://docs.remotehost.ai/llms.txt - Pricing: https://remotehost.ai/pricing - Extensions: https://remotehost.ai/extensions - Downloads: https://remotehost.ai/downloads - About: https://remotehost.ai/about - Contact: hello@remotehost.ai - Support: support@remotehost.ai - X / Twitter: https://x.com/remotehost_ai