Start building for free.

Developer has a $10 monthly minimum and Team has a $500 monthly minimum. Your metered usage counts toward that amount—it isn’t a subscription fee added to usage. For example, $6 of Developer usage means a $10 bill; $18 of usage means an $18 bill. Enterprise has a custom minimum commitment.

Free includes 5 disks of up to 10 GB each, 1,000 serverless tool calls, and 30 minutes of sandbox compute, with up to 5 concurrent sandboxes. These are hard caps, with no overage. Free has one workspace and does not include external mounts.

One tool call is one disk.exec invocation, even when it runs several Bash, Python, or Node commands. Developer and Team pay $0.05 per 1,000 calls, with execution included—no additional CPU or memory charge for that call. 100,000 calls use $5 of your monthly commitment; 1 million use $50. Storage and applicable data transfer are metered separately. Model inference isn’t included.

On Developer and Team, data transfer out of Archil costs $0.07 per GB. Transfer within Archil, including to tool calls and sandboxes, is free. Enterprise transfer pricing is custom.

On paid plans, archive storage costs $0.025 per GB-month for file systems that don’t synchronize to customer-owned buckets, separate from active storage. Free’s included storage remains free within its hard caps.

On Developer and Team, CPU is metered at $0.055 per vCPU-hour and memory at $0.020 per GiB-hour. Both count toward your monthly minimum. Persistent sandboxes and services use these compute rates; serverless tool calls use the per-call rate instead.

Team supports 250 concurrent sandboxes. You can add 500 more for $500 per month. Enterprise supports unlimited concurrent sandboxes.

Disks are generally available in AWS us-east-1 (N. Virginia), us-west-2 (Oregon), and eu-west-1 (Ireland), and in GCP us-central1 (Iowa). Other regions, including those in private preview, and dedicated fleets are available on request. Request a region.

Yes. A two-minute script at docs.archil.com/reference/limits reproduces our published mount, read, write, checkpoint, and branch latencies on your own account, and docs.archil.com/details/comparison publishes the method and every result of our Amazon EFS benchmark, including the tests EFS won. Uptime history is public at status.archil.com.

With bring your own bucket, included on every paid plan, Archil writes each file to your S3, GCS, or R2 bucket as an ordinary object at its path. Any S3 tool can read it without Archil, and deleting the disk leaves those objects in your bucket. Managed disks are stored in Archil's internal format, so you export them with any S3 client over Archil's S3 API, or by mounting the disk and copying it. See docs.archil.com/reference/data-ownership.

Yes. Sandboxes boot from standard OCI images, and the same Archil disk mounts in E2B, Daytona, Modal, Vercel Sandbox, or any Linux machine. Keep workspaces on a disk synced to your own bucket, and you can move compute without migrating data. See docs.archil.com/reference/data-ownership.

Yes. Enterprise customers can run Archil in their own cloud account with bring your own cloud (BYOC). Setup is straightforward, and our team can get you running in about an hour.