Local storage remains included on all previous ranges (B2, C2, R2, and earlier).

Local storage sizing

Today, the local storage capacity remains fixed by instance type, exactly as in our current catalog: a b3-64 comes with 400 GB, regardless of your actual usage. We are working on an evolution that will allow this capacity to be chosen independently of the instance type, and even to start without a local disk for use cases that do not require one.

• Flex instances already partially meet this need. Regardless of the instance type, their local disk is fixed at 50 GB: a b3-64 flex therefore includes 50 GB instead of 400 GB. You can therefore resize the instance from one type to another, upwards or downwards, without changing the local disk, and you only pay for these 50 GB regardless of the instance size.
• Managed Kubernetes: node pools built on b3, c3 and r3 flavors follow the same change.

Savings Plans

The new price list applies effective immediately.

• Subscription to 1, 6 and 24-month commitment periods is no longer available.
• The discount only applies to compute. Local storage and the IPv4 address are invoiced, excluding discount, at their full price.
• If you already hold a Savings Plan, your compute price and discount rate remain guaranteed until the end of your commitment. From October 1, 2026, Local storage and the Public IPv4 address are billed separately on top of your plan, at the published catalog rate, and are not covered by your discount. The details of the two schemes are explained in the first blog.

The schedule

What this looks like, instance by instance

Amounts based on 730 hours per month, excluding tax without commitment, for the local storage capacity currently attached to each instance type, as reflected in the "Local storage" column below.

The increase is identical in dollars for all instances with the same storage capacity: storage is capped at 400 GB, the IP address costs a fixed amount. It therefore will have a larger impact on small configurations, where these two items represent a significant part of the bill, and much less on large ones.

Four concrete examples

Example 1: Architecture with 3 to 4 front-end servers + 1 database

A classic architecture: three application instances exposed, each with its own IPv4 address, and a database accessible only via a private network.

Packs

Example 2: Infrastructure with gateway and some private instances

A common pattern to limit the impact of the price increase: a single instance faces the Internet (the gateway), the rest of the traffic transits via a private network. Here, the gateway exposes a public IP; ten instances remain entirely private.

Complete pack and the alternative

The leverage: if the ten private instances carried a public IP instead of a gateway, the bill would rise to $1,030.77 instead of $1,019.07. Not assigning IPv4 addresses to instances that do not need them (access only via the gateway or private network) allows you to save approximately $2.33 per month per instance; and to secure your infrastructure by reducing the public exposure of services.

Example 3: The evolution of flex instances

Flex instances have a local disk fixed at 50 GB regardless of the size. Result: the storage line added on October 1, 2026 remains the same in dollars (50 GB + 1 IPv4, i.e. approximately $8.61/month) for all sizes in the same family — unlike standard instances, where the local disk grows with the size. The larger the instance, the less this fixed amount weighs, and the percentage difference narrows much faster than in standard.

Example 4: A C3-8 Savings Plan — 12 months subscribed before the switch (July 1, 2026)

A customer subscribes on July 1, 2026 to a 12-month Savings Plan under the old terms: -35% discount on the instance price, price and rate guaranteed until the end of the commitment, on June 30, 2027. The discount still applies to compute pricing after the price increase on October 1, 2026, but the customer will be responsible for separate local storage and IPv4 payments starting October 1, 2026.