Managed Kubernetes payment and pricing model

Managed Kubernetes can run:

• on cloud servers — cloud platform resources are charged;
• or dedicated servers — dedicated servers, dedicated server networks, and cloud platform resources are charged (load balancers, public subnets, public IP addresses).

Balance

Cloud platform resources

To pay for cloud platform resources, either a unified balance or a cloud platform balance is used, depending on the account balance type.

You can pay for resources with different types of funds: basic funds, bonuses.

Before paying, top up your balance.

Dedicated server resources

To pay for dedicated server resources, either a unified balance or a main balance is used, depending on the account balance type.

You can pay for dedicated server resources with different types of funds: basic funds, bonuses.

Before paying, top up your balance.

Payment model

Cloud platform resources

The cloud platform uses a pay-as-you-go payment model. Funds for the previous hour of using cloud platform resources are deducted from the balance every hour, and external traffic is also paid for.

For more details on payment, refer to the document Terms of Use for Selected Services: Cloud Platform Service Group.

Dedicated server resources

When creating a Managed Kubernetes cluster on a dedicated server, a billing option is set for it. The billing option determines the duration of the paid period and the payment amount. The payment day is set to the day the dedicated server is handed over, at which point the first paid period begins.

You can view the payment day, payment amount, and billing option duration in the control panel on the server page → Services tab. If necessary, you can change the billing option and payment day.

When the paid period ends, the server is automatically renewed for the same period.

note

For example, a Managed Kubernetes cluster on a dedicated server was created on September 10, 2024, with a six-month billing plan and a cost of 8 000 ₽/month. The amount of the one-time payment when creating the cluster on a dedicated server (taking into account a 7% discount) is 44 640 ₽. The next payment for the dedicated server will be on February 10, 2025. The server will be automatically renewed for six months, and the payment amount will be calculated based on the cost of the dedicated server at the time of renewal.

The payment is charged as a one-time fee for the entire period. When changing the number of nodes on dedicated servers, only basic funds are charged. In all other cases, bonuses are charged first when paying, followed by basic funds. If there are insufficient bonuses, the remainder is charged from basic funds based on the daily cost calculation of the server — for one day using one type of funds.

note

For example, a server costs 3 000 ₽/month, one day costs 100 ₽. Suppose there are 850 ₽ in primary funds and 2 400 ₽ in bonuses. Then, when renewing the service, 2 400 ₽ will be deducted from bonuses first, and then 600 ₽ from primary funds.

Dedicated server billing options

• 1 day;
• 1 month;
• 3 months — 3% discount;
• 6 months — 7% discount;
• 12 months — 15% discount;
• 12 months, monthly payment – 10% discount.

Traffic

Internal traffic

Internal traffic is inbound and outbound traffic between a cloud platform object or a dedicated server and another Servercore product, for example, S3.

Traffic between projects and pools in the Servercore cloud platform is also referred to as internal traffic.

Internal traffic (inbound and outbound) is free of charge.

External traffic

External traffic is the inbound and outbound traffic between the public address of a cloud platform object and a public address on the Internet. In Managed Kubernetes clusters on cloud and dedicated servers, all external traffic is routed through the cloud router's public address. Remaining traffic is classified as internal.

3 TB of free external traffic is provided each month for all projects within a single cloud platform account. After using the free 3 TB, external traffic is charged according to the cloud platform payment model.

By default, basic Servercore DDoS protection is enabled for the cloud platform. Malicious filtered DDoS traffic is not included in consumption and is not charged.

View cloud platform resource consumption

You can view the current cost of the entire cloud infrastructure, as well as consumption and billing for the infrastructure and external traffic, in the Control panel: in the top menu, click Products → Cloud Servers → Platform consumption** section**.

Current cost

Current cost is the amount of money that the current cloud infrastructure configuration consumes over a specific period of time.

Current cost can be viewed in the Control panel: in the top menu, click Products → Cloud Servers → Platform consumption** section** → Current cost** tab**.

You can view the current cost of specific projects, resources, and pools by hour, day, or month.

Infrastructure cost data is updated every hour. In the Control panel, it is displayed 5–35 minutes after the actual changes to the infrastructure and its cost. Recently deleted resources may continue to be displayed in the Control panel until the next data update. However, resource billing stops from the hour following their deletion.

Consumption and billing charts

Infrastructure consumption and billing charts can be viewed in the Control panel: in the top menu, click Products → Cloud Servers → Platform consumption** section** → Expense chart** tab** → Consumed and Paid tabs.

You can view the consumption of specific projects, objects, resources, regions, and pools. Consumption and billing charts can be viewed for a specific time period or sorted by days, weeks, months, or years.

To export consumption and billing details in .csv format, click Download CSV and select how the rows in the export should be grouped (by hour, day, week, month, or year).

All resource locks are shown on the consumption and billing charts.

Traffic

External traffic consumption for the current month can be viewed in the Control panel: in the top menu, click Products → Cloud Servers → Platform consumption** section** → External traffic** tab**.

To export hourly external and internal traffic consumption details for all public account addresses in .csv format, select the period and click Download CSV. You can only export details for the last three months.

Blocking resources if there are insufficient funds on the balance

Cloud platform resources

If there are insufficient funds on the balance at the time of debit, all cloud platform resources will be automatically blocked — note that charges will continue to accrue for them.

To restore access to the resources, you need to top up the balance for the debt amount within 14 days after the blocking. The debt for resources that were charged during the blocking period will be automatically cleared. Projects are not blocked — you can delete the entire project or its resources via the API.

If you do not top up the balance for the amount of the debt within 14 days after the blocking, all cloud platform resources will be deleted. Projects are not deleted in this case.

To ensure you do not miss a balance top-up, you can configure balance status notifications.

Dedicated server resources

If there are insufficient funds on the balance at the time of debit for full payment, the server will be renewed and will continue to be charged daily for some time, depending on the billing option:

• server with billing options of 1 month, 3 months, 6 months, and 12 months — after four days, access ports to the local network and the Internet are blocked; after 10 days, it is deleted without the possibility of recovery;
• server with a billing option of 1 day — network access is blocked immediately; after 24 hours, it is deleted without the possibility of recovery.

Holidays and weekends are not included in the calculation.

If there are insufficient funds on the balance to pay for a day, the server will be charged in debt. The debt does not expire after the server is deleted.

note

For example, the next payment for your server with a 6-month billing plan and a cost of 8 000 ₽/month is October 11, 2024. Upon renewal, 48 000 ₽ should be deducted in one payment. When the payment is generated, the server cost is recalculated. Suppose it increased to 8 100 ₽/month and the total to be charged is 48 600 ₽, but your account has insufficient funds. In that case, upon renewal, the daily cost of the server will be calculated and charged — 48 600 ₽ ÷ 182 days = 267 ₽. The payment will be charged daily until the balance has enough for the full charge (minus the days already paid). If payment is not received, in four days, the ports for server access to the local network and the Internet will be blocked. In 10 days, the server and all data on it will be deleted without the possibility of recovery.

If funds take a long time to arrive or it is not possible to top up the balance, legal entities can request a balance top-up deferral of up to five days. Legal entities and individuals can also enable a product payment deferral.

Prices

Prices for cloud platform and dedicated server resources can be viewed at servercore.com. Prices in pools may vary.

You can calculate the cost of a Managed Kubernetes cluster in the resource calculator.

Accounting documents

After payment, you can receive accounting documents.