ICP Cloud Engines expand as sovereign cloud infrastructure goes live
The Internet Computer’s Cloud Engines are expanding as the network moves further into dedicated cloud infrastructure, offering organisations a way to run applications on replicated compute environments while retaining greater control over where and how that infrastructure operates.
The latest update reports 26 Cloud Engines operating across seven countries, supported by 107 node machines, 10 node providers and 17 data centres.
These Cloud Engines operate separately from the public Internet Computer mainnet. Each provides its owner with a dedicated replicated execution environment, while allowing control over node providers, locations and machine classes.
The model also allows infrastructure to be adjusted as requirements change. Nodes can be added, removed or relocated without interrupting the canisters running on the Cloud Engine, according to the update.
The development comes as ICP continues to distinguish Cloud Engines from its public subnet infrastructure. The ICP Dashboard introduced a dedicated Cloud Engines section in August, allowing users to view engine counts, data centres, node providers, node machines and node classes. It also separates Cloud Engine figures from the public mainnet statistics.
The wider public network remains considerably larger, with the update reporting 42 subnets, 618 nodes, 72 node providers and 92 data centres spread across 33 countries.
The difference between the two models is largely about control and deployment. Public subnets form part of the shared ICP network, while a Cloud Engine gives its owner a dedicated environment with greater control over the underlying infrastructure.
For organisations considering on-chain applications, that distinction could matter where infrastructure location, hardware configuration and operational control are important requirements. It also provides a model for deploying applications while keeping execution within the replicated infrastructure of the Internet Computer.
DFINITY describes ICP as a cloud platform based on independently operated compute nodes, with applications hosted directly on the network.
The expansion of Cloud Engines points to an effort to position ICP as infrastructure for applications that need dedicated computing environments alongside the characteristics of an on-chain platform.
With Cloud Engine infrastructure now being tracked separately on the public dashboard, its growth can also be followed independently from the wider public mainnet.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life