Agent Sandboxesagentsandboxes.org
Sandbox profile · Hosted platform

Isorun

Answer in brief

Hosted KVM microVM sandboxes booted from pinned OCI images, with fork of a running VM, hibernate/resume, host-side egress rules and credential injection. A KVM microVM sandbox service centred on forking, hibernation and host-side secret handling, with a TypeScript-first SDK.

By the Agent Sandboxes editors · Updated

Overview

Isorun is a hosted sandbox service in which each sandbox is a KVM microVM with its own guest kernel, booted from an OCI image from Docker Hub, GHCR or a private registry. Floating tags such as latest, lts and stable are rejected, so images must be pinned to a tag or digest. A sandbox defaults to 1 vCPU, 1 GiB RAM and a 4 GiB scratch disk, and is destroyed after 300 idle seconds unless the timer is changed. The homepage says sandboxes are "ready in 10ms"; the first boot of a new image on a runner takes 10 to 60 seconds while it is prepared. The docs do not name the hypervisor.

State features include fork, which clones a running sandbox's filesystem, memory and processes into N children, snapshot and restore within a region, hibernate/resume with processes kept at the same PIDs, and optional persistent disks on Tigris that can be snapshotted and forked. Security features run on the host: per-sandbox egress allow/deny rules and named profiles, a credential proxy that injects API keys so the guest sees only placeholders, and an HMAC-chained audit log. There is a TypeScript SDK (MIT, Node 20+), a REST API, an MCP server, adapters for OpenAI Agents and LangChain.js, and an adapter that runs Claude Managed Agents sessions in Isorun microVMs; a Python SDK is described as "in development". The homepage calls the service a public beta, while the changelog lists v1.0.0 as the public launch on 16 June 2026.

Notable

  • Fork clones a running sandbox, including memory and process state, into N children with a single call.
  • API keys for OpenAI, Anthropic, Google, GitHub and Hugging Face are injected by a host-side proxy; the guest's environment holds only placeholders.
  • Ships a self-hosted sandbox adapter for Claude Managed Agents that binds each Anthropic session to its own microVM.

Isorun specifications

AttributeDetails
IsolationKVM microVM per sandbox with its own guest kernel; the docs do not name the hypervisor. Egress policy and the credential proxy are enforced on the host, outside the guest
DeploymentHosted platform
Open sourceNo
SDKs and interfacesJavaScript/TypeScript, REST API, MCP server
Cold start (vendor claim)Homepage: VMs "ready in 10ms" (vendor claim); the API reference example shows create_ms of 9. The first time a runner sees an image it pulls and prepares it, which the docs say takes 10 to 60 seconds
Max session lengthNo maximum lifetime documented. Each sandbox has an idle auto-destroy timer, 300 seconds by default, set per create with timeoutSec or extended with setTimeout(); passing 0 disables it
PersistenceThe image is mounted read-only with a writable scratch layer (4 GiB by default) that lasts for the sandbox's lifetime, including across hibernate/resume. Hibernate keeps filesystem, memory and running processes. Snapshots persist until deleted and restore on any runner in the same region. Optional named persistent disks (ext4 on Tigris Cloud Disk with a local NVMe cache) mount at /workspace, outlive sandboxes and can be snapshotted and forked copy-on-write
GPUNot documented
NetworkingEgress is unrestricted by default; per-sandbox allow/deny rules (CIDRs, IPs, hostnames matched on SNI, wildcards) or named profiles (unrestricted, locked-down, claude-code, openai) are enforced at the host boundary. A host-side proxy injects API keys for OpenAI, Anthropic, Google, GitHub and Hugging Face so the guest only sees placeholders, with optional method and path rules. sandbox.url(port) proxies any port over HTTPS and WebSocket; the docs differ on whether these URLs require the API key
PricingPer-second billing with no minimums: $0.025 per vCPU-hour plus $0.015 per GiB-hour of RAM ($0.040 an hour for the default 1 vCPU + 1 GiB; 8 vCPU + 16 GiB is $0.440 an hour). Hibernated sandboxes are not billed for runtime. Persistent disks: $0.02 per GB-month of data stored. The homepage says egress traffic and platform fees are included
Free tier$50 of credit on sign-up, no card required (about 1,250 hours of a 1 vCPU + 1 GiB sandbox)
ComplianceSOC 2 Type II listed as "(soon)" on the homepage; each sandbox has an HMAC-chained, tamper-evident audit log
RegionsOrganizations are scoped to a US or EU region at sign-up; the API key routes to that region's runner
Company headquartersNot documented

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

Strengths and trade-offs

Strengths

  • You want each sandbox to be a microVM with its own kernel, booted from any pinned OCI image.
  • You need to fork a running sandbox with its memory intact to branch an agent's work.
  • You want third-party API keys kept outside the VM and egress restricted at the host.
  • You want per-second billing with no charge while a workspace is hibernated.

Trade-offs

  • Only a TypeScript SDK today; the Python SDK is described as in development.
  • The hypervisor, GPU support and a maximum session length are not documented.
  • Egress is unrestricted unless you set a policy or profile at create time.

