Trial period restrictions
- Service Level Agreement (SLA)
- Support
- Yandex Cloud Billing
- Yandex Cloud Marketplace
- Service quotas and limits
- Yandex Compute Cloud
- Yandex Object Storage
- Yandex Virtual Private Cloud
- Yandex Resource Manager
- Yandex Network Load Balancer
- Yandex Managed Service for ClickHouse®
- Yandex Managed Service for MongoDB
- Yandex Managed Service for MySQL®
- Yandex Managed Service for PostgreSQL
- Yandex Managed Service for Redis
- Yandex Message Queue
- Yandex SpeechKit
- Yandex Translate
- Yandex Vision OCR
The trial period is available to businesses only as a means of testing and exploring the cloud infrastructure features. During the trial period, you can use Yandex Cloud resources with some restrictions.
Service Level Agreement (SLA)
The Service Level Agreement (SLA) does not apply to the trial period. We do not recommend running production applications in Yandex Cloud during the trial period.
Support
Technical support is provided in full during the trial period. For more information, see Requesting technical support.
Yandex Cloud Billing
Each cloud in Yandex Cloud must be linked to a single billing account. If you relink an existing cloud, you are effectively transferring it between billing accounts. For legal entities, you cannot relink a cloud and your DataSphere, Tracker, and DataLens services from a paid account to a trial period account.
Yandex Cloud Marketplace
During the trial period, no Yandex Cloud Marketplace paid products are available. However, once your paid consumption starts, you will be able to use the balance of your starting grant to pay for them.
Service quotas and limits
- Quotas are organizational restrictions that can be changed by technical support.
- Limits are technical limitations due to Yandex Cloud architectural features. You cannot change the limits.
Quotas and limits for Yandex Cloud services during the trial period are listed below.
Yandex Compute Cloud
Quotas
| Type of limit | Value |
|---|---|
| Number of virtual machines per cloud | 12 |
| Total number of vCPUs across all VMs per cloud | 32 |
| Total number of vCPUs across all VMs per cloud per ru-central1-c zone | 0 |
| Total number of Intel Ice Lake Compute-Optimized vCPUs across all VMs per cloud | 0 |
| Total virtual memory across all VMs per cloud | 128 GB |
| Total number of disks per cloud | 32 |
| Total number of disks per cloud per ru-central1-c zone | 0 |
| Total HDD storage capacity per cloud | 500 GB |
| Total SSD storage capacity per cloud | 200 GB |
| Total non-replicated SSD storage capacity per cloud | 558 GB |
| Total capacity of ultra high-speed network SSD storages with three replicas per cloud | 186 GB |
| Number of non-replicated disk placement groups per cloud | 5 |
| Total number of disk snapshots per cloud | 32 |
| Total storage capacity of all disk snapshots per cloud | 400 GB |
| Number of disk snapshot schedules per cloud | 32 |
| Total number of file storages per cloud1 | 100 |
| Total number of file storages per cloud per ru-central1-c zone | 0 |
| Total HDD file storage capacity per cloud1 | 0 B |
| Total SDD file storage capacity per cloud1 | 0 B |
| Number of images per cloud | 8 |
| Number of images optimized for deployment per cloud1 | 0 |
| Number of instance groups per cloud | 10 |
| Total number of NVIDIA® Tesla® V100 GPUs across all VMs per cloud | 0 |
| Total number of AMD EPYC™ with NVIDIA® Ampere® A100 GPUs across all VMs per cloud | 0 |
| Total number of Intel Ice Lake with NVIDIA® Tesla® T4 GPUs across all VMs per cloud | 0 |
| Number of concurrent operations per folder | 15 |
| Maximum number of VM placement groups per cloud | 2 |
| Maximum number of VMs per partition in a VM placement group with the partition placement strategy | 100 |
| Number of dedicated hosts per dedicated host group1 | 0 |
| Number of dedicated host groups per cloud | 6 |
| Maximum number of VM network interfaces | 8 |
1 To increase quotas for file storage, deployment-optimized images, or dedicated hosts, contact technical support.
VM limits
Limits per VM depend on the VM platform:
Intel Broadwell
Intel Cascade Lake
Intel Ice Lake
Intel Ice Lake (Compute Optimized)
| Type of limit | Value |
|---|---|
| Maximum number of vCPUs per VM | 32 |
| Maximum virtual memory per VM | Without GPU: 256 GB With GPU: 384 GB |
| Maximum number of disks and file storages attached to a single VM2 | 18 vCPUs or fewer: 8 More than 18 vCPUs: 163 |
| Maximum number of GPUs connected to a single VM | 4 |
| Maximum number of security groups per interface | 5 |
| Maximum number of VMs per VM placement group with the spread placement strategy | 5 |
| Type of limit | Value |
|---|---|
| Maximum number of vCPUs per VM | Without GPU: 80 With GPU: 64 |
| Maximum virtual memory per VM | Without GPU: 1280 GB With GPU: 384 GB |
| Maximum number of disks and file storages attached to a single VM2 | 20 vCPUs or fewer: 8 More than 20 vCPUs: 163 |
| Maximum number of GPUs connected to a single VM | 8 |
| Maximum number of security groups per interface | 5 |
| Maximum number of VMs per VM placement group with the spread placement strategy | 5 |
| Type of limit | Value |
|---|---|
| Maximum number of vCPUs per VM | 96 |
| Maximum virtual memory per VM | 640 GB |
| Maximum number of disks and file storages attached to a single VM2 | 32 vCPUs or fewer: 8 More than 32 vCPUs: 163 |
| Maximum number of security groups per interface | 5 |
| Maximum number of VMs per VM placement group with the spread placement strategy | 5 |
| Type of limit | Value |
|---|---|
| Maximum number of vCPUs per VM | 56 |
| Maximum virtual memory per VM | 448 GB |
| Maximum number of disks and file storages attached to a single VM2 | 32 vCPUs or fewer: 8 More than 32 vCPUs: 163 |
| Maximum number of security groups per interface | 5 |
| Maximum number of VMs per VM placement group with the spread placement strategy | 5 |
2 Including the boot disk.
3 When a VM starts, a maximum of 14 devices, including the boot disk and a NIC, can be connected to it. You should connect other devices when your VM is already running. Please note that if you restart a VM with more than 14 devices connected, it will not be able to boot.
VM limits on disk operations
Network SSD
Network HDD
Non-replicated SSD
Ultra high-speed network storage with three replicas (SSD)
Disk and file storage limits
Network SSD
Network HDD
Non-replicated SSD
Ultra high-speed network storage with three replicas (SSD)
| Type of limit | Value |
|---|---|
| Maximum disk size | 256 TB |
| Allocation unit size | 32 GB |
| Maximum4 IOPS for writes per disk | 40,000 |
| Maximum4 IOPS for writes per allocation unit | 1,000 |
| Maximum5 bandwidth for writes per disk | 450 MB/s |
| Maximum5 bandwidth for writes per allocation unit | 15 MB/s |
| Maximum4 IOPS for reads per disk | 20,000 |
| Maximum4 IOPS for reads per allocation unit | 1,000 |
| Maximum5 bandwidth for reads per disk | 450 MB/s |
| Maximum5 bandwidth for reads per allocation unit | 15 MB/s |
| Type of limit | Value |
|---|---|
| Maximum disk size | 256 TB |
| Allocation unit size | 256 GB |
| Maximum4 IOPS for writes per disk | 11,000 |
| Maximum4 IOPS for writes per allocation unit | 300 |
| Maximum5 bandwidth for writes per disk | 240 MB/s |
| Maximum5 bandwidth for writes per allocation unit | 30 MB/s |
| Maximum4 IOPS for reads per disk | 2,000 |
| Maximum4 IOPS for reads per allocation unit | 300 |
| Maximum5 bandwidth for reads per disk | 240 MB/s |
| Maximum5 bandwidth for reads per allocation unit | 30 MB/s |
| Type of limit | Value |
|---|---|
| Minimum non-replicated disk size | 93 GB |
| Allocation unit size | 93 GB |
| Maximum4 IOPS for writes per disk | 75,000 |
| Maximum4 IOPS for writes per allocation unit | 5,600 |
| Maximum5 bandwidth for writes per disk | 1 GB/s |
| Maximum5 bandwidth for writes per allocation unit | 82 MB/s |
| Maximum4 IOPS for reads per disk | 75,000 |
| Maximum4 IOPS for reads per allocation unit | 28,000 |
| Maximum5 bandwidth for reads per disk | 1 GB/s |
| Maximum5 bandwidth for reads per allocation unit | 110 MB/s |
| Type of limit | Value |
|---|---|
| Minimum capacity of ultra high-speed network storage with three replicas (SSD) | 93 GB |
| Allocation unit size | 93 GB |
| Maximum4 IOPS for writes per disk | 40,000 |
| Maximum4 IOPS for writes per allocation unit | 5,600 |
| Maximum5 bandwidth for writes per disk | 1 GB/s |
| Maximum5 bandwidth for writes per allocation unit | 82 MB/s |
| Maximum4 IOPS for reads per disk | 75,000 |
| Maximum4 IOPS for reads per allocation unit | 28,000 |
| Maximum5 bandwidth for reads per disk | 1 GB/s |
| Maximum5 bandwidth for reads per allocation unit | 110 MB/s |
SSD storage
HDD storage
| Type of limit | Value |
|---|---|
| Maximum storage size | 8 TB |
| Allocation unit size | 32 GB |
| Maximum number of files in storage | 1,000,000 |
| Maximum size of file in storage | 300 GB |
| Type of limit | Value |
|---|---|
| Maximum storage size | 8 TB |
| Allocation unit size | 256 GB |
| Maximum number of files in storage | 1,000,000 |
| Maximum size of file in storage | 300 GB |
Read and write operations utilize the same disk resource. The more read operations you do, the fewer write operations you can do, and vice versa. For more information, see Read and write operations.
4 To achieve maximum IOPS, we recommend performing read and write operations whose size is close to that of the disk block (4 KB by default).
5 To achieve the maximum possible bandwidth, we recommend performing 4 MB reads and writes.
Limits of disk snapshot schedules
| Type of limit | Value |
|---|---|
| Number of disks added to a schedule | 1,000 |
| Number of schedules a disk is added to | 1,000 |
Other limits
| Type of limit | Value |
|---|---|
| Time to complete processes when stopping a VM6 | 30 seconds |
6 When a VM stops, the hypervisor sends a shutdown signal to the VM operating system. The OS needs to terminate the current processes nice and easy within the next 30 seconds to avoid data loss. After this time elapses, the VM process is forced to stop.
Yandex Object Storage
Quotas
| Type of limit | Value |
|---|---|
| Storage volume per cloud | 1 TB |
| Number of buckets per cloud | 25 |
Limits
| Type of limit | Value |
|---|---|
| Maximum object size | 5 TB |
| Total header size per request to HTTP API | 8 KB |
| Size of user-defined metadata in an object | 2 KB |
| Maximum size of data to upload per request | 5 GB |
| Minimum size of data parts for multipart upload, except the last one | 5 MB |
| Maximum number of parts in multipart upload | 10,000 |
| Maximum bucket access policy size | 20 KB |
Yandex Virtual Private Cloud
Quotas
| Type of limit | Value |
|---|---|
| Number of cloud networks per cloud | 2 |
| Number of subnets per cloud | 6 |
| Number of all public IP addresses per cloud | 8 |
| Number of static public IP addresses per cloud | 2 |
| Number of routing tables per cloud | 8 |
| Number of static routes per cloud | 256 |
| Maximum number of security groups | 10 |
| Maximum number of security groups per interface | 5 |
Limits
| Type of limit | Value |
|---|---|
| Minimum CIDR size for a subnet | /28 |
| Maximum CIDR size for a subnet | /16 |
| Maximum number of VM connections when using custom security groups1 2 | 350,000 |
| Supported network and transport layer protocols | IP, ICMP, TCP, UDP, GRE, ESP, AH |
| Maximum number of rules per security group | 50 |
| Maximum number of CIDRs per rule | 50 |
| Size of the DNS server IP address list | 100 characters |
| Maximum number of DNS requests to a DNS server (second address in a subnet) | 1,000 requests per second |
| Maximum number of NAT gateways | 20 |
1 All TCP and UDP connections opened and half-opened within 180 seconds are taken into account. If there are no data or keep-alive packets in the connection during this time, it is forcibly closed.
2 The old network diagram had a limit of 50,000 connections.
Outgoing traffic filtering
Yandex Cloud automatically blocks traffic sent from Virtual Private Cloud public IPs to TCP port 25 of any servers on the internet and Yandex Compute Cloud VMs. The only exception is the traffic sent to Yandex Mail email servers, which is allowed and not blocked.
Yandex Cloud can provide a special public IP address with TCP port 25 opened upon request to the support team if you follow the Acceptable Use Policy. In case you violate the Policy, Yandex Cloud can block outgoing traffic on TCP port 25 again.
For public IPs that are already in use, port 25 cannot be opened.
Yandex Resource Manager
Quotas
| Type of limit | Value |
|---|---|
| Maximum number of clouds per organization | 5 |
| Maximum number of folders per cloud | 50 |
Limits
There are no limits for the Resource Manager service.
Yandex Network Load Balancer
Quotas
| Type of limit | Value |
|---|---|
| Number of load balancers per cloud | 2 |
| Number of target groups per cloud | 100 |
Limits
| Type of limit | Value |
|---|---|
| Number of resources per target group | 254 |
| Number of listening ports | 10 |
| Number of health checks per attached target group | 1 |
| Status check protocol | TCP, HTTP |
Other restrictions
A single target group may only contain target resources from a single cloud network.
A target group can include resources that are connected to the same subnet within a single availability zone.
A resource will not be directly available on the target port if you add it to the internal load balancer's target group.
You can create a load balancer without a listener.
Health checks are transmitted from the 198.18.235.0/24 and 198.18.248.0/24 IP address ranges.
When connecting resources to the load balancer, keep in mind the limit on the maximum number of concurrent TCP/UDP connections per VM.
Yandex Managed Service for ClickHouse®
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM) |
| Number of ClickHouse® hosts in a non-sharded cluster when using HDD or SSD network storage | 1 | 7 |
| Number of ClickHouse® hosts in a non-sharded cluster when using non-replicated SSD storage | 3 | 7 |
| Number of ClickHouse® hosts in a non-sharded cluster when using local SSD storage | 2 | 7 |
| Number of shards in a sharded cluster | 1 | 50 |
| Number of hosts in a shard when using network HDD or SSD storage | 1 | 7 |
| Number of hosts in a shard when using non-replicated SSD storage | 3 | 7 |
| Number of hosts in a shard when using local SSD storage | 2 | 7 |
| Total number of hosts per cluster | 1 | 353 (50 shards × 7 hosts + 3 ZooKeeper hosts) |
| Amount of data per host when using network HDD or SSD storage (for Intel Broadwell and Intel Cascade Lake) | 10 GB | 4,096 GB |
| Amount of data per host when using network HDD or SSD storage (for Intel Ice Lake) | 10 GB | 8,192 GB |
| Amount of data per host when using non-replicated SSD storage | 93 GB | 16,368 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | 368 GB | 2944 GB |
| Number of databases per cluster | 1 | 1000 |
Yandex Managed Service for MongoDB
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM) |
| Number of shards per cluster | 1 | 10 |
| Number of hosts per shard when using network HDD or network SSD storage | 1 | 7 |
| Number of hosts per shard when using non-replicated or local SSD storage* | 3 | 7 |
| Number of hosts per cluster | 1 or 3 hosts depending on the disk type; the cluster is created in an unsharded state. | 70 (10 shards, 7 hosts) |
| Amount of data per host when using network HDD or SSD storage | 10 GB | 2048 GB |
| Amount of data per host when using non-replicated SSD storage | 93 GB | 2232 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake)* | 100 GB | 1500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake)* | 368 GB | 2944 GB |
| Number of databases per cluster | 1 | 1000 |
* Read more on how platform selection affects available storage types.
The maximum available number of simultaneous connections to a single Managed Service for MongoDB cluster host depends on the amount of RAM on the host:
| Amount of RAM | Maximum number of connections |
|---|---|
| 2 GB | 2048 |
| 4 GB | 4096 |
| 8 GB | 8192 |
| 16 GB or higher | 16 384 |
Yandex Managed Service for MySQL®
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Cascade Lake, 640 GB RAM) |
| Number of hosts per cluster when using HDD or SSD network storage | 1 | 7 |
| Number of hosts per cluster when using non-replicated SSD or local SSD storage | 3 | 7 |
| Amount of data per host when using network SSD storage | 10 GB | 6,144 GB |
| Amount of data per host when using network HDD storage | 10 GB | 2,048 GB |
| Amount of data per host when using non-replicated SSD storage | 93 GB | 8,184 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | 368 GB | 2944 GB |
| Number of databases per cluster | 1 | 1000 |
Yandex Managed Service for PostgreSQL
Quotas
| Type of limit | Value |
|---|---|
| Connection time-to-live | 12 hours |
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM) |
| Number of hosts per cluster when using HDD or SSD network storage | 1 | 16 |
| Number of hosts per cluster when using non-replicated SSD or local SSD storage | 3 | 16 |
| Amount of data per host when using network SSD storage | 10 GB | 4096 GB |
| Amount of data per host when using network HDD storage | 10 GB | 2048 GB |
| Amount of data per host when using non-replicated SSD storage | 93 GB | 10230 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | 368 GB | 2944 GB |
| Number of connections per user | 1 | 15,985 |
| Number of databases per cluster | 1 | 1000 |
Yandex Managed Service for Redis
Quotas
| Type of limit | Value |
|---|---|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 64 |
| Total virtual memory for all database hosts per cloud | 512 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
Limits
| Type of limit | Minimum value | Maximum value |
|---|---|---|
| Host class | b2.medium (burstable, 4 GB RAM) |
hm3-c32-m512 (32 vCPU Intel Ice Lake, 512 GB RAM) |
| Number of hosts in an unsharded cluster | 1 or 3 depending on the disk type | 7 |
| Number of shards in a sharded cluster | 1 | 10 |
| Number of hosts per shard when using network SSD storage | 1 | 7 |
| Number of hosts per shard when using local SSD storage* | 2 | 7 |
| Number of hosts per shard when using non-replicated SSD storage* | 3 | 7 |
| Number of hosts in a sharded cluster | 1, 2, or 3 hosts depending on the disk type | 70 (10 shards, 7 hosts) |
| Amount of data per host when using network SSD storage | Twice the amount of selected RAM | 4,096 GB |
| Amount of data per host when using non-replicated SSD storage* | Twice the amount of selected RAM, at least 93 GB | 8,184 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake)* | Twice the amount of selected RAM, at least 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake)* | Twice the amount of selected RAM, at least 368 GB | 2944 GB |
| Number of cluster connections | — | 65,000 |
* Read more on how platform selection affects available storage types.
Yandex Message Queue
Quotas
Messages
| Type of limit | Value |
|---|---|
Number of SendMessage and SendMessageBatch calls per queue |
300 calls per second for a standard queue |
Number of ReceiveMessage calls per queue |
300 calls per second for a standard queue |
Number of DeleteMessage and DeleteMessageBatch calls per queue |
300 calls per second for a standard queue |
Number of ChangeMessageVisibility and ChangeMessageVisibilityBatch calls per queue |
300 calls per second for a standard queue |
Number of CreateQueue calls per cloud |
2 calls per second |
Number of DeleteQueue calls per cloud |
5 calls per second |
| Number of other request calls per cloud | 100 calls per second |
| Number of queues per cloud | 1,000 |
Limits
Queues
| Type of limit | Value |
|---|---|
Minimum message enqueue delay (DelaySeconds parameter) |
0 seconds |
Maximum message enqueue delay (DelaySeconds parameter) |
900 seconds (15 minutes) |
| Number of messages being processed per standard queue | 120,000 |
| Number of messages being processed per FIFO queue | 20,000 |
| Rate of enqueueing messages in a FIFO queue | 100 messages per second |
| Queue name | Maximum of 80 characters, including numbers, lowercase and uppercase Latin letters, hyphens, and underscores. The name of a FIFO queue must end with the .fifo suffix. |
Messages
| Type of limit | Value |
|---|---|
Number of SendMessage and SendMessageBatch calls per queue |
30 calls per second for a FIFO queue |
Number of ReceiveMessage calls per queue |
30 calls per second for a FIFO queue |
Number of DeleteMessage and DeleteMessageBatch calls per queue |
30 calls per second for a FIFO queue |
Number of ChangeMessageVisibility and ChangeMessageVisibilityBatch calls per queue |
30 calls per second for a FIFO queue |
| Batch entry ID | Maximum of 80 characters, including numbers, lowercase and uppercase Latin letters, hyphens, and underscores |
| Maximum number of message attributes | 10 |
| Maximum number of entries per batch | 10 |
| Message content | XML, JSON, and unformatted text. The following Unicode characters are supported:
|
| Maximum period for retaining messages in a queue | 1,209,600 seconds (14 days) |
| Minimum period for retaining messages in a queue | 60 seconds (1 minute) |
Maximum message enqueue delay (DelaySeconds parameter) |
900 seconds (15 minutes) |
Minimum message enqueue delay (DelaySeconds parameter) |
0 seconds |
| Maximum message size | 262,144 bytes (256 KB) |
| Minimum message size | 1 byte |
| Maximum message visibility timeout | 12 hours |
| Minimum message visibility timeout | 0 seconds |
Maximum client message wait time in an empty queue (WaitTimeSeconds parameter) |
20 seconds |
Yandex SpeechKit
Quotas
| Type of limit | Value |
|---|---|
| Streaming recognition mode | |
| Requests per second | 40 |
| Synchronous recognition | |
| Requests per second | 20 |
| Asynchronous recognition | |
| Recognition requests per hour | 500 |
| Operation status check requests per hour | 2,500 |
| Billable hours of audio per day | 10,000 |
| Speech synthesis | |
| Requests per second | 40 |
Limits
| Type of limit | Value |
|---|---|
| Streaming recognition mode | |
| Maximum duration of transmitted audio for entire session | 5 minutes |
| Maximum size of transmitted audio data | 10 MB |
| Maximum number of audio channels | 1 |
| Synchronous recognition | |
| Maximum file size | 1 MB |
| Maximum duration of audio | 30 seconds |
| Maximum number of audio channels | 1 |
| Asynchronous recognition | |
| Maximum file size | 1 GB |
| Maximum duration of audio | 4 hours |
| Period for storing recognition results on the server | 3 days |
| Speech synthesis | |
| Minimum duration of a pattern for synthesis | 1 second |
| Maximum REST request size | 5,000 characters |
| Maximum gRPC request size | 250 characters and 24 seconds |
| Maximum gRPC request size in unsafe mode | 5,000 characters |
Yandex Translate
Quotas
| Type of limit | Value |
|---|---|
| Calls of one API method per second | 20 |
| Characters sent for translation or language detection, per hour | 1 million |
Limits
For limitations on the field values in the request body, see the API reference.
The limits for using glossaries are as follows:
-
The number of pairs sent to glossaries must be no more than 50.
-
The total number of Unicode characters in this structure must be no more than 20,000: 10,000 characters per source text and 10,000 characters per target text.
Warning
This only refers to texts without CGI parameters.
Yandex Vision OCR
Quotas
| Type of limit | Value |
|---|---|
| Number of requests per second, synchronous mode | 1 |
| Number of requests per second, asynchronous mode | 10 |
| Number of requests per second, asynchronous mode (getting an operation status) | 50 |
| Number of requests per second, asynchronous mode (getting a response) | 50 |
Limits
| Type of limit | Value |
|---|---|
| Period for storing recognition results on the server | 3 days |
| Maximum file size for the OCR API | 10 MB |
| Maximum image size | 20 MP (length × width) |
| Maximum number of pages in a PDF file when using the OCR API in asynchronous mode | 200 |
ClickHouse® is a registered trademark of ClickHouse, Inc.