Central government cloud policyBIO and NIS2EEA data location

Sovereign cloud for government

The revised Central Government Cloud Policy of 3 July 2026 sets clear requirements: storage and processing within the EEA, a mandatory risk assessment for each cloud service and an annually updated exit plan. Appfront builds and migrates government applications, citizen portals and integrations so that they meet these requirements. We develop the software ourselves; for the underlying infrastructure, we work with specialised Dutch partners.

What is a sovereign cloud for government?

A sovereign cloud is cloud infrastructure that falls entirely under European law and European ownership. For government bodies, that distinction matters: a US provider is subject to the US CLOUD Act even if its servers are in the EU, because the parent company can be compelled to hand over data. If you process citizen data, you want to be able to rule out that dependency and demonstrably remain under EU jurisdiction.

The revised Rijksbreed Cloudbeleid (central government cloud policy) of 3 July 2026 makes this concrete. Storage and processing must take place within the EEA, a risk assessment is mandatory for every cloud service, and an exit plan must be in place and updated annually. Email and document management in the public cloud are discouraged, and state-secret information and basic registrations do not belong in the public cloud. In addition, the BIO applies as the baseline for information security in government, along with the NIS2 directive, which takes effect on 15 August 2026 through the Dutch Cybersecurity Act.

Appfront helps government organisations keep working within these frameworks without grinding to a halt. We build new applications that are sovereign by design from the very first architecture sketch, and migrate existing systems away from environments that no longer fit the policy. You can read about how such an environment is set up technically on our page about building a sovereign cloud.

How we approach this

1
Inventory and risk assessment
We map applications, data flows and integrations, and carry out the risk assessment for each cloud service that the revised central government cloud policy requires: which data is sensitive and which requirements apply.
2
Architecture and partner selection
We design an architecture on infrastructure within the EEA and, together with you, select a suitable Dutch infrastructure partner, independently and based on your requirements.
3
Build or migrate
We build the application or migrate the existing system, using Common Ground principles and open source where appropriate, with attention to integrations and portability.
4
Management and exit plan
After delivery we provide monitoring, maintenance and further development, and supply the technical substantiation for the annually updated exit plan.

What we build and deliver

Government applications
Custom applications for core processes and operations, designed from the architecture up for sovereign infrastructure and the BIO.
Citizen portals
Portals where residents can arrange matters, submit applications and view their data, with accessibility and privacy as the starting point.
Migration from the public cloud
Moving existing applications and workloads to infrastructure within the EEA, without losing functionality or integrations.
Integrations
Secure integrations with basic registrations, national services and your existing line-of-business applications, using open standards and APIs.
Common Ground and open source
Where appropriate, we align with Common Ground principles and open source components, so that solutions can be reused across government bodies.
Management and further development
Ongoing maintenance, security updates and monitoring, plus the documentation you need for your risk assessment and exit plan.

Who it's for

Municipalities

Municipalities that want to set up line-of-business applications, portals or integrations in a sovereign way. For custom work in the municipal domain, we have a separate page on building software for municipalities.

Implementing bodies and independent administrative bodies

Organisations that process large volumes of citizen data and must be able to justify their cloud choices with a risk assessment and exit plan.

Central government and provinces

Parts of central government and provinces that fall under the revised central government cloud policy or want to align with it.

Regional health services and joint arrangements

Partnerships that process sensitive resident data and need a single sovereign environment for multiple participants.

Technology and approach

We build on open, portable technology so your applications are not locked in to a single supplier and an exit plan is more than a paper exercise. Containers, infrastructure as code and open standards make it possible to move between sovereign environments. The infrastructure itself runs with specialised Dutch partners; we take care of the architecture, the build and application management.

Infrastructure within the EEA
Dutch infrastructure partners
Kubernetes / containers
Common Ground principles
Open source and open standards
Infrastructure as Code
Encryption in transit and at rest
Logging and monitoring

Why Appfront

Appfront is an independent software and app development company. We do not sell hosting or data centre capacity ourselves, so our advice on infrastructure and architecture is not influenced by a platform of our own. We combine building government applications with the knowledge to set them up sovereignly: from the risk assessment at the start to the exit plan that has to be updated every year.

For government organisations, that combination is the difference between policy on paper and policy in practice. A risk assessment is only useful if the architecture is set up around it, and an exit plan is only worth something if the applications are actually built to be portable. Because we handle both the software and the migration, we can make those requirements work technically rather than just describing them. That also prepares you for the Cybersecurity Act, which brings the NIS2 Directive into force in the Netherlands on 15 August 2026.

  • Independent of hyperscalers and hosting providers
  • Build and migration in our own hands, infrastructure through Dutch partners
  • Common Ground and open source where appropriate
  • Architecture designed around the BIO, the Rijkscloudbeleid (central government cloud policy) and NIS2

Frequently asked questions

What does the revised Rijksbreed Cloudbeleid (central government cloud policy) mean for government organisations?
The revised policy of 3 July 2026 requires storage and processing to take place within the EEA, a risk assessment for each cloud service and an exit plan that is updated annually. It also advises against using the public cloud for email and document management, and state secrets and base registries do not belong in the public cloud.
Does this policy also apply to municipalities and provinces?
The Rijksbreed Cloudbeleid formally applies to central government. Municipalities, provinces and implementing organisations use it as guidance in practice, and they are also subject to the BIO, which sets requirements for information security in government. We design architectures so that they can meet both frameworks.
Does Appfront provide the sovereign infrastructure itself?
No. Appfront is a software and app development company. We build and migrate the applications and take care of the architecture; for data centres and infrastructure, we work with specialised Dutch partners that fall under Dutch and European jurisdiction.
Can you migrate existing government applications?
Yes. We start with an inventory of applications, data flows and integrations, carry out a risk assessment for each component and draw up a migration plan. We then move the applications step by step to sovereign infrastructure, including the integrations with national services.
How do you handle base registries and sensitive data?
Under the revised Rijkscloudbeleid, base registries and classified state information do not belong in the public cloud. We design architectures in which that data stays on private or sovereign infrastructure, while portals and integrations communicate with it in a secure and auditable way.
Do you work with Common Ground and open source?
Yes, where appropriate. We follow common ground principles and use open source components and open standards, so solutions remain reusable and portable and aren't locked in to a single supplier.

Getting started with sovereign cloud for government

Want to know what the revised Rijkscloudbeleid (Dutch central government cloud policy) means for your application landscape, or discuss a specific migration or new build? We're happy to give you independent advice on the best approach.

Edit content