Yandex Smart Web Security pricing policy
What goes into the cost of using Smart Web Security
The cost depends on the billing mode:
-
By subscription: Best for large amounts of incoming traffic.
-
By 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 towards consumption.
-
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 towards consumption.
Requests processed by ARL profile rules will not be counted towards consumption. Blocked requests will not be counted either, no matter when and which rule blocked them.
Prices for the Russia region
Note
Prices for Yandex Cloud resources vary based on the region. For more information about the available regions, see Regions.
The currency you can use to pay for the resources depends on which legal entity you entered into agreement with. For more information on creating an account, see Registering an account in Yandex Cloud.
Billing by request count
Tip
To calculate the cost of using the service, use the calculator on the Yandex Cloud website or check the pricing data in this section.
Prices for service products are also available in the Price list.
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 | Cost per million 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 | Cost per million 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, connect Yandex DDoS Protection. You will be billed for the public IP address and Yandex DDoS Protection usage.
Example of Smart Web Security billing by requests
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, million | Cost of requests allowed by the security profile, without VAT | Cost of requests allowed by the security profile and WAF, 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.04 million 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 a security profile is used. Both profiles – security and WAF – will contribute to the cost of request processing. Security and WAF profiles being priced equally, the total cost will be double that of a security profile alone.
Let’s calculate the cost of 315.04 million 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.04 million legitimate requests per month processed by security profile rules.
- × 2: the cost is multiplied by
2
because security and WAF profiles are priced equally.