Billing for cloud services (IaaS)

We use an hourly billing for the consumed resources. Thus if you launched a server (an instance) and deleted it after 2 hours, you would pay only for 2 hours of use. If the server works for a whole month, then you should pay for 720 hours (30 days * 24 hours).

It is important to take into account that a switched off server reserves the resource and that is why it is billed in full. Only when the server is deleted the billing is stopped. In order to maximize your gain due to the dynamic resource creation you need to separate the stored data and calculations.

The rendering of services is based on payment in advance. This means that you should pay in advance for the planned amount of consumed services and monitor the state of your personal account.
In your user account you will be able to monitor the consumed resource and see the forecast - how many days you have left for the paid resource. We will definitely remind you about this as the zero balance approaches.

In order to start using our services you need to replenish the account with an amount of at least $10. The amount of money on your account is transferred to the next month and cannot be lost.

In a computing cloud you use resources, such as a disk, measured in GB. You can increase the disk as needed and this will increase the billing for disk only. The instances (servers) consist of 3 resources - the number of CPU cores, the amount of RAM and the size of the root disk. These 3 resources are billed separately.

If you want to create an instance (server), you can select one of the available types. The instance types are optimized for several types of tasks. So you can choose the appropriate type and size, or combine a different combination of types and different additional disks.

root-диск - a disk on which the image of the operating system is deployed, can be increased only when performing an upgrade of the instance.
volume - a dynamically connected disk, can be increased regardless of the instance.

We do not use ephemeral storage. root and volume disks can be of two types - standard or iops, depending on the requirements for the number of input / output operations. Object storage - access via swift or ftp / http protocol cannot be used as block storage (connected as a disk to an instance).

The incoming and outgoing traffic in the network is billed according to the rate of consumption together with the other resources. The traffic passing through the internal network (among instances) is not billed.

Within the network you can create personal networks (VLANs), manage their Internet connection and connect instances to them.

It is possible to reserve public IP addresses and assign/reassign them to instances.

While calculating the billing there are applied discounts according to the amount of consumed resources.

The discount is applied separately to each kind of consumed resource.
The discount is calculated again from every 1st day of the month.
For example: each of the 25 basic1.m instances (2c/4g/100g) for full 30 days will consume:
2 * 720 = 1440 core hours
4 * 720 = 2880 Gb-hours
100 * 720 = 72000 Gb-hours

25 instances all together will consume: 36000 core hours, 72000 Gb-hours (memory), 1.8 Tb–hours (disk), the discount will be applied to each of the three categories of resources.