Agent Sandboxesagentsandboxes.org
Head-to-head

Archil vs Fly.io Sprites

Answer in brief

Choose Archil for agents whose files must outlive the sandbox: per-user or per-session disks that serverless commands and long-running microVMs share; choose Fly.io Sprites for long-running, stateful agent computers that should cost nothing while idle. Archil uses Firecracker microVM isolation; Fly.io Sprites uses MicroVM isolation.

By the Agent Sandboxes editors · Updated

Key differences between Archil and Fly.io Sprites

  • Isolation: Archil uses Firecracker microVM; Fly.io Sprites uses MicroVM.
  • Session length: 24 h (then paused) (Archil) versus Unlimited (Fly.io Sprites).
  • SDKs and interfaces: Only Archil lists CLI and REST API. Only Fly.io Sprites lists Go and Elixir.

What they have in common

  • Both companies are based in the United States.
  • Both are hosted platforms.
  • Both use microVM isolation.
  • Neither is open source.
  • Both support snapshots.
  • Both can pause and resume a sandbox.
  • Both list TypeScript and Python.

Archil vs Fly.io Sprites at a glance

AttributeArchilFly.io Sprites
What it isFirecracker microVM sandboxes and one-shot serverless commands that run against durable, S3-backed Archil disks, with forks and pause/resume.Persistent, hardware-isolated Linux computers for AI agents with a durable 100 GB disk, checkpoints, and no compute charges while idle.
TypeHosted platformHosted platform
IsolationFirecracker microVM with its own Linux kernel for each persistent sandbox; each serverless command also runs in its own fresh Linux microVM colocated with the diskDedicated microVM with hardware-level isolation (Fly docs); Fly.io says Sprites run on its Firecracker substrate
Open sourceNoNo (SDKs MIT)
Self-host / BYOCNo / YesNot documented / Not documented
SDKsJavaScript/TypeScript, Python, CLI, REST APIJavaScript/TypeScript, Go, Python, Elixir
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 documentedWarm wake 100–500 ms with processes preserved; cold wake 1–2 s (vendor docs)
Max sessionPersistent 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 minutesNo lifetime limit — a Sprite persists until destroyed and sleeps after ~30 s idle
PersistenceEach 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 API100 GB durable disk per Sprite that survives sleep; copy-on-write checkpoints (~1 s) with restore; memory preserved on warm pause
Snapshots / pauseYes / YesYes / Yes
GPUNot documentedNo GPU option documented
NetworkingFree 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 headerHTTPS URL per Sprite (org-private by default); outbound open by default with optional DNS-based domain allow/deny policy; connectors broker API credentials
PricingFree: $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: customPer second, compute only while active: $0.0385 per CPU-hour + $0.021875 per GB-hour memory; storage billed while idle
Free tierFree 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$1 trial credit for new Fly.io accounts, no card required; invoices under $5 are waived
ComplianceSOC 2 Type II and HIPAA listed on the website; encryption at rest and in transitFly.io is SOC 2 Type 2; HIPAA BAA and DPA available (company-wide)
RegionsAWS us-east-1, us-west-2 and eu-west-1; BYOC deployments on AWS, Google Cloud, Azure or bare metalNot documented
Company headquartersSan Francisco, California, United StatesChicago, Illinois, United States
Good fit forAgents whose files must outlive the sandbox: per-user or per-session disks that serverless commands and long-running microVMs shareLong-running, stateful agent computers that should cost nothing while idle

Verified November 16, 2026 (Archil) and November 14, 2026 (Fly.io Sprites) from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose Archil

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

Reasons to choose Fly.io Sprites

  • You want a persistent computer per agent or per user
  • Your agents are idle most of the time and you want to pay only for active compute
  • You want fast checkpoints and rollback
  • You want Elixir or Go SDKs

Trade-offs to check first

  • Archil: A persistent sandbox session is capped at 24 hours before it is paused.
  • Archil: Boot time for persistent sandboxes and GPU support are not documented.
  • Fly.io Sprites: No GPUs
  • Fly.io Sprites: Fixed 8 vCPU / 100 GB shape; memory platform-managed

Both are worth piloting with your own image and region. See the full Archil profile and Fly.io Sprites profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Archil or Fly.io Sprites better for AI agents?
Neither is better for every workload. Archil suits agents whose files must outlive the sandbox: per-user or per-session disks that serverless commands and long-running microVMs share. Fly.io Sprites suits long-running, stateful agent computers that should cost nothing while idle.
What is the difference between Archil and Fly.io Sprites?
Archil uses Firecracker microVM; Fly.io Sprites uses MicroVM. Session length: 24 h (then paused) (Archil) versus Unlimited (Fly.io Sprites). Only Archil lists CLI and REST API. Only Fly.io Sprites lists Go and Elixir.
Which is open source, Archil or Fly.io Sprites?
Neither is open source.
How do Archil and Fly.io Sprites isolate code?
Archil: 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. Fly.io Sprites: Dedicated microVM with hardware-level isolation (Fly docs); Fly.io says Sprites run on its Firecracker substrate.
How does Archil pricing compare with Fly.io Sprites?
Archil: 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. Fly.io Sprites: Per second, compute only while active: $0.0385 per CPU-hour + $0.021875 per GB-hour memory; storage billed while idle. Rates change, so check the Archil and Fly.io Sprites pricing pages before deciding.
Do Archil and Fly.io Sprites support GPUs?
Archil: Not documented. Fly.io Sprites: No GPU option documented.
Can you self-host Archil or Fly.io Sprites?
Archil: no self-hosted option is documented. Fly.io Sprites: not documented.
How long can sessions run on Archil and Fly.io Sprites?
Archil: 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. Fly.io Sprites: No lifetime limit — a Sprite persists until destroyed and sleeps after ~30 s idle.
Do Archil and Fly.io Sprites support snapshots or pause and resume?
Archil: snapshots yes, pause and resume yes. Fly.io Sprites: snapshots yes, pause and resume yes.

Sources

  1. archil.com
  2. docs.archil.com
  3. docs.archil.com/compute/sandboxes/introduction
  4. docs.archil.com/compute/serverless-execution
  5. fly.io/sprites
  6. docs.fly.io/sprites
  7. docs.fly.io/sprites/concepts/lifecycle.md
  8. docs.fly.io/sprites/concepts/networking.md

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 vs Fly.io Sprites. agentsandboxes.org. Last reviewed November 16, 2026. https://agentsandboxes.org/compare/archil-vs-fly-sprites/