Cloud exit scanCLOUD Act exposureExit plan per application

Sovereignty assessment: know where your cloud dependencies are

The sovereignty assessment is the cloud exit scan that every sovereignty strategy starts with. We map all your organisation's cloud and SaaS dependencies, determine each system's exposure under the US CLOUD Act, and deliver a report with a risk classification, an exit plan per application and a migration roadmap. Appfront carries out the scan at application and data level; we map infrastructure alternatives together with specialist Dutch partners.

What is a sovereignty assessment?

A sovereignty assessment is a structured scan of all the cloud and SaaS dependencies in your organisation: hyperscalers such as AWS, Azure and Google Cloud, US SaaS services and the data flows between them. For each system we determine its exposure under the US CLOUD Act, the law that can require US companies to hand over data, even when it is physically stored in a European data centre. That exposure often runs deeper than expected: not only in where you host, but also in the SaaS tools and underlying services your applications rely on.

What's more, the question is no longer optional. The revised Dutch Government Cloud Policy of 3 July 2026 requires central government to store and process data within the EEA, makes a prior risk assessment mandatory and requires an annual exit plan for each public cloud service. Under DORA, which has applied since 17 January 2025, financial institutions must have exit strategies for critical ICT services. And with the Cybersecurity Act, the Dutch implementation of NIS2 that comes into force on 15 August 2026, risk management across the entire digital chain is added to that. The assessment provides exactly the substantiation these rules require: a dependency map, a risk classification and a concrete exit plan per application.

How we approach this

1
Discovery
We map all cloud and SaaS dependencies: hyperscalers, US SaaS, underlying services, integrations and the data flows between them, down to application and data level.
2
Exposure and classification
For each system we determine the CLOUD Act exposure and classify the risk: how sensitive the data is, which legal requirements apply and how easily the service can be replaced.
3
Exit plan per application
For each application we work out a realistic exit scenario: moving to a European alternative, rebuilding, or accepting the risk on a well-founded basis. Practical and executable, not a paper exercise.
4
Report and roadmap
You receive a report with a dependency map, priorities and a migration roadmap. If you want to press on afterwards, we offer cloud migration support from plan to execution.

What we build and deliver

Dependency map
A complete overview of all cloud and SaaS services, per application and per data flow, including the suppliers behind your suppliers.
CLOUD Act exposure per system
For each system you can see whether it falls under US jurisdiction, directly or through underlying services, and what that means for your data.
Risk classification
Prioritisation based on data sensitivity, legal requirements and replaceability, so you know what needs attention first and what can wait.
Exit plan per application
Mandatory every year for central government since the revised Government Cloud Policy, and under DORA for financial institutions. We make it concrete rather than a box-ticking exercise.
Migration roadmap
An executable sequence: which application first, which European alternative fits and which dependencies need to be untangled first.
Compliance review
We test the findings against GDPR, NIS2 and the Cybersecurity Act, DORA, BIO and NEN 7510, depending on your sector.

Who it's for

Central government and public sector

The revised Government Cloud Policy requires a risk assessment and an annual exit plan, advises against using the public cloud for email and document management, and excludes state secrets and base registers from it. The assessment delivers that risk assessment and the exit plans, in line with the BIO.

Financial sector

Since 17 January 2025, DORA has required exit strategies for critical ICT service providers. For each system, we map where you depend on third parties and what an exit looks like in practice.

Healthcare

Organisations that process medical data fall under NEN 7510 and the GDPR. We classify which data is stored where, which suppliers have access to it and where jurisdiction becomes a problem.

NIS2 sectors

From 15 August 2026, the Dutch Cybersecurity Act (Cyberbeveiligingswet) sets requirements for risk management across the digital supply chain. The dependency map shows where that chain is vulnerable and where you need to adjust course.

Technology and approach

A good assessment is more than a questionnaire. We analyse the actual architecture: which services your applications call, where data is stored and processed, and which suppliers sit behind them through subcontractors. Because we build and migrate software ourselves, we also assess what an exit costs technically: which code is tied to proprietary cloud services and what it takes to make it portable. For the infrastructure side, we look at EU-based alternatives; you can find an overview of providers in our guide to the best sovereign cloud providers in the Netherlands.

Application and data inventory
Data flow mapping
CLOUD Act assessment
Risk classification
Exit plan per application
Migration roadmap
EU-based alternatives
Open standards

Why Appfront

Appfront is an independent software and app agency. We don't sell hosting or data centre services, so the outcome of the assessment isn't steered by a platform of our own. We scan at the level where the real dependencies sit: the applications and the data. And because we build and migrate ourselves, it doesn't stop at a report: the same people who run the scan can carry out the rebuild or migration afterwards.

  • Independent of hosting providers and hyperscalers
  • Scan at application and data level, not just an infrastructure checklist
  • Exit plan per application that meets Dutch central government cloud policy (Rijkscloudbeleid) and DORA requirements
  • Infrastructure alternatives mapped out together with Dutch infrastructure partners

Related services

After the assessment, we can move straight on: see cloud migration support for the journey from plan to execution, migrating applications to a sovereign cloud for the migration itself and building a sovereign cloud for new builds on EU infrastructure. Looking for a provider? Read the best sovereign cloud providers in the Netherlands.

Frequently asked questions

What is a sovereignty assessment?
A sovereignty assessment is a structured scan of all your cloud and SaaS dependencies. We map which systems run on US hyperscalers or US SaaS services, where your data flows to and which systems fall under the US CLOUD Act. The result is a report with a dependency map, a risk classification and an exit plan per application.
Is an exit plan mandatory?
For the Dutch central government it is: the revised Rijkscloudbeleid (central government cloud policy) of 3 July 2026 requires a risk assessment up front and an annually updated exit plan for public cloud services. Under DORA, which has applied since 17 January 2025, financial institutions must have exit strategies for critical ICT services. For other organisations it isn't mandatory, but it is the logical foundation of any cloud strategy.
What exactly does CLOUD Act exposure mean?
The US CLOUD Act can compel US companies to hand over data to US authorities, even if that data is physically located in a European data centre. Exposure therefore doesn't only arise from hosting directly with a hyperscaler, but also through SaaS services and the underlying infrastructure of US suppliers. In the assessment, we make that exposure visible per system.
Does Appfront also carry out the migration itself?
Yes, at application and data level. We migrate or rebuild applications so that they run on EU-sovereign infrastructure. For data centre, IaaS and colocation matters, we work with specialised Dutch infrastructure partners; we already map those alternatives during the assessment.
What will we actually receive?
A report with a complete dependency map, the CLOUD Act exposure per system, a risk classification, an exit plan per application and a prioritised migration roadmap. It lets you decide on solid grounds what has to come first and what can wait.
Do we then have to move all our systems?
No. The assessment is designed precisely so that you can choose based on risk. Some workloads can stay where they are, while others call for a European alternative or an adapted architecture. The risk classification shows where the real dependencies lie, so you invest where it counts.

Getting started with a sovereignty assessment

Want to know where your cloud dependencies lie and what an exit would involve for each application? We'll gladly run the scan for you and give independent advice on the next steps.

Edit content