---
title: "Cloud server payment model and pricing"
sidebar_label: "Payment model and pricing"
sidebar_position: 2
description: "How to pay for a cloud server, what is the cloud server payment model, where to view prices"
---

import ViewConsumption from '@site/i18n/en/docusaurus-plugin-content-docs/current/_partials/cloud-common/view-consumption.mdx'
import Formbricks from '@theme/MDXComponents/Formbricks'
import {CustomTable} from 'docs-kit/components'

# Cloud server payment model and pricing

## Balance \{#balance}

To pay for a cloud server, depending on the account's balance type, a [unified balance](/balance-and-payments/balance.mdx#united-balance) or [cloud platform balance is used](/balance-and-payments/balance.mdx#balances-by-service-type).

You can pay for [cloud server resources](/access-control/projects/about-projects.mdx#selectel-products-that-support-projects) with different [types of funds](/balance-and-payments/balance.mdx#funds-types): basic funds or bonuses.

Before paying, [top up your balance](/balance-and-payments/manage/top-up-balance.mdx).

## Payment model \{#payment-model}

Cloud servers use a pay-as-you-go pricing model. The balance is charged hourly for the previous hour of [cloud server resource](/access-control/projects/about-projects.mdx#selectel-products-that-support-projects) usage and consumed [external traffic](#external-traffic), if it exceeds the 3 TB free traffic limit for all account projects.

Cloud server resource payment is calculated by project. Each project contains a group of resources: the number of cores, disk size, and others.

The cost of a group of resources is updated every astronomical hour.

Payment for resource consumption depends on the resource type (quotated or non-quotated). Learn more about quotated and non-quotated resources in the [Paid Resources](#paid-resources) table.

For quota-based resources, the maximum consumption during the hour is taken into account.

:::note

For example, at 13:25, two cloud servers are created: one with 2 vCPU, the second with 4 vCPU. The second server is deleted at 13:40. The bill for the 13:00–14:00 hour will factor in the consumption of 6 vCPU. For the 14:00–15:00 hour, only 2 vCPU consumption will be factored in, provided no other cloud servers were created.

:::

For non-quota resources, such as traffic or API requests, the sum of the consumed resource is taken into account.

:::note

For example, five cloud servers with public network access are running in a project. During the 13:00–14:00 hour, each server consumed 2 GB of external traffic, and the monthly free traffic quota was exhausted. The bill for the 13:00–14:00 hour will factor in 10 GB of traffic.

:::

If the number of resources changes, for example, the number of cores or disk size, the payment for the resource will change immediately.

:::note

For example, a cloud server's configuration is changed at 13:25 from 2 vCPU to 4 vCPU. For the 13:00–14:00 hour, you will be charged for 4 vCPU.

:::

Payment for resources continues to be charged when a server is turned off or suspended, as resources remain reserved for it. When [freezing a server](/cloud-servers/manage/manage-server.mdx#freeze-server), vCPU, RAM, and GPU are not charged, while other resources are paid for.

:::note

For example, you have created a cloud server with these resources: vCPU, RAM, and a Universal disk. If you [turn off](/cloud-servers/manage/manage-server.mdx#turn-off-server) or [pause the cloud server](/cloud-servers/manage/manage-server.mdx#pause-server), the resources will continue to be billed every hour.

:::

When [transferring a project to another account](/access-control/projects/manage/transfer-project.mdx), resource consumption for the project in the hour during which the transfer is completed will be billed to the receiving account. No charges will be deducted from the source account for that hour.

:::note

For example, a project was transferred at 12:50. The consumption of project resources for the 12:00–13:00 hour will be transferred to the receiving account. The transferring project account will only account for resource consumption before 12:00.

:::

### Paid resources \{#paid-resources}

For more details on payment, see the [Terms of Use for Selected Services: Cloud Platform service group](https://files.selectel.ru/docs/ru/conditions-cloud-platform.pdf) document.

<CustomTable>
  <table data-sticky>
    <thead>
      <tr>
        <th />

        <th>Resources</th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <th rowspan="12">Quota-based <br /><small>You can configure quotas in the control panel </small></th><td>vCPU</td>
      </tr>

      <tr>
        <td>RAM</td>
      </tr>

      <tr>
        <td>GPU</td>
      </tr>

      <tr>
        <td>Custom image storage</td>
      </tr>

      <tr>
        <td>Local disks</td>
      </tr>

      <tr>
        <td>Network volumes</td>
      </tr>

      <tr>
        <td>Load balancers</td>
      </tr>

      <tr>
        <td>File storage</td>
      </tr>

      <tr>
        <td>Direct public IP addresses</td>
      </tr>

      <tr>
        <td>Public floating IP addresses</td>
      </tr>

      <tr>
        <td>Public subnets</td>
      </tr>

      <tr>
        <td>Cloud routers `*`</td>
      </tr>

      <tr>
        <th rowspan="2">Quota-based <br /><small> Quotas are not displayed in the control panel</small></th><td>Backups</td>
      </tr>

      <tr>
        <td>Snapshots</td>
      </tr>

      <tr>
        <th rowspan="1">Non-quota-based</th><td>Inbound and outbound traffic</td>
      </tr>
    </tbody>
  </table>
</CustomTable>

`*` Free in [pools](/infrastructure/locations.mdx#pool) uz-1, uz-2, kz-1, ke-1.

Learn more about all cloud server resources in the [Selectel products that support projects](/access-control/projects/about-projects.mdx#selectel-products-that-support-projects) ⁠ instruction General information about projects.

### Resource statuses that are factored into billing \{#tariffed-objects-statuses}

All created resources are billed, even if they are powered off and in the following statuses:

<CustomTable>
  <table data-sticky>
    <thead>
      <tr>
        <th>Resources</th><th>Statuses</th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>Cloud servers</td><td>`ACTIVE`<br />`PAUSED`<br />`RESCUE`<br />`SHUTOFF`<br />`SUSPENDED`</td>
      </tr>

      <tr>
        <td>Volumes</td><td>`AVAILABLE`<br />`AWAITING TRANSFER`<br />`BACKING UP`<br />`IN USE`<br />`EXTENDING`<br />`RESERVED`</td>
      </tr>

      <tr>
        <td>Backups</td><td>`AVAILABLE`<br />`RESTORING`</td>
      </tr>

      <tr>
        <td>Snapshots</td><td>`AVAILABLE`</td>
      </tr>

      <tr>
        <td>Images</td><td>`ACTIVE`<br />`DEACTIVATED`</td>
      </tr>

      <tr>
        <td>Load balancers</td><td>`ACTIVE`<br />`PENDING CREATE`<br />`PENDING UPDATE`<br />`PENDING DELETE`<br />`FAILOVER STOPPED`</td>
      </tr>

      <tr>
        <td>File storage</td><td>`AVAILABLE`</td>
      </tr>
    </tbody>
  </table>
</CustomTable>

## Blocking resources if there are insufficient funds on the balance \{#insufficient-funds}

If there are insufficient funds on your balance at the time of debiting, all [cloud server resources](/access-control/projects/about-projects.mdx#selectel-products-that-support-projects) will be automatically blocked—you will continue to be charged for them.

To restore access to your resources, you must [top up your balance](/balance-and-payments/manage/top-up-balance.mdx) to cover the debt:

* for cloud servers with GPU—within 12 hours after blocking;
* for other cloud servers—within 14 days after blocking.

If the balance is not topped up to cover the debt within the allotted time after blocking, the cloud server and its resources will be deleted. If there is a local volume among the resources, the data on it will also be deleted. Projects are not deleted in this case.

To ensure you don't miss any balance top-ups, you can [set up balance notifications](/balance-and-payments/manage/balance-notifications.mdx).

## External traffic \{#external-traffic}

External traffic is the inbound and outbound traffic between the public address of a Cloud Platform resource and a public address on the internet. All other traffic is considered internal.

For all projects within a single cloud platform account, 3 TB of free external traffic is provided every month. Once the 3 TB of free external traffic is exhausted, traffic will be billed like other cloud platform resources. This means that funds will be deducted from your balance every hour for the traffic consumed in the previous hour. The cost of paid traffic will be added to the total cost of the resource group within the project.

By default, [Selectel's basic DDoS protection](/anti-ddos/ddos-selectel.mdx) is enabled for the Cloud Platform. Malicious, filtered DDoS traffic is not included in consumption and is not charged.

## Internal traffic \{#internal-traffic}

Internal traffic is the inbound and outbound traffic between the public address of a Cloud Platform resource and the public address of another Selectel service, such as a Dedicated Server.

Traffic between projects and pools in Selectel's cloud platform is also considered internal.

There is no charge for traffic (inbound and outbound) from the Cloud Platform to any other Selectel services.

## View consumption \{#view-consumption}

<ViewConsumption />

## Prices \{#prices}

Prices for resources and paid external traffic exceeding 3 TB can be viewed at [selectel.ru](https://selectel.ru/prices/). Prices in [pools](/infrastructure/locations.mdx#pool) may vary.

You can calculate the cost of a cloud server using the [resource calculator](https://selectel.ru/prices/calculator/).

## Accounting documents \{#billing-documents}

After payment, you can [obtain accounting documents](/balance-and-payments/accounting-documents.mdx).

<Formbricks />