Sovereign rebuildEU jurisdictionOpen source

Rebuilding software on a sovereign stack

Some applications simply cannot be made sovereign by moving them: they are interwoven with proprietary services from American hyperscalers, run on legacy technology, or are effectively an American SaaS product you want to move away from. Appfront designs and rebuilds such software on an open, sovereign stack under EU jurisdiction, in phases alongside the existing system. We build the application, the data migration and the integrations ourselves; for data centre and infrastructure services we work with specialised Dutch infrastructure partners.

What does rebuilding software as sovereign mean?

Rebuilding as sovereign means we redesign and rebuild an application that is technically or contractually tied to American technology on a stack that falls entirely under European jurisdiction. That is different from migrating: when migrating applications to a sovereign cloud, the software largely moves across unchanged. Where that is possible, migrating is usually the more logical route. Rebuilding comes into play when the application is deeply interwoven with proprietary hyperscaler services, when legacy technology can no longer be run or maintained properly outside the current platform, or when you want to replace an American SaaS product with software you manage yourself.

The trigger is often legal and strategic. American providers fall under the US CLOUD Act and FISA, even if their servers are in the EU. The revised Dutch central government cloud policy of 3 July 2026 requires central government to store and process data within the EEA, carry out a mandatory risk assessment and maintain an exit plan that is reviewed annually, and advises against using the public cloud for email and document management; state secrets and key registers do not belong there at all. In addition, the GDPR, NIS2 via the Dutch Cybersecurity Act (in force from 15 August 2026), DORA for the financial sector, NEN 7510 in healthcare and the BIO for government set concrete requirements for where and how data is processed.

In such cases, migrating an interwoven application produces a copy of the problem: the same dependencies, just in a different place. Rebuilding on an open stack is then the shortest route to an application that demonstrably falls under EU law and that you can move later without another rebuild.

How we approach this

1
Inventory and dependencies
We map the current application: which proprietary services, integrations and contracts are woven into it, which data is sensitive and which legal requirements apply to your sector.
2
Defining the core functionality
We analyse what your organisation actually uses. Not everything needs to come along: the rebuild focuses on the functionality that delivers value, without the ballast of years of legacy.
3
Building in phases alongside the old system
We build the new application on an open, sovereign stack, alongside the existing system. Functionality moves over component by component, with data synchronisation where needed, so work carries on uninterrupted.
4
Switching over and further development
Only once the new system has proven itself do you switch over and we decommission the old one. After that, we handle management, monitoring and further development on the sovereign environment.

What we build and deliver

Rebuilding interwoven cloud applications
We redesign applications that rely on proprietary hyperscaler services using open alternatives, so that they run on any EU infrastructure.
Replacing American SaaS
We build a dedicated application for the functionality you actually use, with your data and your software in your own hands.
Legacy to an open stack
We rebuild outdated systems that no longer run anywhere else on modern, maintainable technology.
Data migration and integrations
We move your data to the new system in a controlled way and rebuild the integrations with your other applications.
Open-source foundation
The rebuild uses open-source components and open standards as its starting point, so the solution is portable and verifiable.
Management and further development
After the switchover, we provide maintenance, security updates and new functionality on the sovereign environment.

Who it's for

Government and public sector

Organisations covered by the revised Dutch central government cloud policy and the BIO (Dutch baseline information security for government) whose applications are too entangled with US services to migrate.

Healthcare

Institutions that must comply with NEN 7510 and the GDPR and want to move medical data out of US SaaS environments.

Financial sector

Organisations covered by DORA that want to reduce their dependence on critical US ICT providers.

Organisations under NIS2

Companies in critical sectors that need to secure their digital supply chain under the Cybersecurity Act and want to replace software they are locked into.

Technology and approach

Open source and portability are the starting point of every rebuild. We choose components that you can inspect, have audited and, if need be, run yourself: open-source frameworks, PostgreSQL instead of proprietary databases, containers instead of platform-specific services. That way the new application is not only sovereign where it runs today, but also remains portable between EU providers. We deliberately engineer out dependence on a single vendor, the lock-in that often creeps in unnoticed with hyperscalers.

EU-based infrastructure
Open-source frameworks
PostgreSQL
Kubernetes / containers
Infrastructure as Code
Open standards and APIs
Encryption in transit and at rest
Monitoring and logging

Why Appfront

Appfront is a technical software and app agency that keeps the entire process in its own hands: from analysing the existing application to design, build, data migration and ongoing maintenance afterwards. For data centre, IaaS and colocation services, we work with specialised Dutch infrastructure partners; we take the lead and make sure the software runs reliably on them. Because we sell no hosting or licences ourselves, our advice on the stack is not coloured by a platform of our own.

  • Rebuild, data migration and integrations in one hand
  • Open source and open standards as the starting point
  • A phased approach alongside the existing system
  • Control over infrastructure through Dutch partners

Related services

If your application can largely move over unchanged, take a look at migrating applications to a sovereign cloud. If you want to set up a new solution as sovereign from the start, see building a sovereign cloud. For the broader issue of outdated systems, there is platform modernisation, and if you are comparing agencies, you will find an overview in the best software modernisation agencies.

Frequently asked questions

What is the difference between rebuilding and migrating?
With migration, an existing application moves largely unchanged to sovereign infrastructure. With a rebuild, we design and build the application anew on an open, sovereign stack. A rebuild is the right choice when the software is so entangled with US cloud services or SaaS that moving it would only shift the problem elsewhere.
When is rebuilding wiser than migrating?
When an application leans heavily on a hyperscaler's proprietary services, when legacy technology can no longer be run or maintained properly outside that platform, or when you want to replace a US SaaS product with software you control yourself. In those cases, migrating just copies the old dependencies across, and rebuilding is the shortest route to genuine sovereignty.
Does the old system stay available during the rebuild?
Yes. We build the new application in phases alongside the existing system. Functionality moves over component by component, with data synchronisation where needed, so your organisation can keep working and you only say goodbye to the old system once the new one has proven itself.
Can you replace a US SaaS solution?
Yes. We analyse which functionality your organisation actually uses, design a dedicated application for it and build it on sovereign infrastructure. You keep control of your data and software, with no subscription to a provider that falls under US jurisdiction.
Why do you build with open source?
Open source and open standards are the foundation of portability: the application can run on any modern EU infrastructure and is not tied to one vendor's services. That way, the rebuild does not create a new dependency.
Does Appfront provide the sovereign infrastructure itself?
No. Appfront designs and builds the software; for data centre and infrastructure services, we work with specialised Dutch infrastructure partners. We advise independently on the environment that fits your requirements and keep control of the overall solution.

Get started with a sovereign software rebuild

Is your application tied to a US stack or SaaS platform, and do you want to know whether rebuilding or migrating is the best route? We'd be glad to look at the dependencies and the approach with you.

Edit content