Skip to main content
Archil persistent sandboxes are Firecracker microVMs whose root filesystem is a durable Archil disk, with pause/resume and fork, managed through the Archil control-plane API. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to archil and these variables:
  • ARCHIL_API_KEY
  • ARCHIL_REGION
To see what Archil costs, connect the Archil integration.

​
Key and permissions

ARCHIL_API_KEY is an Archil control-plane API key (key-…), created in the Archil console via API Keys > Create API Key (or disk CLI / createApiKey). ARCHIL_REGION is the Archil region id the key was created in, for example aws-us-east-1, aws-us-west-2, aws-eu-west-1; a key works only in its own region. Keys are not scoped: full access to the organization or personal account within the key’s region. The docs state API keys ‘have full access to disks in the organization or personal account which created them, including the ability to read data, delete disks, and run sandboxes.’ Sources: docs.archil.com: authorization, docs.archil.com: limits, docs.archil.com: regions, docs.archil.com: introduction, docs.archil.com: typescript.

​
Limits

  • Max 32 vCPU and 64 GiB memory per sandbox; x86-64 images only. (source)
  • Max session length 24 hours, then the sandbox pauses with processes intact; default idle timeout 30 minutes (max 24 hours). On the Free plan a session lasts at most 30 minutes. (source)
  • Persistent sandboxes run only in the AWS public regions aws-us-east-1, aws-us-west-2, aws-eu-west-1 (not gcp-us-central1). (source)
  • Persistent sandboxes are generally available; no per-command timeout. (source)