Less reliance on US suppliers
Using European cloud providers and open-source solutions can reduce your dependence on specific US technologies and suppliers.
From Microsoft Azure to a European, sovereign cloud. More control over your infrastructure, less reliance on US suppliers and potentially much lower costs.
Do you want greater digital sovereignty and less reliance on US cloud providers such as Microsoft Azure, AWS or Google Cloud? Moving to a European, sovereign cloud environment can be an important step.
But how do you approach a migration like this? What European alternatives are available? What happens to your existing systems and integrations? How do you avoid unexpected costs during the migration? And what will the move ultimately deliver?
At Scrape IT, we are making this move ourselves. After more than 20 years as a Microsoft partner, we are migrating our services from Microsoft Azure to a European, sovereign cloud environment.
We are replacing existing cloud services with European hosting solutions and open-source alternatives. We also use the knowledge and practical experience we gain during this migration to help other organizations.
Many organizations use US cloud providers for their servers, applications, databases and other IT services.
This can work well for years. Even so, there are reasons to take another look at how your cloud environment is set up.
One of them is digital sovereignty.
Storing your data on European servers does not automatically mean you are fully independent of US law.
If you work with a US cloud provider, that provider may be subject to US law. Under certain circumstances, this can affect access to and availability of services, even when the data is physically stored in Europe.
There are other reasons to consider making the move, too.
Using European cloud providers and open-source solutions can reduce your dependence on specific US technologies and suppliers.
You gain more options for deciding how your systems are configured, managed and expanded.
European hosting combined with open-source software can be a financially attractive alternative to major cloud platforms. The actual savings depend on your infrastructure, capacity and management arrangements.
Reducing your use of proprietary cloud services makes it easier to replace or move parts of your infrastructure.
Choosing a European cloud can therefore offer technical and financial benefits as well as greater digital sovereignty.
Microsoft Azure offers a wide range of services, from virtual servers and databases to storage, monitoring and data processing.
Over the years, many organizations have built their infrastructure around these services. As a result, their systems are often closely interconnected.
This makes switching more complex than simply choosing a new hosting provider.
Nevertheless, suitable European and open-source alternatives exist for many Azure services.
During our own migration, we have found that many parts of our existing infrastructure can be configured differently, without having to remain dependent on Microsoft Azure.
Depending on your current cloud environment, we can help you assess and migrate various components:
Move existing servers to a European hosting environment.
Assess which systems are suitable for a move to Linux.
Move existing data and storage to a new infrastructure.
Adapt existing applications for a different hosting environment.
Explore which services can be replaced with open-source alternatives.
Ensure that existing connections between applications and services continue to work.
Not every Azure service can be replaced directly. Sometimes changes to the infrastructure or applications are needed.
That is why a successful cloud migration starts with understanding your current environment and the dependencies between systems.
At Scrape IT, we are migrating our infrastructure from Microsoft Azure to a European cloud environment. As part of this, we are replacing various Microsoft services with open-source alternatives.
For our new infrastructure, we use bare-metal servers at the German hosting provider Hetzner. These run Ubuntu Linux as their operating system.
We use Coolify and Docker to manage and deploy our applications, databases and other services.
But which Microsoft Azure services have we actually replaced?
| Microsoft Azure | Our alternative |
|---|---|
| Azure Portal | Coolify |
| Azure Functions | Docker with .NET Functions |
| Azure SQL | PostgreSQL |
| Microsoft Fabric / Azure Databricks | Apache Spark + Apache Airflow |
| Azure API Management | Gravitee |
| Microsoft Entra ID | Keycloak |
Within Microsoft Azure, we used Azure Portal to manage and configure our cloud services.
With Coolify, we now have an open-source platform that lets us install and manage applications, databases and other services on our own servers. Examples include databases, service buses and data processing platforms.
Combined with Docker, it gives us an overview of our servers, projects and available infrastructure. Coolify therefore provides an alternative for a significant part of the management we previously carried out through Azure Portal.
We made extensive use of Azure Functions for background processes.
Within Azure, we could easily create new functions, upload our source code and set the desired configuration.
These processes now run in Docker containers that we manage through Coolify. For this, we use a standard Docker configuration connected to our Git environment.
When we change the source code, a new version is automatically deployed to the Docker container. This was relatively straightforward to set up, without extensive installation expertise.
This allows us to retain an automated deployment process without depending on Azure Functions.
We are replacing our Azure SQL databases with PostgreSQL, an open-source database system.
We can install and manage PostgreSQL directly through Coolify. This gives us a fully fledged relational database system within our own infrastructure.
For our applications, PostgreSQL offers comparable capabilities without making us dependent on Azure SQL.
We made extensive use of Microsoft Fabric and Azure Databricks to process, manage and check the data we collected.
These services offer extensive data processing capabilities, but also come with considerable costs.
One interesting discovery during our migration was that Microsoft itself uses open-source technology, including Apache Spark, for certain data processing capabilities.
We therefore decided to set up our own Apache Spark environment, combined with Apache Airflow to schedule and automate data processing workflows.
This turned out to be one of the biggest benefits of the migration for us.
What surprised us most was the large price difference. Apache Spark and Apache Airflow give us the technology we need, while our costs are significantly lower and we have access to faster clusters.
For us, this was a real eye-opener.
Our experience shows that open-source technology can be a financially and technically attractive alternative to commercial cloud platforms, especially when you regularly process large volumes of data.
We used Azure API Management to manage access to our APIs, including authentication and forwarding requests to different services.
The advantage of API Management is that you have a single central access point for all your APIs.
We now use Gravitee, an open-source API management platform, for this.
Within Azure, we paid relatively high fees for this functionality. With Gravitee, we now have a solution that works at least as well for our applications, but that we manage entirely within our own infrastructure.
This allows us to retain the functionality we need without depending on Azure API Management.
We used Microsoft Entra ID for centralised user management and authentication.
When you use multiple applications and services, you want to avoid each application having a separate user system.
It is therefore important to manage authentication, user accounts and access rights centrally.
We addressed this with Keycloak, an open-source identity and access management platform.
This allows us to manage user accounts, authentication and authorisation centrally within our own infrastructure, without depending on Microsoft Entra ID.
By replacing Microsoft Azure services with open-source alternatives, we have gained more control over our infrastructure and the technology we use.
We have also been able to significantly reduce our recurring cloud costs.
Particularly in data processing, we have found that open-source alternatives can offer both lower costs and good performance.
Not every Microsoft Azure service can be replaced directly. Sometimes technical changes, additional configuration or extra management are necessary.
But our own migration shows that suitable alternatives are available for many applications.
A European, sovereign cloud environment therefore does not have to be more expensive or technically more complex than Microsoft Azure. The options and costs depend on your existing infrastructure, the services you use and how you organise management.
One of the most important lessons from our own migration is that the technical move is not always the biggest challenge.
Alternatives are available for many services. But the way cloud platforms structure their infrastructure, services and pricing can make switching difficult.
Microsoft Azure offers many services that allow businesses to build and manage their infrastructure within a single platform.
But the more dependent you become on that environment, the harder it can be to switch to another cloud provider later.
This is known as vendor lock-in.
One of the biggest challenges we encountered during our migration was Microsoft Azure's outbound data transfer charges.
When systems exchange data within the Azure network, the charges are relatively low. But as soon as you move a system outside Azure while it continues to exchange large amounts of data with systems inside Azure, costs can rise significantly.
This makes it harder to migrate away from Azure gradually. Costs may actually increase temporarily during the transition.
For Scrape IT, this was one of the most difficult parts of the migration.
Vendor lock-in is therefore about the financial consequences of leaving a cloud platform as well as the technology involved.
Many applications depend on multiple services within the same cloud platform.
For example, an application may use a database, storage, an authentication service and various network components.
Moving one component can affect other systems.
It is therefore important to identify in advance which services communicate with each other and what changes are needed to make them work outside Azure.
A European cloud environment may be set up differently from an existing Azure environment.
Some management tasks that Microsoft handles automatically may need to be organized in-house or assigned to a hosting partner when you use a different solution.
This may require extra time and technical expertise at first.
In return, you may gain more freedom to configure your infrastructure to suit your needs.
Switching away from a US cloud provider? Surely that would be far too expensive?
This is one of the arguments used against moving to a European, sovereign cloud.
But is it really true?
During our own migration at Scrape IT, we have found that European hosting combined with open-source software can be significantly cheaper than our existing Azure environment.
Of course, you need to look beyond monthly hosting costs alone.
The following costs also play a role:
A move may therefore require a one-time investment, followed by lower recurring monthly costs.
We want to make the financial impact of our own migration clear.
That is why we are sharing our actual costs and savings.
| Cost item | Amount |
|---|---|
| Monthly costs of the previous cloud environment | € 1,944.44 |
| Monthly European cloud costs | € 148.00 |
| Estimated migration labor costs | € 5,000.00 |
| Monthly savings | € 1,796.44 |
| Percentage cost savings | 92.4% |
| Estimated payback period (months) | 2.8 |
Based on our current costs, we expect the move to a European cloud environment to reduce our monthly costs by approximately 92%.
The migration is not yet fully complete. The time required and the associated migration costs are therefore currently based on an estimate.
Based on this estimate, we expect to recover the migration costs within approximately three months.
The actual migration costs and payback period may still change once the migration is fully complete.
The cost savings we are achieving through our migration are substantial. It is important to explain that our infrastructure has several specific characteristics that contribute to these savings.
For example, we use many environments that require relatively little processing power (CPU). This allows us to combine multiple environments and run them on just one or two machines.
Our web scrapers are also deliberately designed to avoid placing unnecessary load on websites. They collect data throughout the day, keeping processing requirements relatively low and allowing us to use our server capacity efficiently.
We have also deliberately chosen to handle more technical management ourselves. This gives us more control over our infrastructure and reduces the cost of external management, but it naturally requires our own technical expertise and time.
Our savings therefore cannot be applied directly to other organizations. Potential savings from a cloud migration depend on factors such as the existing infrastructure, required processing power, use of cloud services and how management is organized.
What our experience demonstrates above all is that a European, sovereign cloud environment does not automatically have to cost more than a US cloud provider.
At Scrape IT, we are working toward greater digital sovereignty ourselves. After more than 20 years as a Microsoft partner, we decided to reduce our reliance on US cloud providers.
That is why we are migrating our services from Microsoft Azure to a European, sovereign cloud environment.
During this transition, we have gained valuable experience with technology, costs and management. We are happy to share that knowledge with other organizations considering a similar move.
One of our first steps was moving from Windows servers to Linux.
Our technical staff needed some time to adjust at first. Not everything works the way you are used to, and some tasks require a different approach.
They now see Linux as a flexible system that offers many options for configuring infrastructure to suit their needs.
AI has also proved useful when learning new systems and solving technical problems.
Open-source alternatives are available for many Microsoft Azure services. During our own migration, we found that we could replace various parts of our infrastructure without remaining dependent on Microsoft.
We use technologies such as PostgreSQL, Apache Spark, Docker and Keycloak for this.
The move sometimes requires technical changes and a different approach to management. Even so, replacing various Azure services turned out to be easier than we had expected.
Curious about the alternatives we use? We have put together an overview of the Microsoft Azure services we have replaced and the open-source solutions we use instead.
Within Azure, many infrastructure components are offered as managed services.
This is convenient, but it also means you depend on the platform's capabilities, settings and pricing.
For our new infrastructure, we have chosen to handle more tasks ourselves.
This sometimes requires extra maintenance and configuration, but also gives us more control.
Organizations that prefer to outsource this work can choose European hosting partners that provide technical management.
During our migration, we have found that European providers can deliver high-quality hosting solutions.
Various service models are available, from infrastructure you manage entirely yourself to environments managed by an external provider.
For us, this confirms that a US hyperscaler is not necessary for every application.
Would you like to explore whether your organization can move to a European, sovereign cloud environment?
Digital sovereignty involves more than moving your data to Europe. Your choice of hosting provider, the technology you use and the way your infrastructure is managed all play a role.
That is why we start by mapping your existing infrastructure, technical dependencies and potential costs.
At Scrape IT, we use our own migration experience to support other organizations through this process.
We start by mapping your current infrastructure.
Which servers, databases, applications and cloud services do you use? How are these systems connected? And which components depend on specific technology within Microsoft Azure or another cloud provider?
This gives us an overview of the components that could potentially be migrated.
Next, we assess which European hosting providers and open-source solutions could be suitable.
We take into account your existing technical requirements, performance, required capacity and management options.
We also identify which components can be moved directly and where technical changes are needed.
Not all systems need to be moved at the same time.
We assess which sequence makes the most sense technically and financially.
We pay particular attention to dependencies between systems, data transfer costs and minimizing disruption during the transition.
Depending on your existing infrastructure, we help move and reconfigure systems and services.
This may involve servers, databases, storage or replacing specific Azure services with European or open-source alternatives.
We also check how existing applications and integrations work within the new environment.
After moving the systems, it is important to verify that everything is working properly.
We review infrastructure operation, performance and potential improvements to the setup.
We can also explore whether further savings are possible by adjusting capacity or configuration.
Do you want to reduce your reliance on US cloud providers and gain more control over your data and IT infrastructure?
At Scrape IT, we can help you explore the options for moving existing systems to a European, sovereign cloud environment.
We have experienced the technical and financial challenges of a cloud migration firsthand.
From replacing Azure services with open-source alternatives to handling data transfers, dependencies and setting up a new hosting environment.
We are happy to share that knowledge.
Whether you want to explore available European alternatives, understand the potential costs or get support with the migration itself, we are happy to work through the options with you.
Curious about what moving to a European cloud could mean for your organization?