Limits

These are Archil’s current limits. Most can be raised. If a limit or the performance below is in your way, tell us at support@archil.com and we’ll prioritize it. Every latency row can be rerun on your own account with the script in Latency benchmark. The Seen column isn’t a cap. It’s the highest value Archil production has recorded from July 2025 to October 2026. Rates are averaged over one minute.

Disks and files

Limit	Current	Seen
Max file size	1 PiB
Max files in one directory	Unlimited	80K+
Max connected clients per disk	5,000
Max connected clients, all disks	Unlimited	32K+
Max data sources per disk	1
Max disk name length	100 characters
Max branch name length	100 characters

Disk and branch names can use letters, digits, -, and _.

Disks per plan

Plan	Max disks per region	Seen
Free	5
Developer	1,000
Team	25,000
Enterprise	Unlimited	100K+

Disks synchronized with a data source

A disk synchronized with a data source keeps each file as a normal object in your bucket, so these limits apply instead.

Limit	Current
Max file size	5 TiB
Max path or S3 key length	1,024 bytes
Max entries in one directory listed over S3	100,000

The path length includes the bucket prefix, if the disk uses one.

Throughput and requests

Limit	Current	Seen
Max write throughput per disk	1 GB/s	620 MB/s
Max read throughput per disk	Unlimited	5.9 GB/s
Max control-plane API request body	512 KiB

Latency

Operation	p50	p95
Create a disk	9.3 ms	11 ms
Checkpoint a disk	13 ms	19 ms
Branch from a checkpoint	33 ms	36 ms
Delete a disk	8.1 ms	10 ms
Mount a disk	50 ms	58 ms
4 KiB read, client cache miss	0.50 ms	0.75 ms
4 KiB write, `O_SYNC`	2.0 ms	8.2 ms

Checkpoint and branch times don’t depend on disk size. A client cache miss is served from the file server’s cache. Data that has to come from the data source takes longer, typically 10 to 30 ms for Amazon S3. An O_SYNC write returns once the file server has made it durable. We measured these on October 27, 2026 from a c7gn.2xlarge in AWS us-east-1, using the script in Latency benchmark.

Sandboxes

Limit	Current
Max vCPU per sandbox	32
Max memory per sandbox	64 GiB
Max session length	24 hours
Default idle timeout	30 minutes
Max idle timeout	24 hours
Default concurrent commands per sandbox	32
Max concurrent commands per sandbox	256

A sandbox pauses when its session reaches 24 hours or its idle timeout. On the Free plan, a session lasts at most 30 minutes. See Running long jobs.

Serverless execution

Limit	Current
vCPU per command	2
Memory per command	4 GiB
Max command duration	5 minutes
Max command length	100 KiB
Max output returned per stream	4 MiB each for stdout and stderr

Output past 4 MiB on a stream is dropped. See Serverless execution limits.

S3 API

Limit	Current
Max `PutObject` size	5 GiB
Max object size with multipart upload	5 TiB
Max parts per upload	10,000
Min part size	5 MiB
Max part size	5 GiB
Max `CopyObject` source size	5 GiB
Max keys per `ListObjectsV2` page	1,000
Max keys per `DeleteObjects` request	1,000
Default share URL lifetime	24 hours
Max share URL lifetime	7 days

The last part of a multipart upload can be smaller than 5 MiB.

Reproduce these numbers

The script and our full results are on Latency.

Getting started

Compute

Concepts

Data Sources

Details

Administration

Protocols

Reference

Legal