Cloud exit: repatriating from the public cloud
A cloud exit is the controlled move of applications, data and workloads out of the US public cloud to a Dutch or European environment, or to your own infrastructure. Appfront carries out that exit: in phases, application by application, and always with a fallback option. We handle the application and data migration ourselves; for data centres, IaaS and colocation we work with specialised Dutch infrastructure partners. Still unsure what exactly needs to move? Then start with the sovereignty assessment.
What is a cloud exit?
A cloud exit, also known as repatriation, is the planned move of applications, data and workloads out of a US hyperscaler's public cloud and into an environment you choose yourself: a Dutch or European cloud provider, a private cloud or your own infrastructure. What sets it apart from an ordinary migration is the direction and the reason: you are leaving deliberately and want the exit to be controlled, with no disruption to your services and no data loss.
The trigger is often legal. US cloud providers fall under the US CLOUD Act and FISA, even when their servers are in the EU: jurisdiction follows the parent company, not the server location. For organisations with sensitive or regulated data, that is increasingly hard to justify under the GDPR, NIS2 (the Dutch Cybersecurity Act enters into force on 15 August 2026) and sector standards such as NEN 7510 in healthcare and the BIO in government.
Cost control and obligations also play a part. Public cloud costs grow with usage and are hard to predict; for stable workloads, your own or a European environment often gives you more control over the cost profile. And increasingly, a prepared exit is simply mandatory: the revised Dutch central government cloud policy of 3 July 2026 requires government organisations to store and process data within the EEA, carry out a mandatory risk assessment and maintain an annually reviewed exit plan, and DORA requires financial institutions to have exit strategies for critical ICT services. If you have such a plan, you also want to be able to execute it. This service is about that execution; for the analysis beforehand, there is the sovereignty assessment.
How we approach this
What we build and deliver
Who it's for
The revised Dutch central government cloud policy requires storage and processing within the EEA, advises against public cloud for email and document management, and demands an exit plan that is tested annually. We carry out that exit plan.
Organisations that process medical data under NEN 7510 and no longer want to host it with a US hyperscaler.
DORA has applied since 17 January 2025 and requires exit strategies for critical ICT services. We make that strategy executable and carry it out.
Companies with stable workloads for which the flexibility of the hyperscaler adds little, but whose bills keep growing with usage.
Technology and approach
We repatriate to open, portable technology. We replace cloud-native building blocks with open alternatives, so your applications run on any environment and a future move no longer requires a rebuild. For the landing infrastructure we work with specialised Dutch partners; we retain control of architecture, migration and applications.
Why Appfront
Appfront is an independent software and app agency. We do not sell hosting ourselves and have no interest in where your workloads end up, so our advice on the landing environment is unbiased. We combine migration experience with the engineering capacity to adapt or rebuild applications where the exit requires it.
- Phased approach with a fallback option per application
- Application and data migration in our own hands, infrastructure via Dutch partners
- Experience replacing cloud-native services with open alternatives
- Management and further development after the exit
Related services
Start with the sovereignty assessment if you do not yet have an exit plan. Also see migrating applications to a sovereign cloud, migrating from AWS to a sovereign cloud and building a sovereign cloud.
If your exit also raises the question of who is entitled to the data your systems and equipment produce, that touches on the European Data Act: it obliges providers to make switching possible without unnecessary barriers and gives users the right to their own product data.
Frequently asked questions
Get started with your cloud exit
Do you have an exit plan that needs to be executed, or do you want to know what repatriation would look like for your applications? We're happy to think along with you, independently, about a controlled route out of the public cloud.