Cloud Engines are configurable, application-specific execution environments built on the Internet Computer.
Each Cloud Engine corresponds to a private subnet assembled and configured under the authority of the Network Nervous System, or NNS, $ICP‘s autonomous on-chain governance system. They allow enterprises and developers to deploy workloads with customized security, performance, and resilience characteristics, while preserving the Internet Computer’s core properties of decentralization, tamperproof operation, verifiability, and fault tolerance.
Why Cloud Engines Matter Right Now
Global cloud infrastructure spending reached $102.6 billion in Q3 2025, a 25% increase year over year, according to research firm Omdia, driven by rising enterprise demand for scalable compute and storage and strong market interest in artificial intelligence. Within this environment, centralized cloud providers dominate, but dependence on them introduces regulatory, security, and trust concerns for privacy-sensitive and blockchain-native applications.
By keeping computation and data fully on-chain, the Internet Computer aims to offer a sovereign cloud environment that addresses these concerns directly. DFINITY founder Dominic Williams formally introduced Cloud Engines as the centerpiece of Internet Computer 2.0 in November 2025.
The Mission 70 whitepaper, co-authored by Williams and DFINITY’s Björn Assmann and released on January 13, 2026, then laid out the economic case for Cloud Engines, specifically how they connect enterprise cloud usage to $ICP‘s tokenomics through a deflationary payment model.
How Does the Cloud Engine Model Work?
The setup is modeled on how the internet itself scaled during the 1990s ISP boom. According to the Mission 70 whitepaper, associations of independent node providers can offer enterprise customers a straightforward way to create Cloud Engines running over their nodes.
Node providers invest in their own hardware and hosting, then receive revenue from the Cloud Engines running on their nodes, with 80% going to the providers and 20% used by the network to buy and burn $ICP tokens.
The NNS Keeps the Network Honest
Node configuration is not open to arbitrary choices. The NNS enforces deterministic decentralization rules, requiring that nodes in any given engine are run by independent entities, from separate data centers, with different operators, across different geographies. This ensures Cloud Engines retain the tamperproof properties of the broader Internet Computer network, even when built on enterprise-specific infrastructure.
Sovereign or Virtualized: Both Are Supported
According to the Mission 70 whitepaper, node providers will be able to offer two types of infrastructure. The first is sovereign nodes, physical machines that providers own and operate themselves. The second is virtualized nodes running on traditional cloud infrastructure such as AWS or Google Cloud. Because a Cloud Engine is designed to span multiple nodes across providers, it will continue functioning normally even if one underlying cloud platform suffers an outage.
The First Cloud Engine Deployment
The concept moved into practice at the World Computer Day event in Davos on January 20, 2026, when Williams introduced Swiss Cloud Engines. The Swiss Subnet features 13 independent node providers based in Switzerland and Liechtenstein, with all data storage and processing kept within Swiss borders to support compliance with local regulations such as GDPR. The subnet is designed to serve banks, hospitals, government bodies, and enterprises requiring verifiable data sovereignty.
On May 10, 2026, as part of Internet Computer’s fifth birthday, DFINITY plans to demo Cloud Engines live, including agentic builds and AI nodes, according to the project’s announcement on X.
How Cloud Engines Tie Into $ICP Tokenomics
Cloud Engines and Caffeine.ai are the two demand-side drivers of Mission 70, which targets a 70% reduction in $ICP inflation by the end of 2026. Supply-side measures alone reduce annual $ICP minting from 9.72% in January 2026 to 5.42% by January 2027, a 44% reduction.
Achieving the full 70% target also requires increasing the network’s cycle burn rate from 0.05 XDR per second to 0.77 XDR per second through demand acceleration. Every $ICP token converted into cycles to power a Cloud Engine is burned, directly linking enterprise cloud usage to token supply reduction.
Conclusion
Internet Computer Cloud Engines give enterprises and developers a way to run sovereign, tamperproof workloads on configurable private subnets, governed by the NNS and backed by independent node providers. The Swiss Subnet, launched at Davos in January 2026 with 13 independent node providers, is the first national subnet built to host Swiss Cloud Engines, with the Cloud Engine rental service announced as the next step in that rollout. Cloud Engines, alongside Caffeine.ai, form the two key demand-side mechanisms of Mission 70, which sets precise numeric targets for $ICP burn and inflation reduction. Together they connect $ICP‘s technical architecture directly to its economic model.
- Research paper by Dominic Williams and Björn Assmann: Mission 70 whitepaper (v1.1.1, February 6, 2026):
- Medium post by Dominic Williams: Mission 70 whitepaper (v1.1.1, February 6, 2026):
- Report by Cryptonews: Internet Computer Launches First National Subnet in Switzerland at Davos 2026
- Omdia Q3 2025 cloud spending research: Omdia: Global cloud infrastructure spending hits $102.6 billion, up 25% in Q3 2025
- DFINITY’s X announcement: May 10, 2026 demo
