Move the cloud, not the code: a twin the application cannot tell from the real service

Workloads stay on hyperscalers because moving means changing code: every call to S3, EC2 and IAM is written into applications that work today and nobody wants to touch. So the requirement is that the application must not know it has moved. The same calls land on a twin, an open source interface to a real system valued for one thing, that the client cannot tell the difference, and the twin decides where the bytes go: real S3, an sgit vault, a European operator's data centre, a laptop. Switching a mock costs a code path; switching a twin costs an endpoint, so migration becomes a configuration decision rather than a project, and projects get cancelled. The S3 twin exists as open source; EC2 and IAM do not yet.

Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).

Note. Dated 12 October 2026, from a digital sovereignty event; the chief executive is not named and did not review it. AWS's European Sovereign Cloud went live on 15 January 2026, a separate cloud with its first region in Brandenburg, operated by EU residents; the article's reading: 'Sovereignty that depends on one company's API is sovereignty by permission.' None of it works if the twin layer is closed: swap one vendor's API for another vendor's proprietary wrapper and the lock-in has moved, not gone.

Where it comes from

Move the cloud, not the code Why workloads do not move; The criterion: the code must not know; This is not theoretical: the S3 twin (newsroom)

What it answers in the 2018 book

AWS answered outline, MVP for Gen Z Dev
Legacy Applications answered outline, Concepts

Where it goes

Chapter Serverless, for real, part Build it without a server (drafting); topic Building blocks: cloud, serverless, free models, git and CI.

Other ideas proposed for the same chapter: Building blocks: cloud as Lego, free models with your own key, git as a standard, The file system is the database: load, extract, transform, save, and keep every intermediate as a file, No server, by design: retire the back end too, and keep only commodity servers, Ship now, and ship your startup serverless: no servers of yours, no database, client side, with privacy by design and control of your agents, What serverless costs when nobody is using it, product by product, 18 October 2026, The name shows the glue: a first version is often a villager's work dressed as a town planner's.

Node idea:the-code-must-not-know-it-moved in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.