Resource consumption for every environment is billed to the account owner on an hourly basis. The main chargeable resources are RAM and CPU, while disk space, external traffic, public IPv4, and Built-in SSL can also be charged depending on the hosting provider.
Primary Charges
RAM and CPU usage measured through cloudlets.
Provider-Dependent Charges
Disk space and external network traffic may be charged or may include a free allowance.
Optional Extras
Public IPv4 and Built-in SSL can introduce additional charges.
Hourly Billing
Resource consumption is calculated for each hour of environment operation.
The platform provides built-in statistics for monitoring the main resources consumed by each environment, including CPU, RAM, network traffic, and disk usage.
Use built-in Statistics to monitor CPU, RAM, network, and disk consumption in real time.
Resources consumed by environments supplied through subscription-based products are treated as free of charge by default according to the source documentation.
Primary Chargeable Resources
RAM and CPU are the primary resources used for compute billing. Both are measured through the platform’s standard resource unit called a cloudlet.
1 Cloudlet = 128 MiB RAM and 400 MHz CPU.
The two resource types are measured differently during each billing hour:
RAM
Billing uses the peak RAM usage recorded during the hour.
CPU
Billing uses the average CPU usage recorded during the hour.
How Cloudlet Charging Works
RAM and CPU usage are converted to cloudlets independently, but the platform does not add the two values together. For each hour, only the larger of the RAM-derived or CPU-derived cloudlet count is used for billing.
Example: if average CPU usage is 2400 MHz (6 cloudlets) and peak RAM usage is 1024 MiB (8 cloudlets), the charge is based on 8 cloudlets — not 14.
There are two cloudlet types:
Reserved Cloudlets
Resource capacity reserved in advance through the environment topology wizard.
Dynamic Cloudlets
Additional resources that scale dynamically according to application demand.
RAM used by the operating system for disk cache and buffers is excluded from chargeable RAM usage.
Provider-Dependent Charges
Disk space and external traffic are not priced identically by every hosting provider. Some providers charge for all consumption, while others include a free amount.
Disk Space
Disk usage is measured in GB. Billing is based on actual disk consumption, so there is no need to purchase unused storage capacity in advance simply as a reserve.
When a workload requires separate persistent storage, the source recommends considering Primary or Compound data-container architectures because they can reduce duplicate disk usage and lower the total environment cost.
Traffic
Traffic usage is measured in GB. Only external traffic is chargeable: the combined incoming and outgoing traffic exchanged between the environment and the Internet.
External Traffic
Incoming + outgoing data exchanged between the environment and the Internet can be charged.
Internal Traffic
Traffic within the same environment or between environments hosted by the same provider is free according to the source.
Optional Extras
Optional Resource
Purpose
Charging Note
Public IPv4
Provides a directly reachable external IP address for a specific server inside the environment.
Can be charged separately depending on the hosting provider.
Built-in SSL
Creates a secure connection between clients and the environment.
Can be a paid option, although some providers offer it free of charge.
Without a Public IPv4 address, Internet traffic is routed to the environment through the platform resolver / shared load-balancing layer rather than connecting directly to a specific node.
Charged Resources summary: compute is billed hourly using the larger of RAM or CPU cloudlet consumption; disk and external traffic are provider-dependent; internal traffic is free; and optional services such as Public IPv4 and Built-in SSL can add separate charges.
