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
What we build and deliver
Who it's for
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.
Institutions that must comply with NEN 7510 and the GDPR and want to move medical data out of US SaaS environments.
Organisations covered by DORA that want to reduce their dependence on critical US ICT providers.
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.
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
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.