Public Cloud: the end of all-inclusive pricing

Our Public Cloud instances have always included local storage and a public IPv4 address in their price. On October 1, 2026, these two resources will become separate billing lines. The price of the virtual machine, the compute, does not change. 

With memory and storage costs rising, our objective is to limit the impact on you. This involves the ability to choose what you need and in what quantity. 

Even at the same configuration, your bill will increase. But you potentially minimize the increase if you: release an unused IP address, choose a flex instance that only includes 50 GB of local disk and add remote Block Storage.  

This article reviews what is changing and why. For the details of the price changes, instance by instance, go to the second blog. 

Why we are evolving our model 

There are two reasons for this evolution. 

Being comparable 

From the beginning, our instances have included resources that our competitors charge for separately: local storage and the public IPv4 address. This choice was aimed at simplicity. It ends up working against us. 

When a customer puts two prices side by side, they are comparing two numbers, not two scopes. Ours appears higher because it contains more, and our real advantage becomes invisible when it should be obvious. 

By billing local storage and the IP address separately, we are aligning our model with that of the market. Each line becomes readable and comparison becomes possible, line by line, with an identical scope. It is a question of transparency, but also of fairness: we want our positioning to be verifiable on an invoice, not to need explaining every time. 

Maintaining the price of computing 

The surge in artificial intelligence has led to huge demand for graphics processors, which are known for their high memory requirements. The top three global manufacturers are now focusing their factory production on high-bandwidth memory (HBM), and this has impacted standard DDR5, which is used in our servers. 

As we design and assemble our own servers, we buy these components directly, without any intermediaries. Memory costs us six times more today than it did a year ago, and storage is following the same trajectory. 

What level of increase are we talking about? 

Between 1.4% and 21.9% depending on the services you have, with unchanged storage capacity. 

The difference between these two figures is easily explained. Local storage is capped at 400 GB and the IP address costs a fixed amount, so the increase is almost the same in dollars for all instances. With a smaller instance, this amount weighs heavily. On a larger one, it becomes marginal. The price breakdown, instance by instance, is in the second blog. 

We chose this path rather than a general increase in the price of instances, because it makes each item visible and actionable: an IP address that is not being used can be released, an oversized volume can be reduced. 

Local storage becomes its own storage class 

On generation 3 instances, the B3, C3 and R3 ranges, local storage is no longer included in the instance price. It is charged at $0.0001721 per GB per hour, or approximately $0.125633 per month, or $125 per TB per month. On all previous ranges (B2, C2, R2 and earlier), it remains included. 

By removing local storage from the instance price, this local NVMe disk does not just become an extra line on an invoice: it becomes a Storage class, the Low Latency Local Storage class, backed directly by the NVMe disk of the server hosting your instance. It is available on all our generation 3 instances and is particularly sought after for database storage. 

This class is in addition to our existing Block Storage classes, those backed by our distributed storage and designed for high availability, which remain unchanged. It is up to you to choose according to your load: the lowest latency with local NVMe, availability with distributed storage, or both at the same time on the same instance. 

Today, the capacity remains fixed by the template, exactly as in our current catalog (50, 100, 200 or 400 GB depending on the instance). We are working on an evolution that will allow this storage to be sized independently of the instance size, and even to start an instance without a local disk directly on the classic and high speed Block Storage classes. No date to announce for the moment, but this is the direction we are taking. 

Managed Kubernetes: node pools built on b3, c3 and r3 flavors follow the same billing change. 

The prices of our other storage solutions, high availability Block Storage, Object Storage and File Storage, remain unchanged. 

The public IPv4 address becomes optional 

IPv4 addresses are now charged at the rate already applied to our Floating IPs: $0.0032 per hour, or approximately $2.33 per month. Billing is per second, on all Public Cloud Virtual Machine ranges as well as on the Gateway, including when the address is not attached to an instance. 

A new dedicated section of the Manager allows you to create, attach and release your addresses as soon as you no longer have a use for them. 

If you wish to limit the number of charged public IPv4 addresses, a 100% private network architecture remains the most efficient solution: it pools the outgoing traffic of your instances behind a single IPv4 address, that of your Gateway, rather than one per instance. Find out how to configure a gateway on your private network. 

Savings Plans are also evolving 

Here too, it is a matter of becoming comparable. The market generally offers two commitment periods: 1 year and 3 years. We used to offer five, from 1 to 36 months. This was intended to provide flexibility, but it produced price lists that no one could compare with those of other providers. Effective immediately, the new 12 and 36-month discounts apply to any new Savings Plan, and the 1, 6 and 24-month commitment periods stop being available for new subscriptions. From October 1, 2026, local storage and the public IPv4 address are billed separately, for new and existing subscriptions. 

What’s not changing 

The hourly price of the instances. The performance of our network. Anti-DDoS protection included. Outbound traffic included.  

Since our last announcement, we have deployed per-second billing and made Public Cloud File Storage generally available.  

To find out more: the detailed pricing, instance by instance, and the precise impact on your invoice, can be found in Public Cloud, our prices and packaging are changing on October 1, 2026.