Resources and limits
This page contains detailed information about account and project organization, the weights of virtual CPU modes, and default system limits.
Resource Organization
Cloud infrastructure management is divided into two logical levels: account and projects.
| Management Level | Contents |
|---|---|
| Account | General profile settings, financial balance, and total vCPU limit (shared across all projects). |
| Project | Virtual machines, private networks (VLANs), reserved public IPs, Cloud Gateways, backup storage (PBS datastore), team access permissions, and hourly cost details. |
Public Cloud services are billed hourly in Polish Zlotys (PLN). We offer two payment models:
- Prepaid — funds are deducted hourly from your balance. Automatic balance replenishment from a saved card is available (auto-reload).
- Postpaid — pay for actually consumed resources. You receive a single invoice at the beginning of each month for the previous period (requires approval).
For more details on payment models, see the Billing models section.
CPU Modes
When creating a virtual machine or resizing it, you choose the CPU mode and the number of vCPUs.
The number of vCPUs determines how many virtual cores the guest operating system “sees.” On the other hand, the CPU mode defines the total maximum limit of processor time that the VM can use collectively on the physical host.
One fully loaded vCPU corresponds to 100% of a physical core’s time.
| CPU Mode | Total CPU Limit for VM |
|---|---|
| Performance | Up to 100% per vCPU (e.g., 4 vCPUs = up to 400% CPU time) |
| Eco | Up to 50% per vCPU (e.g., 4 vCPUs = up to 200% CPU time) |
| Slim | Up to 25% per vCPU (e.g., 4 vCPUs = up to 100% CPU time) |
Example of running in Eco with 4 vCPUs (200% limit): The virtual machine can use any load combination within the limit — for instance, loading all four virtual cores at 50% each, or two virtual cores at a full 100% (while the other two cores idle). Total physical CPU consumption will never exceed 200%.
The selected CPU mode also determines how many resources the VM consumes from your global account limit.
Limits (Default)
To protect new accounts from uncontrolled expenses, default starting limits are in place. If your business needs more resources, please send a request to our support team.
Account Limits
| Resource | Default Limit |
|---|---|
| Projects within one zone | 5 |
| Total vCPU budget on account | 16 (in Performance mode equivalent) |
| Maximum vCPUs for a single VM | 16 |
The vCPU budget is shared across all projects of the account and is calculated based on mode weights:
| CPU Mode | vCPU Weight |
|---|---|
| Performance | 1 |
| Eco | 0.5 |
| Slim | 0.25 |
Example of using a 16 vCPU budget: You can create 16 vCPUs in Performance mode, 32 vCPUs in Eco mode, 64 vCPUs in Slim mode, or any other combination within the budget. The absolute number of cores on a single VM is limited to 16.
Project Limits
| Resource | Default Limit |
|---|---|
| Private networks (VLAN) | 1 |
| Automated backup jobs | 1 |
| Total RAM for all VMs | Account vCPU budget × 6 GiB (default 96 GiB) |
| Total system disks (NVMe) for all VMs | Account vCPU budget × 100 GiB (default 1600 GiB) |
Virtual Machine (VM) Limits
| Resource | Limits and Steps |
|---|---|
| vCPU Count | From 2 to limit (increases in steps of 2) |
| Operational Memory (RAM) | From vCPU × 1 to vCPU × 6 GiB |
| System Disk | From vCPU × 10 to vCPU × 100 GiB (in steps of ×10) |
| User Snapshots | 1 at a time per VM |
| Private Network Interfaces (LAN) | Up to 8 interfaces (each requires a created private network) |
| SSH Keys at Creation | Up to 5 keys |
Note: Decreasing VM configuration (vCPU, RAM, or switching to a lower CPU mode) is allowed no more than once a day per machine. Lowering vCPU and RAM requires a mandatory stop of the server. For more details, see the Resize VM section.
Network Limits and Rules
| Feature | Limit or Rule |
|---|---|
| Public IPv4 | Reverse DNS (PTR record) can be easily changed directly in the portal. |
| IPv6 | Planned for implementation. |
| Private Networks | Default 1 per project (only IPv4 addressing is supported). |
| External VLAN | Connection interface is available in the UI, but support assistance is required for configuration. |
| WAN Bandwidth | 100 / 200 / 300 / 400 Mbps for VMs with 2–7 / 8–15 / 16–23 / 24+ vCPUs respectively. |
| LAN Bandwidth | 2 / 3 / 4 / 5 Gbps for the same vCPU levels (exact metrics are specified in the VM creation form). |
| VM Firewall | Filters public WAN interface only. Subnets (CIDR) up to /26 are allowed in rules. |
Next steps
- Platform capabilities — detailed overview of cloud architecture and hardware.
- Getting started — step-by-step launch of your first VM.
- Private network — local traffic isolation.