Agent Sandboxesagentsandboxes.org
Alternatives

Temps alternatives

Answer in brief

The 5 alternatives below are grouped by kind of sandbox, and each says what it does differently from Temps. Start from whatever made you look: missing GPUs, session limits, self-hosting, pricing or isolation.

By the Agent Sandboxes editors · Updated

Why teams look beyond Temps

Worth it only if you want the whole Temps platform; as a sandbox on its own it is thinly documented.

  • Sandboxes are a feature of a deployment platform, not a dedicated sandbox product; the vendor calls E2B more mature.
  • No SDK on npm yet; interaction is via CLI and REST API.
  • Snapshots, resource limits, session limits and GPU are not documented.
  • Default Docker backend shares the host kernel; Firecracker needs a KVM-capable Linux host.

Temps alternatives, by kind

Cloud development environments

Cloud and in-browser development environments that coding agents increasingly run in.

  • Coder

    Self-hosted cloud development environments defined in Terraform (VMs, Kubernetes pods or Docker containers) for developers and coding agents, with a control-plane-hosted agent loop so workspaces hold no model credentials.

    • Template-defined (VM/pod/container)
    • Open source
    • Self-hostable
    • Pause/resume

    How it differs: Organisations that want to run coding agents in self-hosted workspaces on their own clusters and clouds with audit and governance. The leading open-source, self-hosted workspace platform for agents and developers, with isolation as strong as the Terraform templates you write.

    Full profile →Coder alternativesWebsite ↗

Open-source runtimes to self-host

Open-source sandbox runtimes you run on your own servers or Kubernetes.

  • Microsandbox

    Open-source, local-first microVM runtime that gives each sandbox its own Linux kernel, with an optional managed cloud.

    • MicroVM (libkrun)
    • Open source
    • Self-hostable
    • BYOC
    • Snapshots

    How it differs: Self-hosted microVM isolation on developer machines or your own servers. The most approachable way to get microVM-grade isolation locally or self-hosted.

    Full profile →Website ↗

  • OpenSandbox

    Apache-2.0 sandbox runtime for agents that starts on Docker, scales on Kubernetes and offers a Firecracker "Fast Sandbox" with pause/resume.

    • Containers or Firecracker
    • Open source
    • Self-hostable
    • Pause/resume

    How it differs: Teams that want an open, multi-language sandbox API they can run from a laptop Docker daemon up to a Kubernetes cluster. The most broadly supported open sandbox API of this batch, with real microVM isolation available once you are on Kubernetes.

    Full profile →OpenSandbox alternativesWebsite ↗

  • Pullrun

    Apache-2.0 sandbox runtime that runs the same OCI image as a runc container, a Firecracker microVM on Linux or an Apple Virtualization VM on macOS, with a CLI and MCP server.

    • Firecracker / Apple VM / runc
    • Open source
    • Self-hostable
    • Snapshots

    How it differs: Running agent workloads from OCI images as microVMs on your own Linux hosts or Apple Silicon Macs. A promising self-hosted OCI-to-microVM runtime for teams who want to own the sandbox layer, but not yet a hosted platform.

    Full profile →Pullrun alternativesWebsite ↗

Local sandboxes for coding agents

Isolation for agents like Claude Code, Codex or Gemini CLI on your own laptop.

  • Docker Sandboxes

    Docker’s `sbx` CLI for running AI coding agents in microVM sandboxes on your machine, with an experimental Docker-hosted cloud.

    • MicroVM
    • Self-hostable
    • GPU
    • Pause/resume

    How it differs: Running coding agents unsupervised on a laptop with microVM isolation. The easiest way to give local coding agents a real microVM boundary.

    Full profile →Website ↗

Temps vs alternatives

SandboxIsolationOpen sourceSelf-host / BYOCCold start (vendor)Max sessionSnapshots / pauseGPUSDKs
TempsDocker or FirecrackerYesYes / NoNot documentedNot documentedNot documented / YesNot documentedCLI, REST API
CoderTemplate-defined (VM/pod/container)YesYes / NoNot documentedNot documentedNot documented / YesNot documentedCLI, REST API, MCP server
Docker SandboxesMicroVMNoYes / NoNot documentedUntil removed (local)Yes / YesYessbx CLI, TypeScript (cloud), REST API (cloud)
MicrosandboxMicroVM (libkrun)YesYes / Yes<100 msNot documentedYes / Not documentedNoTypeScript, Python, Rust, Go, Ruby, CLI, MCP server
OpenSandboxContainers or FirecrackerYesYes / No64 ms P50 (claimed)Not documentedNot documented / YesNot documentedPython, JavaScript/TypeScript, Java, Kotlin, Go, C#, CLI, MCP server, REST API
PullrunFirecracker / Apple VM / runcYesYes / No~500 ms (claim)Not documentedYes / Not documentedNot documentedCLI, MCP server

Frequently asked questions

What are the main alternatives to Temps?
Coder, Docker Sandboxes, Microsandbox, OpenSandbox, Pullrun. Which one fits depends on what you need that Temps does not offer; each entry above explains how it differs.
Is there an open-source alternative to Temps?

Cite this page

Agent Sandboxes. (2026). Temps alternatives. agentsandboxes.org. Last reviewed November 9, 2026. https://agentsandboxes.org/alternatives/temps/

Found an error or a missing sandbox? Submit a correction — every entry links to the sources it relies on.