Plans and limits
Disks on every plan use Archil-managed storage by default, so you don’t need a bucket of your own.
Free requires no credit card and includes 1,000 serverless tool calls and 1 hour of sandbox compute
per month: 1 vCPU-hour and 2 GiB-hours, which is one hour of a sandbox at the default size of 1 vCPU and
2 GiB. A Free sandbox session lasts at most 30 minutes. Its usage limits are hard caps, with no overage. Free does not include bring
your own bucket (BYOB) or external mounts.
Team customers can add capacity in blocks of 500 concurrent sandboxes, with each additional block costing $500 per month.
How the monthly minimum works
Your metered usage counts toward your plan’s monthly minimum; the minimum is not a subscription fee added to usage. For example, $6 of Developer usage results in a $10 bill, while $18 of usage results in an $18 bill. Enterprise has a custom monthly minimum and custom usage pricing.Usage rates
These rates apply to Developer and Team. Enterprise pricing is custom, and Free’s included usage remains free within its caps.Storage
Active storage is the time-weighted average of data in Archil’s high-speed storage layer. See Metering for how active data is measured. Archive storage covers all of the data an Archil-managed disk stores in the bucket Archil operates for it, whether or not that data is active. It takes the place of the object storage bill you would otherwise pay a cloud provider, so it applies only to file systems that do not synchronize to customer-owned buckets. For BYOB, you pay your cloud provider for the data in your bucket instead. Active storage is billed on top of archive storage, for the data in the high-speed layer. For example, an Archil-managed disk that holds 100 GB, of which 5 GiB is active on average over the month, uses $2.50 of archive storage and $1.00 of active storage.Serverless tool calls
Eachdisk.exec() invocation, disk.grep() search request, or SQLite query counts as one call.
An exec invocation still counts as one call when it runs several Bash, Python, or Node commands;
a search request counts as one call regardless of how many workers it uses.
Execution is included in the per-call rate, with no additional CPU or memory charge for that
call. For example, 100,000 calls use $5 of your monthly minimum and 1 million calls use $50.
An exec that asks for more than the default 2 vCPU and 4096 MiB
counts as several calls: its size as a multiple of the default, by whichever of vCPU and memory is the larger
multiple, rounded up. For example, 4 vCPU and 4096 MiB counts as two calls, and 8 vCPU and 16,384 MiB as four.
The Free plan runs every exec at the default size.
Storage and applicable data transfer are metered separately. Model inference is not included.
Persistent sandboxes and services
Persistent sandboxes and services use the CPU and memory rates above, metered separately. Both count toward your monthly minimum. These rates do not apply to serverless tool calls, which use the per-call rate. Compute is metered on the vCPUs and memory a running sandbox is allocated, sampled each minute, whatever the sandbox actually uses. A sandbox with 1 vCPU and 2 GiB of memory costs $0.095 an hour. Stopping or pausing a sandbox stops compute charges; its disk data remains subject to storage pricing.Data transfer
On Developer and Team, transfer within Archil is free, including transfer to Archil tool calls and sandboxes. Data leaving Archil, including delivery to external compute, costs $0.07 per GB. Enterprise transfer pricing is custom. Enterprise customers can use private networking to avoid Archil egress charges.Plan features
All plans include multi-AZ durability and community support.- Free: Archil-managed disks, serverless tool calls, and sandboxes, within the limits above. Sandboxes reach a managed allowlist of package registries, Git hosts, container registries, OS package mirrors, and model provider APIs, and all other egress is denied.
- Developer, Team, and Enterprise: BYOB, external mounts, advanced observability, private sandbox images, and custom sandbox network policies, including deny-all egress, domain and CIDR allowlists, and credential brokering.
- Team and Enterprise: SOC 2 compliance documentation and a shared Slack support channel.
- Enterprise: checkpoints and branching for BYOB, private networking via PrivateLink or VPC peering, advanced API key permissions, SSO and SCIM, HIPAA, BYOC and on-premises deployment, 24/7 support, and an availability SLA. DPA and BAA are available.
External mounts
An external mount is a disk mounted on compute outside Archil, such as your own servers, a Kubernetes cluster, or another sandbox provider like E2B or Daytona. External mounts are available on Developer and above. Usage counts toward Developer’s $10 monthly minimum, so a light external workload costs $10 a month. Data read out to external compute is billed as data transfer out of Archil, at $0.07 per GB on Developer and Team. Transfer to Archil sandboxes and serverless tool calls is free.Checkpoints on BYOB disks
Checkpoints and branches need Archil’s flat-block storage format, which Archil-managed disks use in AWS regions on every plan. On Developer and Team, BYOB disks use the native format instead, which writes each file to your bucket as an ordinary object that any S3 tool can read. Native-format disks can’t be checkpointed. Enterprise can create BYOB disks in the flat-block format. On Developer and Team, use an Archil-managed disk for workloads that need checkpoints and branches.Networking
Free, Developer, and Team use public networking. Enterprise supports public networking, PrivateLink, or VPC peering. Contact sales for Enterprise pricing and deployment options.Monitoring usage
Per-disk usage
Each disk in the Archil console has a Usage tab showing a real-time chart of active data over time. You can view usage across multiple time ranges (6 hours, 24 hours, 7 days, 30 days, or all time).Account-wide billing
The Billing page provides a unified view across all disks and regions:- Current active data per disk
- Month-to-date average and projected monthly cost per disk and in total
- Past billing cycles with per-disk breakdowns and links to Stripe invoices
Programmatic access
A
summary response for an Enterprise contract with a $12,500 base fee, 25,000 credits a month and
2,000,000 tool calls included, read mid-period. Money is in dollars. The credits drawn so far
are a credit line on the statement; what is left of each grant, and when it refills, is credits.
The tool calls ran past what is included, so billing invoices only the 400,000 beyond it and the
grant shows as spent, with no credit line of its own:
usage takes a timezone, so “today” resets at your midnight.