Skip to main content
Effective date: August 18, 2026 · Last updated: August 18, 2026
These Storage Service Terms (“Storage Terms”) supplement the Master Services Agreement (the “MSA”) and govern Customer’s use of the VESSL standalone storage services, including Cluster Storage and Object Storage (collectively, the “Storage Services”). In the event of a conflict between these Storage Terms and the MSA, these Storage Terms will prevail over the MSA to the extent of the conflict, in accordance with the order of precedence set out in MSA Section 2.2. Scope note: These Storage Terms apply to standalone storage volumes that Customer creates and manages independently through the VESSL platform. Storage resources that are provisioned as an integral component of another Service (e.g., block storage attached to Container Compute Workspaces, NFS Storage within VM Clusters, or temporary local storage allocated during a Workspace session) are governed by the Service-Specific Terms for that Service, not by these Storage Terms. Capitalized terms not defined here have the meanings given in the MSA.

1. Description of the Storage Services

The Storage Services are VESSL’s managed data-storage services, enabling Customer to create, manage, and access persistent storage volumes through the VESSL platform (including the console, API, and/or CLI). The Storage Services currently comprise the following storage types: Cluster Storage: High-availability shared storage provisioned within a specific Cluster. Data persists independently of Workspace and Batch Job lifecycle. Object Storage: Shared storage that is not bound to a specific Cluster. Data persists independently of Workspace and Batch Job lifecycle. VESSL may introduce additional storage types or tiers from time to time, as described in the Documentation (see Understand storage). Temporary local storage (e.g., NVMe scratch space allocated during a Workspace session) is not part of the Storage Services; it is ephemeral and is deleted when the Workspace is paused or terminated.

2. Definitions

In addition to the terms defined in the MSA, the following terms apply to these Storage Terms: “Cluster Storage” means the VESSL storage service that provides persistent, shared storage within a Cluster. “Cluster Storage Volume” means a customer-visible persistent storage volume created through the VESSL platform, bound to a specific Cluster, and mountable by one or more Workspaces or Jobs in that Cluster. “Object Storage” means shared storage volumes that are accessible across Clusters and teams within an Organization, independent of any specific Cluster. “Volume” means a persistent storage unit created by Customer that can be mounted to Workspaces or Batch Jobs to store and access data.

3. Provisioning and Access

3.1 Volume Creation

Customer may create Volumes through the VESSL platform. Volume creation is subject to the quotas, limits, and permissions described in the Documentation (see Create a volume).

3.2 Access Control

Customer is responsible for configuring access permissions for each Volume, including team assignments and Workspace attachments. VESSL provides role-based access controls as described in the Documentation (see Manage volume data). Customer is solely responsible for the accuracy and appropriateness of its access-control configuration.

3.3 Data Upload and Management

Customer may upload, download, browse, and manage files within Volumes as described in the Documentation (see Load data into a volume). Operations that exceed documented quotas, rate limits, or file-size limits may be throttled or rejected.

3.4 Workspace and Job Attachment

Volumes may be attached to Workspaces and Batch Jobs as described in the Documentation (see Create a workspace). The attachment does not transfer ownership of the Volume or its contents. When a Workspace is terminated, the attached Volume and its data persist unless Customer explicitly deletes the Volume.

3.5 Cluster Binding

Cluster Storage volumes are bound to the Cluster in which they are created. Object Storage volumes are not bound to any specific Cluster and may be accessed from any Cluster within the Organization.

4. Storage Characteristics

4.1 Performance

Storage performance may vary depending on workload patterns, concurrent access, and underlying infrastructure. VESSL does not guarantee specific throughput, IOPS, or latency levels for the Storage Services.

4.2 Durability and Data Protection

VESSL uses commercially reasonable measures to protect data stored in the Storage Services against loss. However, VESSL does not provide a numerical storage-durability commitment. Customer should maintain independent copies of all critical data.

4.3 Availability

The public SLA applies only to eligible Cluster Storage and measures availability separately for each affected Cluster Storage Volume. Object Storage is not a Covered Service under the public SLA.

4.4 Persistence

Data stored in both Cluster Storage and Object Storage persists independently of Workspace and Batch Job lifecycle. This is distinct from temporary local storage, which is ephemeral and deleted when the Workspace is paused or terminated.

5. Quotas and Limits

Storage capacity selections, technical limits, and operational limits, where applicable, are displayed in the VESSL console or described in the Documentation (see Storage pricing). The applicable billing basis is governed by Section 8 and Annex A or the applicable private Order Form.

6. Customer Responsibilities

This Section sets out Customer-side responsibilities specific to the Storage Services. VESSL’s obligations are governed by the MSA, the Data Processing Agreement (DPA), the Privacy Policy, and the SLA.

6.1 Content

