AgenticFS is a serverless file storage service built for AI agent scenarios. A single file system manages up to 500,000 AgenticSpaces — independent workspaces that provide capacity quotas, access isolation, and performance isolation for each AI agent end user.
AgenticFS and AgenticSpace
|
Term |
Description |
|
AgenticFS |
A region-level file system that centrally manages up to 500,000 AgenticSpaces. |
|
AgenticSpace |
A zone-level independent workspace with its own inode space, providing capacity quotas, access isolation, and performance isolation for a single AI agent end user. |
Based on this architecture, AgenticFS provides the following core capabilities:
-
Agentic elasticity: A single AgenticFS can manage up to 500,000 AgenticSpaces.
-
Agentic capacity management: Set capacity and file count limits per AI agent to prevent resource abuse and control costs.
-
Agentic permission management: Enforce dedicated permissions for each AI agent to ensure access isolation.
-
Agentic performance isolation: Each AI agent supports QoS-based performance isolation for throughput, IOPS, and metadata, preventing interference from abnormal or malicious access and ensuring fault domain isolation.
Application model
AgenticFS supports typical multi-tenant scenarios on AI agent platforms. It maps platform end users to file system resources through four types of objects: AgenticFS, AgenticSpace, access point, and quota:
-
AI agent platform developers provision and manage one or more AgenticFS instances and manage large-scale AgenticSpaces from a unified view.
-
Each AI agent end user is allocated an independent AgenticSpace that serves as the user's workspace and enforces capacity and file count quotas, access isolation, and performance isolation.
-
AgenticFS maps multiple sessions for the same end user to subdirectories within that user's AgenticSpace, storing persistent data such as session logs, memory, Markdown files, and Skills.
-
Access points operate at both the AgenticFS and AgenticSpace levels. Combine them with RAM access policies to enable differentiated resource access for different applications and RAM users/roles.
-
Quotas for capacity and file count apply at the AgenticSpace level.
Specifications
Functional specifications
|
Item |
AgenticFS |
AgenticSpace |
|
Protocol |
|
|
|
Maximum capacity |
100 PiB |
1 PiB |
|
Maximum number of files |
5 trillion |
1 billion |
|
Quantity |
20 per account. You can submit a ticket to request an increase. |
500,000 per AgenticFS. You can submit a ticket to request an increase. |
|
Quota |
Not applicable |
Supports capacity and file count quotas. |
|
Performance isolation |
Not applicable |
Supported |
|
Scaling method |
Auto scaling with a 4 KiB scaling step size. |
Auto scaling with a 4 KiB scaling step size. |
|
Mount latency |
1–3 seconds |
1–3 seconds |
|
Encryption |
Supports encryption in transit. |
Supports encryption in transit. |
|
SLA |
99.95% |
99.95% |
Performance specifications
|
Item |
AgenticSpace |
|
Average latency for single-channel 4 KB read/write operations |
Intra-zone access: 2 ms; cross-zone access: 3–5 ms |
|
Peak throughput |
Initial read/write throughput is 300 MB/s, increasing by 0.3 MB/s per GiB of capacity. Maximum read throughput is 20 GB/s and maximum write throughput is 5 GB/s. |
|
Maximum IOPS |
30,000 |
Note: AgenticFS is a region-level product, and AgenticSpace is a zone-level product.
Limitations
-
AgenticFS is currently in invitation-only preview. To use this service, submit a ticket.
-
A single AgenticFS can have a maximum of 500,000 AgenticSpaces.
-
The parent directory of an AgenticSpace path must exist. Renaming paths and soft links are not supported.
-
Nested AgenticSpaces are not supported. An AgenticSpace cannot be created within an existing AgenticSpace.
-
The maximum number of files for a single AgenticSpace is 1 billion. If this limit is exceeded, write operations fail with a "no space" error.
-
The minimum capacity quota is 1 GiB, adjustable in 1 GiB increments. The new quota value must be greater than the currently used capacity.
Billing
AgenticFS is billed based on the peak storage capacity used per hour. The default billing method is pay-as-you-go. For more information, see AgenticFS Billing.