Skip to content
Portal

Platform Overview

Pilvio.pro is a cloud infrastructure platform that provides virtual compute, networking, storage, and container services through an easy-to-use web portal and REST API.

This page gives you a high-level understanding of the resources available to you, how they fit together, and how billing works.

What Pilvio.pro Provides

The platform lets you provision and manage:

  • Virtual Machines (VMs) — Run Linux or Windows workloads in isolated virtual environments.
  • Cloudspaces — Isolated virtual networks that contain your VMs. A cloudspace can be public (connected to an external network) or private (fully isolated). "Public" means connected to an external network — that network may be the internet or a private network such as your company network; an internet connection is not required.
  • Object Storage (Objectspaces) — S3-compatible blob storage for backups, files, disk images, and application data.
  • Containerspaces — Managed Kubernetes clusters powered by Rancher, for containerised workloads.
  • Virtual Desktop Infrastructure (VDI) — Windows desktop environments delivered to end users via RDP.
  • Networking — Port forwards, load balancers, reverse proxies, DNS, and VPN connections between cloudspaces.

How the Portal Is Organised

The portal is organised around a few key concepts:

Locations

A location is a data centre where your resources are hosted. When you create a cloudspace, VM, or storage volume, you choose which location to use. Each location has its own available image catalogue, external networks, storage classes, and pricing.

Organisations and Roles

You belong to an organisation — the team or company account that owns the cloud resources. Pilvio.pro has three audiences:

  • Cloud admin — the platform operator, who sees the Cloud admin menu group.
  • Admin — the owner or member of a customer organisation, who sees the Admin menu group, Software Licenses and Containerspaces.
  • Role user — a user with limited access, granted through roles. See Roles & Permissions.

All of them use the same portal, and the menu differs per audience. See Roles at a Glance for who is who.

Resources Inside Cloudspaces

Your compute, storage, and networking resources live inside cloudspaces. Each cloudspace is a private virtual network:

  • VMs in the same cloudspace can communicate with each other on a private subnet.
  • A cloudspace can be connected to an external network (public) — the internet or a private/company network — or kept fully isolated (private).
  • Multiple cloudspaces in the same location can be connected to each other via VPN tunnels.

The Resource Model

Virtual Machines

Each VM runs inside a cloudspace and includes: - An OS image (Linux or Windows) from your location's catalogue. - One or more network interfaces — private by default, public IP attachable. - A boot disk and optionally data disks. - Optional vGPUs for GPU-accelerated workloads.

Objectspaces

An objectspace provides S3-compatible object storage. You can attach it to a cloudspace so VMs in that cloudspace have low-latency access, or use it independently.

Containerspaces

A containerspace is a managed Kubernetes cluster. The portal handles the cluster infrastructure — you deploy and manage your workloads through the Pilvio.pro portal without operating your own Kubernetes control plane.

VDI

VDI (Virtual Desktop Infrastructure) delivers Windows desktop environments to end users. Administrators define a VDI profile (VM template, pool size, connection mode) and end users connect via the VDI Agent client.

Billing Model

Pilvio.pro bills on a resource allocation and consumption basis:

  • Allocation-based units are billed for the resources you reserve, regardless of actual usage (for example a 10 GiB disk, or a VM's memory and vCPUs).
  • Consumption-based units are billed for what you actually use (for example network traffic and object storage).

All resources are metered hourly and billed monthly. The table shows which units each resource of the Resource Model consumes. For the definition of every unit, see Billing & Resource Units.

Resource Billing units
Virtual machine VCU (virtual CPUs) and MU (memory); WU in addition if the VM runs Windows
Disk SU or FSU, depending on the storage class; TU for IOPS
Objectspace OU
Network traffic NU (traffic from and towards the virtual firewall or the external IP address of your VMs)
Public IP address PIU
vGPU VGU

For example, a Windows VM with 2 unpinned vCPUs, 4096 MB of memory and 100 GiB of disk consumes 2 VCU, 4 MU, 1 WU and 0.1 SU over a month. See the worked example in Billing & Resource Units.

Unit prices are set per location. They are shown in the price table on the Locations page (columns SU, OU, MU, VCU, TU, WU, NU, PIU, VGU and FSU) and in the location step of the create-cloudspace wizard. Costs are also shown in Spending Analysis.

Units and what they measure

Each resource you run consumes one or more billing units. The same unit always measures the same thing, so you can read a price or a consumption figure and know which resource it refers to:

Unit Measures Billed as
VCU Virtual CPUs (vCPUs) Allocation
MU Memory (RAM) Allocation
SU Storage (disk), scaled by the storage class's SU multiplier Allocation
FSU Flash / physical storage Allocation
VGU Virtual GPU (vGPU) Allocation
TU Disk IOPS Allocation
PIU Public IP address Allocation
WU Windows licensing on a VM Allocation
NU Network traffic from and towards the virtual firewall or the external IP address of your VMs Consumption
OU Object storage usage Consumption

Allocation units are charged for what you reserve; consumption units are charged for what you actually use. A single VM typically bills several units at once — for example its vCPUs (VCU), memory (MU), disks (SU) and, if Windows, licensing (WU). The full definitions, including the storage-class multiplier, are in Billing & Resource Units.