Customer is solely responsible for (a) the legality, accuracy, and quality of all content stored in the Storage Services, (b) obtaining all rights and consents necessary to store and process such content, (c) compliance with applicable data-protection laws, and (d) ensuring that stored content does not violate the Acceptable Use Policy (AUP) or applicable law.

6.2 Backup

Customer is responsible for maintaining backup copies of data stored in the Storage Services that Customer considers critical. The Storage Services do not include an automated, self-service, or guaranteed backup or restore service. VESSL may, in its discretion and subject to technical feasibility, provide limited manual assistance in response to a support request, but such assistance does not transfer Customer’s backup responsibility or create a recovery, restoration-time, or data-integrity commitment. VESSL’s liability for data loss is governed by Section 11 (Limitation of Liability) of the MSA.

6.3 Access Management

Customer is responsible for properly configuring access permissions for Volumes and for managing which Authorized Users and workloads can access Customer’s data. Unauthorized access resulting from Customer’s misconfiguration is Customer’s responsibility.

6.4 Data Hygiene

Customer is responsible for managing the lifecycle of its Volumes, including deleting Volumes that are no longer needed.

7. Data Retention and Deletion

7.1 During the Subscription Term

Customer data remains in the Storage Services for so long as the applicable Volume exists and Customer’s account is active. Customer may delete individual files or entire Volumes at any time through the VESSL platform. Deletion of a Volume is permanent and irreversible. Customer should download any needed data before deleting a Volume.

7.2 Lifecycle Events

(a) Voluntary Self-Service Account Termination. Ordinary account access ends immediately. Eligible Customer Content is available only through the controlled fourteen (14)-day recovery or export process described in Annex A and the DPA. After that period, VESSL may delete the remaining Customer Content in accordance with the DPA. (b) Self-Service Payment Depletion. If the Purchased Credits and Promotional Credits available for the Storage Services are exhausted and no other authorized payment method covers those Services, VESSL may restrict access to affected Cluster Storage and Object Storage. VESSL will retain the affected persistent storage for a fixed period of thirty (30) days and will provide notice before deletion. The thirty-day period begins when the applicable balances first become exhausted and remain insufficient to cover the Storage Services. Replenishment or authorization of another payment method before deletion cures the depletion condition and restores access subject to ordinary technical processing time. If Customer later exhausts the applicable payment coverage again, a new thirty-day period begins. After the full thirty-day period, VESSL may permanently delete the affected storage and associated Customer Content. (c) B2B Termination. The data-return or deletion period stated in the applicable private Order Form controls and may be up to ninety (90) days if expressly stated. If the Order Form does not state a period, MSA Section 5.4 and the DPA control. (d) Backups and Required Retention. DPA Section 12 governs backups, legal holds, residual records, and deletion from systems where immediate deletion is not technically feasible.

7.3 Cluster Decommission

If the Cluster underlying a Cluster Storage Volume is decommissioned, VESSL will provide reasonable advance notice and, where practicable, assist Customer in migrating data to an alternative Cluster or to Object Storage. VESSL’s obligation in such circumstances is limited to providing commercially reasonable migration support during the notice period.

8. Billing

For Self-Service, Storage Services are billed under Annex A using the rates, billing cycles, calculation methods, and any outbound data-transfer charges displayed in the VESSL console. VESSL will provide at least seven (7) days’ advance notice before an increase to a published Self-Service Storage Services usage rate takes effect. The increase applies prospectively and does not alter Fees accrued before its effective date. For B2B, the applicable private Order Form or invoice governs rates, committed Fees, billing cycles, and data-transfer charges during its term.

9. Preview Features

VESSL may introduce new features or capabilities within the Storage Services and designate them as “Preview,” “Beta,” or similar in the Documentation or VESSL platform. Such designated features are subject to MSA Section 2.3 (Beta Services), may be modified, re-priced, or discontinued, and are excluded from the SLA. This designation applies only to features expressly labeled as such, and not to the underlying Storage Service types (Cluster Storage, Object Storage) as a whole.

10. Acceptable Use

The Acceptable Use Policy applies in full to all use of the Storage Services.

11. Service Levels

The public SLA applies automatically to eligible paid Self-Service Cluster Storage and measures availability separately for each affected Cluster Storage Volume. Object Storage is not a Covered Service under the public SLA. For a B2B Customer, the public SLA applies by default, except to the extent an applicable Custom SLA Addendum or Order Form expressly provides otherwise. Service Credits are Customer’s sole monetary remedy for a failure to meet an applicable SLA metric, subject to the exceptions and no-double-recovery rule in the SLA and MSA Section 13.

12. Modifications

VESSL may update these Storage Terms only in accordance with MSA Section 14.10.
VESSL AI, Inc. — legal@vessl.ai