Whitepaper · 10 pages · October 2026
Compute and Storage, Priced Separately
Why every ZCP plan is now CPU and memory only, and how the root disk is sized and billed by the GB
ZCP Pricing V2 explained: compute-only plans, a root disk you size in GB, six storage tiers, a worked price example, how to size a disk, and what stays the same for existing servers.
- Pricing
- Compute
- Block Storage
- Root Disk
- Migration
- Billing Lines
- 2
- Compute and root disk, separate
- Storage Tiers
- 6
- Priced per GB per month
- Same Total
- $36
- Same root size on the default tier
- Forced Changes
- 0
- Existing servers keep plan and price
Inside
What the paper covers
The Problem with Bundles
Unused disk, plan changes to grow, and CPU that forces storage
The Hyperscaler Model
Fixed compute sizes and a root disk sized and billed by the GB
Tiers and Billing Lines
Six storage tiers and four separate lines on Review and Deploy
A Worked Example
One plan, three disk sizes and four tiers, with assumptions and the date
Sizing a Root Disk
Template minimum, growth, and which tier for which workload
Existing Customers
What stays the same, what to check, and what is coming next
Steps
The migration, step by step
- 01List your serversStep 1
- 02Pick a tier per roleStep 2
- 03Create with an explicit root sizeStep 3
- 04Add the disk line to the forecastStep 4
- 05Watch usage and growStep 5
Get the full paper
10 pages, PDF, 1.2 MB. Your first hour with our engineers is free.
More whitepapers
See every whitepaper
Object Storage by Industry10 pages · September 2026
Building and Operating a Private Cloud on Apache CloudStack and Ceph10 pages · September 2026
Running Authoritative DNS with PowerDNS and dnsdist10 pages · September 2026
Configuration Management at Platform Scale with Ansible10 pages · September 2026
Enterprise EKS Auto Mode Migration Roadmap10 pages · September 2026
CI/CD Pipelines for Infrastructure as Code10 pages · September 2026
