Terms of Use of Yandex Compute Cloud

This document contains specific terms of use of Yandex Compute Cloud («the Service») and is an integral part of Yandex.Cloud Customer Agreement («Agreement») and Service Terms set forth at https://yandex.com/legal/cloud_service_terms/. Capitalized terms used herein but not defined herein shall have the meanings set forth in Agreement and Linked Documents.

1. Functional Features of the Service

1.1. Yandex provides Customer with scalable virtual computing capacity to place, store, and process Customer Content, to create and run Virtual Machines and Disks, to manage them, and to use other functional features of the Service.

1.2. As part of the Service, the following resources are available:

(a) Virtual Machines with no virtual operating system installed;

(b) Virtual Machines based on Windows and Linux;

(d) Interrupted Virtual Machines (Interrupted VM);

(e) Reserved instance pools.

1.3. Customer may:

(a) create Virtual Machines in Availability Zones optimal for Customer;

(b) create Virtual Machines with technical parameters that are optimal for Customer;

(d) store Customer Content and make back-up copies using Discs;

(e) access Virtual Machines via SSH using a key pair, via RDP, and using a graphical console;

(f) monitor the state of Virtual Machines;

(g) purchase user licenses for subscription to remote desktop services for Virtual Machines;

(h) resource reservation for launching Virtual Machines using Reserved instance pools;

(i) use other functional features of the Service, which Yandex makes available to Customers. Functional features of the Service are described in Documentation on Site.

1.4. Service Level for the Service is determined in SLA. Interrupted VM and Reserved instance pools are not subject to SLA.

2. Pricing

2.1. The use of the Service is chargeable.

2.2. Service Fee is determined as per Service Rates and billing units specified on Site. Yandex may change Service Rates as stipulated by Agreement.

2.3. Service Fee for a Virtual Machine and Interrupted VM usage depends on the allocated computing resources, operating system, and usage time. Service Fee is calculated for the time of using the VM, from the moment it is started and to a complete stop. The time when the Virtual Machine is stopped is not charged.

2.4. Service Fee for Disk usage depends on usage time (from Disc creation to Disc deletion), selected type of Disk and Disk space. The usage of Disk is charged regardless whether a Virtual Machine is running.

2.5. As part of the Service, the volume of Outgoing Traffic passing through Customer's Virtual Machine or Disk, the cost of Image, Snapshot, user licenses for subscription to remote desktop services, and other additional benefits ordered and used by Customer and related to the use of the Service are charged separately.

2.6. The cost of a Reserved instance pool depends on the number of Virtual Machines the pool is sized for (pool size), the number of CPU cores and the CPU performance tier, the amount of memory (RAM), the operating system, and other parameters that may be specified in the documentation on the Site. The cost is calculated based on the duration of resource reservation, starting from the moment the command to create a Reserved instance pool is executed and continuing until the pool is deleted. Charges apply only to resources that are reserved. Accordingly, the calculation includes time when resources were not used to run Virtual Machines but were reserved for the Client. The time when resources are used to run Virtual Machines is included in the cost of the corresponding Virtual Machines.

2.7. Yandex may from time to time provide Customer with additional functional features of the Service for an additional fee.

3. Limitations

3.1. Customer shall monitor and ensure the security and relevance of software used in Virtual Machines, timely update software versions or make configuration changes as per the Guidelines or requirements published by developers of respective software.

3.2. Customer shall counteract installing malware on Disks; software specifically developed to gain unauthorized access to information; software, databases, and other Content in violation of the intellectual property rights of third parties.

3.3. If any gross violations of information protection requirements threatening the operation of Platform or third-party resources are revealed on the part of Customer, Yandex may interrupt the operation of Virtual Machines that violate security requirements.

3.4. Limitations on the use of Interruptible VM.

3.4.1. Availability of Interruptible VMs to Customer is not guaranteed. Customer is able to create Interrupted VM if Yandex has available computing resources.

3.4.2. Interrupted VM use period cannot exceed Twenty-four (24) hours.

3.4.3. The operation of the Interrupted VM can be completed at any time without warning.

3.4.4. Interrupted VM cannot be changed to Virtual Machine.

3.4.5. Yandex is entitled to impose other restrictions on Interrupted VM, which are published in the Service documentation on Site.

3.5. Limitations on the use of Reserved instance pools.

3.5.1. Provisioning of reserve capacity is not guaranteed and is only possible when free resources are available.

3.5.2. Reserved instance pools reserve compute resources but do not ensure resource availability if the underlying infrastructure hosting the reserved resources fails. In non-routine events (e.g., server failures, infrastructure malfunctions, and similar issues), the reservation may be lost. In such cases, no charges apply for the period during which the reservation was lost.

3.5.3. If the reservation is lost, the Service will automatically attempt to re-create it. However, restoration of the reservation is not guaranteed.

3.5.4. Reserved instance pools can be used only to launch Virtual Machines of a predefined configuration and do not support launching Virtual Machines with other configurations.

3.5.5. Reserved instance pools reserve only the compute resources specified at the time the Reserved instance pool is created. Having a reservation does not prevent shortages of resources not covered by the reservation (e.g., disk space).

3.5.6. Yandex is entitled to impose other restrictions on Reserved instance pools, which are published in the Service documentation on Site.

4. Definitions

“Availability Zones” means geographically distributed data centers that host Yandex's infrastructure used to provide Customer with computing and other resources of Platform. Information on Availability Zones is available on Site and in Management Console;

“Disk” means virtual disk space used to place and store operating systems and Content;

“Image” means a full copy of the structure of file system and data on Disk;

“Incoming Traffic” means an amount of information from the Internet, passing through the virtual computing resources or other cloud resources of Platform provided to Customer;

“Interrupted virtual machine (VM)” means an available Virtual Machine with a lower consumption cost and additional restrictions of use;

“Outgoing Traffic” means an amount of information outgoing to external information systems and passing through the virtual computing resources or other cloud resources of Platform provided to Customer. Information on consumed outgoing traffic is provided to Customer as Statistics aggregated from all Services;

“Snapshot” means a copy of Disk file system at a given moment;

“Virtual Machine” means virtual computing resource of Platform, emulating hardware and used by Customer to remotely process Content.

“Reserved instance pools” are a set of resources reserved for the Client, sufficient to launch a predefined number of Virtual Machines of a predefined configuration.

________________________________________

Web address: https://yandex.com/legal/cloud_terms_compute/

Date of placement: December 19, 2025

Effective date: December 19, 2025

Previous version of the document: https://yandex.com/legal/cloud_terms_compute/01112023/.

Previous version of the document: https://yandex.com/legal/cloud_terms_compute/17022023/.

Previous version of the document: https://yandex.com/legal/cloud_terms_compute/01032020/.

Previous version of the document: https://yandex.com/legal/cloud_terms_compute/26042019/.