Billing Plans

Before users can create virtual servers in your cloud, it is important to set prices for the resources they use. This is a three-step process: creating a billing plan, setting prices and resources limits for that plan, and then assigning users to that plan.

You can set default (master) and custom resource limits for сompute resource, data store and network zones. The master bucket/template is a virtual zone which does not exist physically. They are added to each billing plan automatically. The main purpose of the master bucket and master template is holding limit and price settings that can be applied to multiple zones with one click. The master bucket sets the total limits for all compute zones added to the bucket. The master template sets the same limits per each zone using master template: you can simply set desired limits and prices per master zone and assign all your data store and network zones to it.

Master Bucket Billing

Master bucket is created automatically with each billing plan as a part of the сompute zone limits section. Master bucket is highlighted in green. You can add or remove сompute zones to/from the master bucket any time after the billing plan creation.

Depending on the configuration, сompute zone billing may behave differently:

  1. The billing plan contains only master bucket with no сompute zones within and besides it.
    In this case the limits and prices set in the master bucket will be applied to all user's virtual servers.  Users will be able to create virtual servers in any сompute zone available as long as there are enough limits in the master bucket.

    If you create or alter a billing plan of a user who already has сompute zones, "orphaned" сompute zones will use master bucket limits. For example, if user has three сompute zones and you add two of them to the billing plan, the third one will be billed according to the master bucket limits.
  2. The billing plan contains several сompute zones, all of which are added to master bucket.
    The users signed up with this plan will be able to manage virtual servers in these zones only. The master bucket limits and prices are total for all the zones and affect all compute resources in these zones as if they were a single zone. For example, if you have three Compute zones added to the master bucket with the CPU limit set to 6, you can either create one virtual server with 6 CPUs in any of three zones, or three virtual servers with two CPUs in any of the three сompute zones, or two virtual servers with three CPUs, and so on.  
  3. The billing plan contains several сompute zones with custom prices and limits.
    Users will only be able to control these zones' resources. The prices and ability to control virtual servers are determined by limits set for each сompute zone individually. For example, you will be only able to create virtual servers in the Compute zones set in the billing plan. Limits and prices for that virtual servers will be taken from the corresponding сompute zone limits (each сompute zone will have its own limits and prices).
  4. The billing plan contains mixed сompute zone limits (both master and custom).
    For example, if there are three сompute zones added to a billing plan, two of which are added to the master bucket and one zone added with custom limits, the first two zones will share the master bucket’s limits, while the third one will use its own limits.

Refer to Set User Billing Plan Prices And Resource Limits section for details on applying resources to zones.

Master Template Billing

Master template is created automatically with each billing plan as a part of the data store zone and network zone limits sections. Master templates are highlighted in yellow. You can add data stores and network zones to the master templates any time after the billing plan creation. 

Depending on the configuration, master template billing may behave differently: 

  1. The billing plan contains only the master template with no data store/network zones added.
    In this case the billing plan does not limit/charge the data stores and networks.
  2. The billing plan contains one or more data store/network zones which are not added to the master template and have custom prices/limits.
    The prices and ability to control virtual servers is determined by limits set for each data store/network zone individually. Users signed up with this billing plan will be able to control only data store/network zones set in the billing plan. Limits and prices will be taken from the corresponding data store/network zone limits (each data store/network zone will have its own limits and prices).
  3. The billing plan contains data store/network zones added to the master template.
    The master template zones’ limits and prices will affect all those data stores/networks according to the limits and prices set in master template. That means that each zone will have the limits and prices as the master template.
  4. The billing plan contains mixed data store/network zone limits (both master and custom).
    For example, if there are three data store zones added to a billing plan, two of which are added to the master template and one zone added with custom limits, the first two zones will have the same limits and prices as those set for the master template, while the third one will use its own limits.

Refer to Set User Billing Plan Prices And Resource Limits section for details on applying resources to zones.


When a zone is assigned to the master bucket or master template, its current prices are substituted with corresponding bucket/template zone’s settings. When you unsubscribe a billing plan limit from the master bucket or master template, its resources will be restored.

When a data store or a network zone is added to the master template, its limit type (hourly or monthly) is overridden by the master template. Currently only hourly limit type is available for master templates, so if a zone had a monthly limit type and then was assigned a master template, the limit type will become hourly. If a zone is removed from the master template, it's limit type will become the same as it was before the master template was applied to the zone.