Archil
Firecracker microVM sandboxes and one-shot serverless commands that run against durable, S3-backed Archil disks, with forks and pause/resume. A storage-first sandbox: Firecracker microVMs and one-shot commands built around durable, forkable disks.
Overview
Archil describes itself as "Sandboxes and durable disks for AI". The product is built around the Archil disk: a file system that keeps hot data on SSD and the rest in object storage, either your own S3 bucket (where files stay ordinary S3 objects) or storage Archil manages, and that can be read over POSIX or the S3 API or mounted on your own hosts with the Archil CLI. Code runs against those disks in two ways. Serverless execution runs one Bash, Python or Node.js command in a fresh microVM next to the data and returns, with a 5-minute limit per command. Persistent sandboxes are Firecracker microVMs with their own kernel and a persistent root disk that run for up to 24 hours per session.
A persistent sandbox takes 1 to 32 vCPU and 0.25 to 64 GiB of memory on x86-64, boots from a public or private OCI image, and can be stopped, started, paused (keeping memory and processes) or forked; Archil says a fork's checkpoint takes about 15 ms and its branch about 35 ms regardless of disk size. Idle sandboxes pause after 30 minutes by default, and traffic to an exposed port wakes them. There are TypeScript and Python SDKs, a CLI, a REST API and an AI SDK integration. Compute is billed per vCPU-hour and GiB-hour only while running, with storage billed separately. GPU support is not documented, and the product is not open source, although BYOC deployments are offered.
Notable
- Docs: forking a sandbox checkpoints its root disk in about 15 ms and creates a branch in about 35 ms, regardless of disk size.
- Serverless execution: median 37 ms boot plus mount per command (vendor measurement); hundreds of commands can run in parallel.
- Disks can sit on your own S3 bucket, where files remain ordinary S3 objects readable by other tools.
Archil specifications
| Attribute | Details |
|---|---|
| Isolation | Firecracker microVM with its own Linux kernel for each persistent sandbox; each serverless command also runs in its own fresh Linux microVM colocated with the disk |
| Deployment | Hosted platform · BYOC available |
| Open source | No |
| SDKs and interfaces | JavaScript/TypeScript, Python, CLI, REST API |
| Cold start (vendor claim) | Serverless commands: median boot-plus-mount (queueMs) of 37 ms and 82 ms end to end for a trivial command, measured by Archil from a laptop to a disk in AWS us-west-2; the first call on a new disk took a median 331 ms. Boot time for persistent sandboxes is not documented |
| Max session length | Persistent sandboxes: maxTtlSeconds defaults to and is capped at 24 hours, after which the sandbox is paused, not deleted; Free plan sessions last at most 30 minutes. Serverless commands stop after 5 minutes |
| Persistence | Each sandbox's root filesystem is ext4 on an Archil disk, so files and installed packages survive stop, start, pause and resume; pause also keeps memory and running processes. Mounted Archil disks outlive the sandbox, are SSD-cached over object storage (your own S3 bucket or Archil-managed) and are readable over POSIX and the S3 API |
| GPU | Not documented |
| Networking | Free plan egress is limited to a managed allowlist of package registries, Git hosts, container registries, OS mirrors and model provider APIs; on paid plans you set a per-sandbox firewall policy, and a sandbox created without one has unrestricted egress. Ports are private until exposed; exposed ports are public TLS (SNI) endpoints without authentication, or can be gated with port tokens sent in an X-Archil-Token header |
| Pricing | Free: $0, 5 file systems, 10 GB per disk, 5 concurrent sandboxes, 1,000 serverless tool calls, 1 vCPU-hour and 2 GiB-hours of sandbox compute a month (hard caps). Developer: $10 monthly minimum, 20 concurrent sandboxes. Team: $500 monthly minimum, 250 concurrent sandboxes. Usage on paid plans: $0.055 per vCPU-hour and $0.020 per GiB-hour while a sandbox runs, $0.05 per 1,000 serverless calls, $0.20 per GiB-month active storage, $0.07 per GB egress. Enterprise: custom |
| Free tier | Free plan: 1 vCPU-hour and 2 GiB-hours of sandbox compute, 1,000 serverless tool calls and 5 disks of up to 10 GB a month, no card required |
| Compliance | SOC 2 Type II and HIPAA listed on the website; encryption at rest and in transit |
| Regions | AWS us-east-1, us-west-2 and eu-west-1; BYOC deployments on AWS, Google Cloud, Azure or bare metal |
| Company headquarters | San Francisco, California, United States · More from the United States |
Facts from Archil’s public documentation, verified November 16, 2026. Performance numbers are vendor claims.
Strengths and trade-offs
Strengths
- You want an agent's files on durable disks that outlive any one sandbox and are readable over S3.
- You need both one-shot tool calls and long-running microVMs against the same data.
- You want to fork a sandbox's disk in milliseconds to branch an agent's work.
- You need sandboxes that pause when idle and wake on incoming traffic, billed only while running.
Trade-offs
- A persistent sandbox session is capped at 24 hours before it is paused.
- Boot time for persistent sandboxes and GPU support are not documented.
- x86-64 only, and processes run as root inside the VM.
- Not open source; self-managed deployment is offered as BYOC rather than a public release.
Good fit for: Agents whose files must outlive the sandbox: per-user or per-session disks that serverless commands and long-running microVMs share.
How Archil compares
| Sandbox | Company HQ | Isolation | Open source | Self-host / BYOC | Cold start (vendor) | Max session | Snapshots / pause | GPU | SDKs |
|---|---|---|---|---|---|---|---|---|---|
| Archil | United States | Firecracker microVM | No | No / Yes | 37 ms exec (claim) | 24 h (then paused) | Yes / Yes | Not documented | JavaScript/TypeScript, Python, CLI, REST API |
| Fly.io Sprites | United States | MicroVM | No | Not documented / Not documented | 0.1–2 s wake | Unlimited | Yes / Yes | No | JavaScript/TypeScript, Go, Python, Elixir |
| E2B | United States | Firecracker microVM | Yes | Yes / Yes | Not documented | 1 h / 24 h (Pro) | Yes / Yes | No | Python, JavaScript/TypeScript |
| Morph Cloud | Not documented | VM | No | Not documented / Not documented | <250 ms (restore) | Configurable | Yes / Yes | Not documented | Python, TypeScript |
| Freestyle | United States | VM | No | Not documented / Not documented | 65 ms | Unlimited (paid) | Yes / Yes | Not documented | TypeScript |
| OpenComputer | United States | QEMU/KVM VM | Yes | Yes / Not documented | Not documented | No limit documented | Yes / Yes | Not documented | JavaScript/TypeScript, Python, CLI, REST API |
| Daytona | United States | Containers or VMs | No | Not documented / Yes | <90 ms | Unlimited | Yes / Yes | Yes | Python, TypeScript, Ruby, Go, Java |
Head-to-head: Archil vs Fly.io Sprites
Frequently asked questions
What is Archil?
How does Archil isolate code?
Is Archil open source?
How much does Archil cost?
Does Archil have a free tier?
How long can Archil sessions run?
Does Archil support snapshots or pause and resume?
Can you self-host Archil?
Which regions does Archil run in?
What compliance certifications does Archil have?
Where is Archil, Inc. based?
What are the alternatives to Archil?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 16, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). Archil. agentsandboxes.org. Last reviewed November 16, 2026. https://agentsandboxes.org/sandboxes/archil/