Resources and limits
Learn about resource organization in the hostd Public Cloud, CPU classes, and default resource limits.
This page contains detailed information about account and project organization, CPU classes, 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 classes
When creating a virtual machine or resizing it, you choose the CPU class and the number of vCPUs.
The vCPU count is the number of virtual processors visible to the guest operating system. The CPU class sets the relative scheduling priority when VMs compete for CPU time on the host. When capacity is available, every class can use its allocated vCPUs; the class does not impose a fixed percentage cap on their usage.
| CPU class | API slug | Role |
|---|---|---|
| Regular | regular | Default class for typical workloads |
| Light | light | Lower scheduler priority — workers, staging, CI |
Hourly vCPU rates differ by class (Regular, Light). The account vCPU limit counts every class 1:1.
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 (raw vCPUs, all classes) |
| Maximum vCPUs for a single VM | 16 |
There is no separate limit on how many virtual machines you can create — only the vCPU budget and the derived RAM and disk quotas apply.
The vCPU budget is shared across all projects of the account. Every CPU class counts as 1 against the budget.
Example of using a 16 vCPU budget: 16 vCPUs in any mix of Regular and Light. A single VM is still limited to 16 vCPUs.
Project Limits
| Resource | Default Limit |
|---|---|
| Private networks (VLAN) | 1 |
| Automated backup jobs | 1 |
| Total RAM for all VMs | Account vCPU budget × 4 GiB (default 64 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 × 4 GiB |
| System Disk | From vCPU × 10 to vCPU × 100 GiB (in 20 GiB steps) |
| 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: You can lower vCPU, RAM, or CPU class 24 hours after you create a VM or increase those resources. Lowering vCPU and RAM also needs a stopped VM. 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 | Public WAN in IPv6 or IPv4 + IPv6. Hourly public IP billing is IPv4-only. |
| 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 (IPv4) or /64 (IPv6) are allowed in rules. |