Good fit for: Agents that need full Linux VMs from any pinned OCI image, with fork, hibernate and API keys kept out of the guest.

How Isorun compares

SandboxCompany HQIsolationOpen sourceSelf-host / BYOCCold start (vendor)Max sessionSnapshots / pauseGPUSDKs
IsorunNot documentedKVM microVMNoNot documented / Not documented10 ms (claim)300 s idle timeout (default)Yes / YesNot documentedJavaScript/TypeScript, REST API, MCP server
E2BUnited StatesFirecracker microVMYesYes / YesNot documented1 h / 24 h (Pro)Yes / YesNoPython, JavaScript/TypeScript
Morph CloudNot documentedVMNoNot documented / Not documented<250 ms (restore)ConfigurableYes / YesNot documentedPython, TypeScript
Fly.io SpritesUnited StatesMicroVMNoNot documented / Not documented0.1–2 s wakeUnlimitedYes / YesNoJavaScript/TypeScript, Go, Python, Elixir
ArchilUnited StatesFirecracker microVMNoNo / Yes37 ms exec (claim)24 h (then paused)Yes / YesNot documentedJavaScript/TypeScript, Python, CLI, REST API
DaytonaUnited StatesContainers or VMsNoNot documented / Yes<90 msUnlimitedYes / YesYesPython, TypeScript, Ruby, Go, Java
FreestyleUnited StatesVMNoNot documented / Not documented65 msUnlimited (paid)Yes / YesNot documentedTypeScript

Head-to-head: E2B vs Isorun

See all Isorun alternatives →

Frequently asked questions

What is Isorun?
Hosted KVM microVM sandboxes booted from pinned OCI images, with fork of a running VM, hibernate/resume, host-side egress rules and credential injection. A KVM microVM sandbox service centred on forking, hibernation and host-side secret handling, with a TypeScript-first SDK.
How does Isorun isolate code?
Isorun documents its isolation as: KVM microVM per sandbox with its own guest kernel; the docs do not name the hypervisor. Egress policy and the credential proxy are enforced on the host, outside the guest.
Is Isorun open source?
No, Isorun is not open source.
How much does Isorun cost?
Per-second billing with no minimums: $0.025 per vCPU-hour plus $0.015 per GiB-hour of RAM ($0.040 an hour for the default 1 vCPU + 1 GiB; 8 vCPU + 16 GiB is $0.440 an hour). Hibernated sandboxes are not billed for runtime. Persistent disks: $0.02 per GB-month of data stored. The homepage says egress traffic and platform fees are included Check the official pricing page for current rates.
Does Isorun have a free tier?
$50 of credit on sign-up, no card required (about 1,250 hours of a 1 vCPU + 1 GiB sandbox).
How long can Isorun sessions run?
No maximum lifetime documented. Each sandbox has an idle auto-destroy timer, 300 seconds by default, set per create with timeoutSec or extended with setTimeout(); passing 0 disables it.
Does Isorun support snapshots or pause and resume?
Snapshots: yes. Pause and resume: yes. The image is mounted read-only with a writable scratch layer (4 GiB by default) that lasts for the sandbox's lifetime, including across hibernate/resume. Hibernate keeps filesystem, memory and running processes. Snapshots persist until deleted and restore on any runner in the same region. Optional named persistent disks (ext4 on Tigris Cloud Disk with a local NVMe cache) mount at /workspace, outlive sandboxes and can be snapshotted and forked copy-on-write.
Which regions does Isorun run in?
Organizations are scoped to a US or EU region at sign-up; the API key routes to that region's runner.
What compliance certifications does Isorun have?
SOC 2 Type II listed as "(soon)" on the homepage; each sandbox has an HMAC-chained, tamper-evident audit log.
What are the alternatives to Isorun?
Common alternatives include E2B, Morph Cloud, Fly.io Sprites, Archil, Daytona, Freestyle. See Isorun alternatives for a full comparison.

Sources

  1. isorun.ai
  2. docs.isorun.ai
  3. docs.isorun.ai/getting-started/quickstart
  4. docs.isorun.ai/getting-started/authentication
  5. docs.isorun.ai/getting-started/pricing
  6. docs.isorun.ai/sandboxes/lifecycle
  7. docs.isorun.ai/sandboxes/persistent-storage
  8. docs.isorun.ai/sandboxes/checkpoints-and-rollback
  9. docs.isorun.ai/sandboxes/public-urls
  10. docs.isorun.ai/sandboxes/any-oci-image
  11. docs.isorun.ai/security/network-filtering
  12. docs.isorun.ai/security/credential-injection
  13. docs.isorun.ai/sdks/typescript
  14. docs.isorun.ai/integrations/crewai
  15. docs.isorun.ai/api-reference
  16. docs.isorun.ai/changelog
  17. github.com/isorun/sdk

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 18, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

Agent Sandboxes. (2026). Isorun. agentsandboxes.org. Last reviewed November 18, 2026. https://agentsandboxes.org/sandboxes/isorun/