Effective date: August 18, 2026 · Last updated: August 18, 2026
- VM Cluster services (GPU virtual machines with root SSH access): VM Cluster Service Terms
- Standalone storage services (Cluster Storage and Object Storage): Storage Service Terms
1. Description of the Container Compute Services
The Container Compute Services are VESSL’s managed AI infrastructure platform for container-based compute, delivering on-demand GPU and CPU Workspaces and Jobs. VESSL orchestrates, schedules, monitors, and operates the Container Compute Services through its proprietary control plane and management software. The underlying compute capacity may be provisioned on infrastructure operated by VESSL or by an underlying infrastructure provider engaged by VESSL as a Sub-processor. A current list of Sub-processors is available in the Sub-processor List. Customer accesses the Container Compute Services through the VESSL platform (including the console, API, and/or CLI) and not by means of any direct, unmodified access to the underlying infrastructure provider’s console or API. The Region(s) in which a given Container Compute Service is provisioned are determined by the Cluster selected by Customer in the VESSL platform. VESSL offers the following Container Compute Service categories, as further described in the Documentation (see Understand workspaces and Understand jobs): Workspaces: On-demand GPU or CPU container instances that Customer can launch, connect to, and use persistently through the VESSL platform. Workspaces provide a containerized environment; Customer does not receive root access to the host operating system or kernel. Jobs: Compute jobs that Customer submits for execution on GPU or CPU resources. Jobs run to completion or until terminated by Customer, and do not provide persistent access to the instance.2. Resource Provisioning
2.1 On-Demand Resources
Where Customer consumes resources on a pay-as-you-go basis, availability is subject to capacity. VESSL does not guarantee on-demand availability except to the extent expressly committed in the SLA.2.2 Region and Data Center
Container Compute Services are provided from the Region(s) determined by the Cluster selected by Customer in the VESSL platform. VESSL may relocate workloads between data centers within the same Region for operational reasons. Migration to alternative infrastructure within the same Region or to a different Region is governed by Section 6.3.3. VESSL’s Obligations and Responsibilities
3.1 Incorporation by Reference
VESSL’s obligations and responsibilities in connection with the Container Compute Services are governed by the following documents: Security: MSA Section 8 Data Processing and Privacy: the DPA and Privacy Policy Security Incident Response: the procedures set forth in the DPA Warranties and Disclaimers: MSA Sections 9 and 10 Limitation of Liability: MSA Section 11 Service Levels: MSA Section 13 and the SLA3.2 Service-Specific Obligations
In addition to and supplementing Section 3.1, VESSL will perform the following obligations specific to the Container Compute Services: (a) Control Plane Operations: VESSL will operate and maintain the control plane for orchestration, scheduling, and monitoring of Workspaces and Jobs. (b) Container Isolation: VESSL will maintain reasonable technical measures to ensure network- and storage-level isolation between each Customer’s container workloads.4. Customer Responsibilities
4.1 Configuration
Customer is responsible for the configuration of its workloads, including container images, parameters, scaling policies, and security configurations on top of the base images provided by VESSL.4.2 Security
Customer is responsible for (a) the access controls and policies that VESSL exposes within Customer’s account on the VESSL Platform, (b) credential management for Customer’s Authorized Users, (c) encryption keys (where Customer manages keys), and (d) the security of any software, configurations, or container images Customer deploys through the VESSL Platform.4.3 Backup, Disaster Recovery, and Storage Durability
Customer is solely responsible for backup, snapshot, and disaster recovery of Customer Content. VESSL does not provide a numerical storage-durability commitment for the Container Compute Services. Customer should design its workloads on the assumption that storage media may fail.4.4 Resource Limits
Data stored only on temporary storage may be lost in the event of a resource-limit violation. Data stored on Cluster Storage or Object Storage volumes is not affected. VESSL is not liable for data loss resulting from resource-limit violations. Customer is responsible for designing workloads to operate within allocated resource limits. Resource-limit enforcement behavior is described in the Documentation (see Resource limits).5. Managed Software Stack
VESSL provides a managed software stack for the Container Compute Services, as described in the Managed software stack documentation. Third-party components included in the stack are provided under the licenses of the respective vendors. Security patching is described in the Documentation (see Managed software stack).6. Maintenance and Replacement
6.1 Scheduled Maintenance
VESSL conducts scheduled maintenance as described in the SLA. Customer is responsible for designing workloads to tolerate maintenance windows.6.2 Hardware Replacement
VESSL may replace hardware components based on monitoring data, including detected GPU errors, storage failures, cooling system failures, or planned hardware refresh. Any migration resulting from hardware replacement is governed by Section 6.3; maintenance-related exclusions and notice are governed by the SLA.6.3 Infrastructure and Region Migration
(a) Same-Region: If VESSL reasonably determines that continued operation on the existing infrastructure within a Region is not commercially feasible, VESSL may migrate Customer workloads to alternative infrastructure in the same Region with at least 30 days’ advance notice (or such shorter period as is reasonably practicable in the circumstances) and migration support. (b) Cross-Region: VESSL will provide Customer with at least 30 days’ advance written notice. If Customer does not object in writing within 30 days of receipt of notice, Customer will be deemed to have consented to the migration. If Customer objects, Customer may terminate the affected Services without penalty and receive a refund for any unused prepaid Fees. (c) Exceptions: This Section does not apply where migration is required to address a security incident, regulatory requirement, or Force Majeure Event.7. Storage
7.1 Storage Types
VESSL may offer multiple storage tiers for use with the Container Compute Services. Standalone storage services (Cluster Storage and Object Storage volumes managed independently) are governed by the separate Storage Service Terms.7.2 Temporary Storage
Each Workspace is allocated temporary local storage for use during the session. Temporary storage is deleted when the Workspace is paused or terminated, and cannot be recovered. Customer must store data requiring persistence on Cluster Storage or Object Storage volumes governed by the Storage Service Terms.7.3 Quotas and Limits
Storage quotas and operational limits, where applicable, are displayed in the VESSL console or described in the Documentation (see Billing overview).7.4 Data Retention on Termination
The applicable data-return, recovery/export, retention, and deletion period is determined by the event and transaction path under MSA Section 5.4, Annex A or the applicable private Order Form, the Storage Service Terms, and the DPA, subject to any express service-specific exception. Customer is responsible for transferring needed data within the applicable period.7.5 Customer Container Images
Customer may use custom container images with the Container Compute Services, including images pulled from Customer’s Git repositories or external registries (collectively, “Customer Images”). Customer retains ownership of Customer Images and is solely responsible for:- the legality of any third-party software included in Customer Images;
- compliance with the licenses applicable to such software;
- the security configuration and contents of Customer Images, including patching, hardening, and removal of secrets;
- Where Customer Images contain Personal Data, establishing a lawful basis for processing and complying with all applicable data protection laws (including the Personal Information Protection Act of Korea and the EU General Data Protection Regulation); and
- downloading and deleting Customer Images upon termination, in accordance with MSA Section 5.4.
8. Billing and Insufficient Balance
For Self-Service, Container Compute Services are billed on a pay-as-you-go basis under Annex A, using Purchased Credits and Promotional Credits as applicable and the pricing displayed in the VESSL console. For B2B, the billing basis, Fees, payment terms, and any committed-use terms are governed by the applicable private Order Form or invoice. Charges accrue based on the resources provisioned or consumed, including applicable GPU or CPU type, duration, and storage. For Self-Service, VESSL may reject creation or start of a Workspace if Customer does not have sufficient Purchased Credits or Promotional Credits. If Customer’s available Purchased Credits and Promotional Credits reach zero, running Workspaces will be automatically paused. Pausing immediately and irreversibly deletes temporary storage data. If Customer does not replenish the applicable balance within twenty-four (24) hours after Pause, the affected Workspaces will be automatically terminated. VESSL may reject a new Job submission, or suspend or terminate a running Job, if Customer does not have sufficient Purchased Credits or Promotional Credits or another authorized payment method to cover the applicable charges. If the Purchased Credits and Promotional Credits available for Self-Service 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.9. Acceptable Use
The Acceptable Use Policy (AUP) applies in full to all use of the Container Compute Services.10. Service Levels
The public SLA applies automatically to eligible paid Self-Service Container Compute Services and measures availability separately for each running Workload. 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.11. Modifications
VESSL may update these Container Compute Terms only in accordance with MSA Section 14.10.VESSL AI, Inc. — legal@vessl.ai