Yandex Smart Web Security pricing policy
Note
Currency of Service rates (prices) depends on the company you made a contract with:
- Prices in US dollars are applicable to customers of Iron Hive doo Beograd (Serbia) or Direct Cursus Technology L.L.C. (Dubai).
- Prices in Russian roubles are applicable to customers of Yandex.Cloud LLC.
All prices below do not include VAT.
What goes into the cost of using Smart Web Security
The cost depends on the billing mode:
-
Subscription: Best for large amounts of incoming traffic.
-
Request count: Best for small amounts of incoming traffic.
Both methods are based on the number of requests across all clouds linked to a single billing account.
Only legitimate requests are counted for billing purposes. These are requests that were allowed by all rules and let through to the protected resource.
At the same time, there are things to consider about billing in the dry run mode:
-
If a rule has blocked a request, in the dry run mode, requests are not blocked and reach their destination. Such requests will be counted for billing.
-
If dry run was enabled only for one rule type, e.g., security profile rules, and the request was blocked by a WAF or ARL rule without dry run on, such a request will not be counted for billing.
Requests processed by ARL profile rules will not be counted for billing. Blocked requests will not be counted either, no matter when and which rule blocked them.
When using domains, in addition to the cost of processed requests, you pay for traffic passing through the proxy server and protection from DDoS attacks at levels L3–L4 of the OSI model
Prices for the Russia region
Note
Yandex Cloud resources are priced differently in different regions. For more information about the available regions, see Regions.
Your payment currency is determined by your contracting legal entity. For more information on creating an account, see Registering an account in Yandex Cloud.
Subscription billing
You pay for packages of legitimate requests. Each package includes a certain number of requests. You can purchase the WAF package only together with the AntiDDoS package.
Our subscription plans are priced per calendar month.
A calendar month is defined as the period from 00:00 on the first day of the month to 23:59 on the last day of the same month, UTC+3. The prices for the number of requests per month are fixed and not based on the number of days in the month.
|
Start, without VAT |
Pro, without VAT |
Business, without VAT |
Enterprise |
|
|
Legitimate requests per month included in the subscription fee, in millions |
100 |
500 |
1,000 |
Calculated separately |
|
Monthly subscription fee for the AntiDDoS package. The package includes processing requests with security profile rules: |
$416.67 |
$1,316.67 |
$2,125.00 |
Calculated separately |
|
Monthly subscription fee for the WAF package. The package includes requests analysis by WAF rules |
$333.33 |
$625.00 |
$1,250.00 |
Calculated separately |
The prices below are for 12-month subscription; no monthly subscription is available.
If the plan you select is not enough, you can switch to another with pro-rata recalculation of the resources consumed to date.
Billing by request count
Tip
To calculate the cost of using the service, use our calculator on the Yandex Cloud website or check out the pricing below.
The prices for service products are also available in the price list.
The billing period is a calendar month.
A calendar month is defined as the period from 00:00 on the first day of the month to 23:59 on the last day of the same month, UTC+3. The prices for the number of requests per month are fixed and not based on the number of days in the month.
You pay for the actual number of legitimate requests. For each request, you pay for:
-
Processing by security profile rules: basic and Smart Protection.
-
Processing by WAF rules. If your request is processed by security profile rules and then WAF rules, you pay for both.
-
Processing by rules in the dry run mode if the request has reached the protected resource.
Requests processed by security profile rules
| Number of requests per month, million | Price per 1,000,000 requests, without VAT |
|---|---|
| Up to 0.01 (10,000 requests), inclusive | Free |
| From 0.01 to 1, inclusive | $224.999910 |
| From 1 to 10, inclusive | $31.499987 |
| From 10 to 100, inclusive | $1.799999 |
| From 100 to 1,000, inclusive | $1.259999 |
| From 1,000 to 10,000, inclusive | $0.450000 |
| Over 10,000 | $0.225000 |
Requests processed by WAF rules
| Number of requests per month, million | Price per 1,000,000 requests, without VAT |
|---|---|
| Up to 0.01 (10,000 requests), inclusive | Free |
| From 0.01 to 1, inclusive | $224.999910 |
| From 1 to 10, inclusive | $31.499987 |
| From 10 to 100, inclusive | $1.799999 |
| From 100 to 1,000, inclusive | $1.259999 |
| From 1,000 to 10,000, inclusive | $0.450000 |
| Over 10,000 | $0.225000 |
To use additional protection against DDoS attacks at OSI layers 3 and 4, enable Yandex DDoS Protection. In this case, you will be billed for using the public IP address and Yandex DDoS Protection.
Proxy server resources
When using domains, you pay for the actual usage of the computing resources of each active proxy server and for traffic protection from DDoS attacks at levels L3–L4.
The amount of proxy server resources used is measured by the number of resource units, i.e., internal VMs provisioned for the proxy server in each one of its availability zones.
One resource unit delivers the following maximum performance (autoscaling thresholds):
- 1,000 requests per second (RPS).
- 4,000 concurrently active connections.
- 300 new connections per second.
- 22 MB (176 Mbit) of traffic per second (covers both incoming and outgoing traffic).
The system autoscales the resource unit group based on external load on the proxy server nodes. It calculates the group size to keep load per resource unit below the specified thresholds.
The default minimum number of resource units per proxy server is 6 (2 in each availability zone). If you need more proxy server resource units, you can submit a request to increase their number.
The proxy server fee is per hour. You are charged for the minimum number of resource units that were running for an hour.
Traffic protection from DDoS attacks at levels L3–L4 is charged based on the amount of legitimate traffic in GB.
Warning
Proxy server resource prices are valid from November 10, 2025.
| Service | Price without VAT |
|---|---|
| One resource unit of proxy server (per hour) | $0.02 |
| Protecting incoming traffic against DDoS attacks (per GB) | $0.009083333333 |
Example of Smart Web Security billing by request count
Pre-calculated request costs
To better understand how the cost of requests is calculated, see the table below with prices calculated for a certain number of requests per month. This number does not include the non-billable limit of 10,000 requests.
The prices below are for reference only. Smart Web Security usage by your services will be calculated based on the actual request count.
| Number of requests per month (in millions) | Cost of requests allowed by the security profile, without VAT | Cost of requests allowed by the security and WAF profiles, without VAT |
|---|---|---|
| 1 | $224.999910 | $449.999820 |
| 10 | $508.499793 | $1,016.999586 |
| 100 | $670.499703 | $1,340.999406 |
| 1 000 | $1,804.498803 | $3,608.997606 |
| 10 000 | $5,854.498803 | $11,708.997606 |
Let’s calculate the cost of 315,040,000 legitimate requests per month processed by security profile rules:
0.01 × 0 + 0.99 × $224.999910 + 9 × $31.499987 + 90 × $1.799999 + 215.04 × $1.259999 = $939.199889, without VAT.
Where:
- 0.01 × 0: Non-billable threshold of the first 0.01 million requests.
- 0.99 × $224.999910: Cost of the subsequent 0.99 million requests.
- 9 × $31.499987: Cost of the subsequent 9 million requests.
- 90 × $1.799999: Cost of the subsequent 90 million requests.
- 215.04 × $1.259999: Cost of the remaining 215.04 million requests.
You can only connect a WAF profile if using a security profile. Both profiles, security and WAF, will contribute to the cost of request processing. Since the security and WAF profiles are priced equally, the total cost will be double that of a security profile alone.
Let’s calculate the cost of 315,040,000 legitimate requests per month processed by security and WAF profile rules:
$939.199889 × 2 = $1,878.399778, without VAT.
Where:
- $939.199889: Cost of 315,040,000 legitimate requests per month processed by security profile rules.
- × 2: The cost is multiplied by
2since the security and WAF profiles are priced equally.
Let’s calculate the cost of 315,040,000 legitimate requests per month when using a proxy server and security profile rules:
$939.199889 + 6 × 720 × $0.02 + 7 × $0.009083333333 = $1,025.663472, including VAT.
Where:
- $939.199889: Cost of 315,040,000 legitimate requests per month processed by security profile rules.
- 6: Minimum number of proxy server resource units.
- 720: Number of hours in 30 days.
- $0.02: Price per proxy server resource unit per hour.
- 7: Amount of incoming traffic (GB).
- $0.009083333333: Price of incoming traffic DDoS protection per GB.