ZCP in Q3 2026: What Shipped, and What Is in Progress

This post covers ZCP releases from Q3 and an October platform update. If you run backups or managed Kubernetes, review the billing changes below.

What shipped in Q3

• Intel Xeon compute in Montréal. General-purpose ci2 and memory-optimized cim2 plans, custom Intel configurations, and Intel-backed Kubernetes capacity joined AMD in YUL-1 on August 16.
• YUL local storage tiers. ZCP added host-local NVMe and SATA SSD root and data volumes on August 22, for workloads with an application-level recovery design.
• Postpaid billing. Since September 1, new accounts choose Prepaid or Postpaid at signup. How each mode works.
• Kubernetes 1.37. Available for new managed clusters in both regions since September 6, with refreshed 1.36, 1.35, and 1.34 patch releases. Read the release notes.
• Eight subnets per VPC. The per-VPC subnet limit moved from three to eight on September 7, and existing VPCs picked up the new limit with no action needed.
• Object storage reachable from new VPCs. Workloads in newly created VPCs resolve the object-storage endpoint.
• CLI v0.0.28 and v0.0.29, and Terraform provider v0.2.0. Credentials redacted from debug output, working backup commands, complete volume listings, and object-storage bucket configuration as code. The detail is here.

October platform update

Backups on your terms

You will be able to create, edit, pause, resume, and run backup schedules on demand. Each schedule will carry its own timezone and retention policy, so backup timing and retention can match the workload.

Activity logs will record schedule creation and updates, runs, failures, and retention cleanup.

Backup billing is moving from a charge for each schedule to the storage your backups consume. Each backup subscription ends when its backup is deleted, whether you delete it or retention does.

Kubernetes billing follows the resources you run

The Kubernetes billing update will charge for the cloud resources a cluster provisions: control-plane and worker virtual machines, block storage, networks, public IP addresses, and load balancers. The cluster itself will not carry a separate charge.

Your invoice will list each provisioned resource separately. A three-node cluster with two load balancers will show those resources as separate line items.

Cluster configurations will also gain separate CPU and memory sizing for control-plane and worker nodes. This work does not include CSI integration.

The Store becomes searchable

The redesigned Store will bring product search, category counts, and product cards. Open a product to see vendor information and contract details. Choose an available billing cycle and quantity, then see the total price before you buy.

Marketplace setup details arrive by email

After a Marketplace application VM deploys successfully, ZCP will email you the application credentials and any configuration values you supplied during setup. The details needed for a first sign-in will arrive with the deployment.

Treat that email as sensitive because it contains access details. Change the supplied credentials at first sign-in where the application supports it. Deleting the email does not revoke those credentials.

Smaller changes in the same release

The platform update includes low-credit notifications, VM password-management changes, and rate limits for tickets, feedback, login, and password-reset requests. API token expiration settings are also included.

Object-storage access keys support rotation. Each object store has one or two active keys. The last active key cannot be revoked. A new secret is visible for five minutes after key creation, then hidden while the key remains active. Revoking a key invalidates it in both the backing store and the control plane. Keep two active keys during rotation, move your applications to the new key, confirm they work, then revoke the old key.

CLI v0.0.30

CLI v0.0.30 adds custom VM configuration flags, load-balancer rule listing, and object-storage access-key rotation.

If you already run backups or Kubernetes clusters

ZCP is migrating existing backup billing to the storage-based model. Existing Kubernetes billing configurations need an update before the resource-based model applies.

Your costs will depend on the backup storage and retention you use, and on the resources in your clusters. Review backup retention and cluster sizing before the billing migration reaches your account.

The Q3 2026 platform update release notes will cover the implementation details for existing schedules and clusters when they are ready.

Where to follow the rest

The roadmap tracks each of these items through building, preview, and available, alongside the Q4 work on the ZCP control plane, PaaS runtime, and platform observability. The changelog records every release as it ships.

Questions about what this means for your account? Talk to our team.