Cloud-nativeDutch cloudPortability

Cloud-native development for a Dutch cloud

Cloud-native applications are built to run in the cloud: in containers, with automated deployments and infrastructure defined as code. Appfront applies those principles on Dutch and European infrastructure. We build with open standards rather than proprietary hyperscaler services, so your application stays portable between Dutch providers. We build the software; the hosting runs with specialist Dutch infrastructure partners.

What is cloud-native development for a Dutch cloud?

Cloud-native development means an application is built for the cloud from the very first design: split into services, packaged in containers, with configuration separate from the code and fully automated deployments. With the large American hyperscalers, cloud-native in practice quickly becomes entangled with proprietary services: managed databases, queues, functions and identity services that only exist on that one platform. If you build on those, you are tied to a provider that falls under the US CLOUD Act and FISA, even if the servers are in the EU.

We turn that around. We build cloud-native on open standards: Kubernetes for orchestration, PostgreSQL as the database, S3-compatible object storage and open-source components for caching, queues and monitoring. As a result, the same application runs on any Dutch or European provider that offers these building blocks, and moving between providers remains a manageable operation. Cloud-native and sovereignty go hand in hand: the portability that cloud-native promises is only truly delivered when the application does not depend on hyperscaler services.

This approach is in line with the direction of the revised Dutch central government cloud policy of 3 July 2026, which requires storage and processing within the EEA and expects government organisations to maintain an annual exit plan. An application built to be portable from the start effectively has that exit plan built in. If you want to bring an existing environment under EU jurisdiction, also take a look at building a sovereign cloud.

How we approach this

1
Architecture and provider selection
We design the application architecture based on your requirements for data, integrations and compliance, and together with you we select a Dutch infrastructure partner that fits.
2
Building to 12-factor principles
We build stateless services with configuration in the environment, explicit dependencies and logs as an event stream, so the application behaves the same everywhere.
3
CI/CD and infrastructure as code
Every change goes to production through an automated pipeline with tests and reviews. The entire infrastructure is defined in code and can be reproduced at any provider.
4
Go-live and further development
After go-live we take care of monitoring, security updates and further development, and we keep the application portable with every change.

What we build and deliver

Cloud-native applications
New web applications, portals and APIs, built from the first line of code for Dutch and European infrastructure.
Containers and Kubernetes
Applications packaged in containers and deployed on Kubernetes, the open orchestration standard offered by virtually every European provider.
Open data layer
PostgreSQL, S3-compatible object storage and open-source components for caching and queues, instead of proprietary hyperscaler services.
CI/CD pipelines
Automated building, testing and deployment, so releases are predictable and repeatable.
Infrastructure as code
The entire environment captured in code, so it is reproducible and an exit or migration doesn't become guesswork.
Management and monitoring
Ongoing maintenance, observability and security updates for the environment at your infrastructure partner.

Who it's for

Government and public sector

Organisations covered by the Dutch government's cloud policy (Rijkscloudbeleid) and the BIO that want to set up new applications within the EEA from day one, with an actionable exit plan.

Healthcare

Institutions that process medical data under NEN 7510 and the GDPR and don't want to entangle new systems with non-EU services.

Financial sector

Organisations covered by DORA that need a grip on outsourcing risks and the exit strategy of their ICT supply chain.

SaaS and product companies

Builders of software for customers who require data to be located in the Netherlands or the EU, or who must account for their supply chain under NIS2 and the upcoming Dutch Cybersecurity Act.

Technology and approach

We deliberately choose technology that is available from multiple providers. No functions, queues or databases that exist only at a single hyperscaler, but open components that run on any Kubernetes environment. That keeps the application portable and leaves your choice between Dutch providers open, now and later.

Kubernetes and containers
PostgreSQL
S3-compatible object storage
Terraform / OpenTofu
CI/CD pipelines
Open source components
Encryption in transit and at rest
Monitoring and logging

Why Appfront

Appfront is a software and app development company. We build the applications and set up the deployment; the infrastructure runs with Dutch partners who specialise in it. Because we don't sell hosting ourselves, our advice on providers and architecture is independent. What it gives you: an application that is portable between providers, an exit plan that holds up on paper and in practice, and no forced migration or rebuild when regulations or your choice of provider change. If existing software needs tackling instead, rebuilding software sovereignly is often the better route.

  • Cloud-native from the start, not a retrofit
  • Open standards so the application stays portable between providers
  • Independent advice, we don't sell hosting ourselves
  • Knowledge of GDPR, NIS2, DORA, NEN 7510 and BIO built into the architecture

Frequently asked questions

What does cloud-native development mean for a Dutch cloud?
Cloud-native means an application is designed from the outset to run in the cloud: in containers, with separate services, automated deployments and configuration kept apart from the code. We apply those principles on Dutch and European infrastructure, using open components instead of services that exist only at an American hyperscaler.
Does Appfront host the applications itself?
No. Appfront is a software and app development company; we build the applications and set up the deployment. Hosting runs with specialised Dutch infrastructure partners, selected based on your requirements for location, certification and management.
Will I miss out on functionality if we don't use hyperscaler services?
Almost all the building blocks of the major hyperscalers have mature open alternatives: PostgreSQL for managed databases, S3-compatible object storage, Kubernetes for orchestration and open source solutions for queues, caching and monitoring. The difference lies mainly in ease at the start, not in what is ultimately possible.
Can we switch Dutch providers later?
Yes, that is exactly the aim of this approach. Because the application runs on containers, Kubernetes and open standards, and the infrastructure is captured as code, moving to another Dutch or European provider is a manageable operation rather than a rebuild project.
Does this align with the Dutch government's cloud policy and NIS2?
The revised Dutch government cloud policy of 3 July 2026 calls for storage and processing within the EEA, a risk assessment per workload and an annual exit plan. Building cloud-native on Dutch infrastructure makes that exit plan practically executable. For NIS2, DORA, NEN 7510 and BIO too, it helps that you can demonstrably keep control over where your data is stored and what the supply chain looks like.
We already run on a US hyperscaler. What now?
Then we first look at how deeply you are tied into proprietary services. Sometimes it is enough to containerise the application and replace a few services; sometimes partially rebuilding is the wiser choice. We map this out and draw up a realistic step-by-step plan.

Get started with cloud-native development

Do you want to build a new application from the start for Dutch infrastructure, portable and free of dependence on hyperscaler services? We are happy to help you think through the architecture and provider choice.

Edit content