DFINITY Foundation

Cloud engines are designed to remove the operational burden from running infrastructure. The setup process follows three steps. First, select your nodes. Choose hardware type, operator, and geography. Standard or high-performance. Any continent, any compliance zone. A cloud engine runs on a minimum of four nodes and scales to one hundred. Second, fund your engine. Pay in USD. Dollars convert to cycles via the Network Nervous System. Pay as you go or on a schedule. Infrastructure overhead is zero. Third, deploy your apps. Install from App Center or deploy direct. Connect your AI agent. Push changes from the tools you already use. There are no servers to manage. During our recent Cloud Engine demo, one node was intentionally taken offline. Apps kept running without interruption. No alerts, no downtime. More at opencloud.org

✨ We are delighted to welcome Pierre Samaties to #ScalingBlockchainForPublicGood at Sciences Po.    Pierre Samaties is Chief Business Officer at DFINITY Foundation, where he oversees strategy, products, ventures and business activities around the Internet Computer Protocol. He brings extensive experience across digital infrastructure and emerging technology implementation.    🌟 Before joining DFINITY, Pierre founded and led Roland Berger’s global Digital Assets and Web3 practice, advising governments and technology enterprises. Earlier, he served as Managing Partner and CEO at RWE and innogy Consulting GmbH in the Middle East, working across energy-sector strategy, transformation and venture investment.    Pierre’s work also connects to practical applications of blockchain for development and sustainability. During his time at Roland Berger, he was involved in the Voluntary Recycling Credits initiative, developed with DFINITY to support transparent and auditable recycling incentives through blockchain technology.    💫 At Sciences Po, Pierre will contribute an enterprise and implementation perspective to this discussion, as DFINITY Foundation works with UNDP to develop and test digital credentials infrastructure for the Universal Trusted Credentials prototype in Cambodia, aimed at strengthening digital trust and access to finance for MSMEs.   Register and join us in Paris 👇  https://luma.com/5dx11z7w    #Blockchain #PublicSectorInnovation #GovTech 

Most apps run their frontend on centralized cloud. Cloud Engines are different. They run on Internet Computer hardware, or on AWS and Google. Regardless of where the nodes are, the properties don't change: tamperproof execution, always-on uptime, and freedom from vendor lock-in. No security teams. No sysadmin teams. Software running on a mathematical network, the way it should be. Three promises. All kept.

✨ Governments and public institutions need to assess where blockchain can address real public challenges and what capabilities are needed to implement it responsibly. To achieve this, the adoption of such innovative technology must be approached judiciously.    On 4 June at Sciences Po, #ScalingBlockchainForPublicGood will explore how governments, institutions, and blockchain ecosystem actors can collaborate in the development of blockchain-enabled public services.    🌟 Session 1: Blockchain Adoption in Practice: Aligning Governments, Industry and Institutions 🌟    The session will feature the launch of the #GovernmentBlockchainAcademy by Burcu Mavis, followed by a keynote intervention from Nadia Filali of Groupe Caisse des Dépôts.    Taking part in the panel discussion will be:  🔹 Dr Maria Papadaki, Dubai Blockchain Center  🔹 Xavier Juredieu, EUROPEUM - EDIC  🔹 Alex Maaza, Cardano Foundation  🔹 Nikhil Vadgama, Exponential Science 🔹 Pierre Samaties, DFINITY Foundation    Request your place and join the conversation in Paris 👇  https://luma.com/5dx11z7w

When blockchain reaches internet scale, it stops competing with crypto, and starts competing with global infrastructure. Pakistan Digital Authority DFINITY Foundation

AI can write and deploy code at the speed of conversation. The problem is that production cloud wasn't built for that. On traditional infrastructure, you need a security team to patch holes, a sysadmin team to keep things running, and a rollback plan for every update. That's not workable when AI is the developer. Cloud Engines remove all three requirements. No infrastructure hacks are possible. Apps are guaranteed to run. And Motoko, the first programming language built specifically for AI, catches lossy updates before they're applied. The result: AI that deploys to production safely, without a security team or sysadmin in the loop.

89%. That's the increase in attacks by AI-enabled adversaries in 2025, taken from CrowdStrike's 2026 Global Threat Report. The fastest recorded eCrime breakout time this year: 27 seconds. What used to take the world's best hackers days now takes an hour. What took an hour now takes minutes. AI democratized the attack. A criminal gang now operates at the level of a small nation state. Volume. Speed. Autonomy. The response has been more monitoring. More detection. More patching. That's not wrong. But it doesn't scale with the threat. When the attack surface grows 89% in a year, defense needs to be in the architecture - not the maintenance plan.

Not a prototype. Production-grade SaaS, built without a single line of human code. As Cloud Engines take off, there's an emerging market for Internet Computer apps. AI is building them now. Tamperproof infrastructure removes the security ceiling. Always-on guarantees remove the reliability ceiling. That's the platform. AI builds. The network enforces safety.

Standard cloud infrastructure has three points of failure. The OS. The network perimeter. The team managing both. Cloud engines remove all three. A cloud engine is a sovereign frontier cloud. Tamperproof execution, fault-tolerant by design, and entirely under your control. Tamperproof: no vulnerable OS, no credentials to steal. Software runs inside a mathematically secure network protocol. Fault-tolerant: computation replicates symmetrically across nodes. If a node goes offline or is compromised, your app keeps running. Sovereign: you choose the hardware, the operators, the geography. Your apps do not notice the substrate moving beneath them. opencloud.org

$23.1 billion. That's what Europe will spend on sovereign cloud infrastructure by 2027. Tripling in two years. Gartner's forecast. A trend already in motion. The market has read the room. But most of that spend goes to the same three companies. AWS. Azure. Google. Same infrastructure. Same jurisdiction. Same CLOUD Act exposure. Different contract. You can spend $23 billion on sovereignty and still have none. The distinction isn't the budget. It's the architecture. Who chooses the nodes? Who sets the governance? Whose law applies when the request comes in? Sovereignty isn't a feature you can licence from the same architecture you're trying to move beyond.