Agent Sandboxesagentsandboxes.org
Sandbox profile · Open-source project

Temps

Answer in brief

Self-hosted single-binary deployment platform (MIT or Apache-2.0) whose AI feature set includes Docker or Firecracker agent sandboxes with a browser terminal and preview URLs. Worth it only if you want the whole Temps platform; as a sandbox on its own it is thinly documented.

By the Agent Sandboxes editors · Updated

Overview

Temps is a self-hosted deployment platform shipped as a single Rust binary that bundles app deployments, analytics, error tracking, session replay, uptime monitoring, email, tracing, an AI gateway and AI agent sandboxes. It installs on a fresh Ubuntu server with one command and is dual-licensed MIT or Apache-2.0, with 906 GitHub stars at verification. Sandboxes are one feature among many: isolated environments driven from the CLI or REST API, with a live in-browser terminal and preview URLs; a Node sandbox SDK exists in the repository but is not yet on npm.

The default backend is a Docker container with capabilities dropped and no-new-privileges set, sharing the host kernel. On Linux hosts with /dev/kvm, temps firecracker setup enables a Firecracker backend that boots each sandbox as a microVM with its own guest kernel; the backend is chosen per sandbox and a Firecracker request fails rather than silently falling back, and macOS hosts cannot enable it. Workspaces suspend when idle and wake on the next command. Snapshots, resource limits, GPU and session limits are not documented, and the vendor's own comparison page calls E2B "the more mature product".

Notable

  • Dual-licensed MIT or Apache-2.0; 906 GitHub stars and 3,979 commits at verification; "55+ Rust crates".
  • Firecracker backend requires Linux x86_64 or aarch64 with /dev/kvm and a one-time setup; Docker backend works on macOS for local development.
  • Anonymous usage telemetry is on by default and can be disabled with TEMPS_TELEMETRY=0.

Temps specifications

AttributeDetails
IsolationDocker container by default (capabilities dropped, no-new-privileges, shared host kernel); optional Firecracker microVM backend with its own guest kernel on Linux hosts with /dev/kvm, chosen per sandbox
DeploymentOpen-source project · Self-hostable
Open sourceYes (MIT OR Apache-2.0)
SDKs and interfacesCLI, REST API
Cold start (vendor claim)Not documented
Max session lengthNot documented
PersistenceWorkspaces suspend when idle and wake on the next command; snapshots are not documented
GPUNot documented
NetworkingPassword-protected preview URLs and an in-browser command runner; the platform proxy (built on Pingora) provides automatic HTTPS
PricingFree to self-host, no usage billing; an optional Premium licence is sold separately (details on the pricing page)
Free tierFree to self-host
ComplianceNot documented
RegionsYour own server

Facts from Temps’s public documentation, verified November 9, 2026. Performance numbers are vendor claims.

Strengths and trade-offs

Strengths

  • You already run or want a self-hosted PaaS and would like sandboxes without another service.
  • You want to choose Docker or Firecracker isolation per sandbox on one host.
  • You need agent sandboxes with no per-second or per-sandbox charges.

Trade-offs

  • 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.

Good fit for: Teams already self-hosting a PaaS who want built-in agent sandboxes next to their deployments.

How Temps compares

SandboxIsolationOpen sourceSelf-host / BYOCCold start (vendor)Max sessionSnapshots / pauseGPUSDKs
TempsDocker or FirecrackerYesYes / NoNot documentedNot documentedNot documented / YesNot documentedCLI, REST API
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
PullrunFirecracker / Apple VM / runcYesYes / No~500 ms (claim)Not documentedYes / Not documentedNot documentedCLI, MCP server
CoderTemplate-defined (VM/pod/container)YesYes / NoNot documentedNot documentedNot documented / YesNot documentedCLI, REST API, 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

See all Temps alternatives →

Frequently asked questions

What is Temps?
Self-hosted single-binary deployment platform (MIT or Apache-2.0) whose AI feature set includes Docker or Firecracker agent sandboxes with a browser terminal and preview URLs. Worth it only if you want the whole Temps platform; as a sandbox on its own it is thinly documented.
How does Temps isolate code?
Temps documents its isolation as: Docker container by default (capabilities dropped, no-new-privileges, shared host kernel); optional Firecracker microVM backend with its own guest kernel on Linux hosts with /dev/kvm, chosen per sandbox.
Is Temps open source?
Yes (MIT OR Apache-2.0). It can be self-hosted.
How much does Temps cost?
Free to self-host, no usage billing; an optional Premium licence is sold separately (details on the pricing page) Check the official pricing page for current rates.
What are the alternatives to Temps?
Common alternatives include Docker Sandboxes, Microsandbox, Pullrun, Coder, OpenSandbox. See Temps alternatives for a full comparison.

Sources

  1. temps.sh
  2. temps.sh/agents
  3. github.com/gotempsh/temps

Cite this page

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

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