#
Resource Pricing
Kvant resource pricing is based on three independently billed dimensions: compute (CPU), memory (RAM), and persistent storage. Costs are calculated monthly against the requests values defined in each Namespace's ResourceQuota, making billing predictable and directly tied to provisioned capacity rather than variable runtime usage.
#
Pricing Reference
Over-commitment and billing
Over-commitment is permitted (a Namespace's limits may exceed its requests), but billing is always based on requests. Setting conservative requests and higher limits allows workloads to burst without increasing the base monthly cost.
#
Resource Truth Table
The table below defines the behaviour of each resource type across key operational dimensions.
#
Per-Resource Pricing Detail
#
Compute (CPU)
CPU is measured in vCPU cores, where 1 vCPU = 1000 millicores in Kubernetes notation. CPU is a compressible resource: if a pod attempts to use more than its limit, it is throttled rather than terminated. Billing is based on requests.cpu.
#
Memory (RAM)
Memory is measured in GiB. Unlike CPU, memory is non-compressible: if a pod exceeds its memory limit, the kernel terminates it with an OOMKill signal. This makes accurate memory requests particularly important for production workloads. Billing is based on requests.memory.
#
Storage
Persistent storage is provisioned via PersistentVolumeClaims (PVCs) against a configured StorageClass (e.g. Ceph RBD). Storage is billed per GiB at a flat rate and is independent of compute and memory costs, allowing flexible cost modelling for data-heavy workloads.
You buy storage through the portal in 100 GiB increments only: 100 GiB minimum.
#
Example Namespace Cost Calculation
The table below shows a combined monthly cost calculation for a production namespace with typical resource allocations.