Entreprise6 min de lecture
Hosting in Luxembourg vs Germany, Belgium, France and the Netherlands: what actually differs
Same GDPR, same EU, different law, VAT, latency, prices and market. An honest comparison of hosting a server in Luxembourg against its four neighbours, and when each one is the right call.
Cet article n’est pas encore traduit ; la version anglaise est affichée.
The question of where a server should be is usually answered by habit, with whichever provider you already know. For a server that only has to be somewhere in the EU that is fine. The five countries around here are not interchangeable, though, and the differences can be listed. This is the long version of the questions we get asked most often, and where a neighbouring country is the better choice, it says so.
What is the same everywhere
All five are EU Member States. The GDPR applies in full in each of them, the same rules on international transfers apply, and a server in any of them keeps your data inside the EU. A hosting contract with a provider in any of the five is a contract under EU consumer and B2B rules. Moving a VPS between them is a technical job, not a legal one. Luxembourg is not safer for the GDPR than Germany; the differences lie elsewhere.
What differs
Governing law and supervisory authority
The contract is governed by the law of the provider's country, and complaints about data protection go to that country's authority: the CNPD in Luxembourg, the federal and state authorities in Germany, the Data Protection Authority in Belgium, the CNIL in France, the Autoriteit Persoonsgegevens in the Netherlands. If you are a Luxembourg company, a provider under Luxembourg law means your contract, your supervisory authority and your provider's are all in the same system, in a jurisdiction you already deal with. The reverse is also true: a German company gains nothing in legal simplicity from a Luxembourg provider.
A second layer has become more important. Article 32 of the EU Data Act asks providers to take measures against access by governments outside the EU. In practice the test is whether any part of the chain (the operator, the building, the backups, the parent company) is under a non-EU jurisdiction. This is a question about the provider rather than the country, since a provider owned from outside the EU is in the same position in Frankfurt as in Luxembourg. Ask who owns the hardware and who could be ordered to hand over data. The country on the invoice does not answer that.
VAT and invoicing
Business customers with a valid EU VAT number are invoiced without VAT under the reverse charge from any of the five, so for B2B the rate does not matter. For everyone else it does. Luxembourg charges 17 %, Germany 19 %, France 20 %, Belgium and the Netherlands 21 %. On a small monthly server that is a few euros, on a larger bill it becomes visible.
Latency to your users
The round-trip time depends on how many networks a packet crosses, and that depends on where the provider exchanges traffic, not on which side of the border the server stands. A server in Luxembourg that peers at LU-CIX, BNIX and France-IX reaches ISPs present at those exchanges in a handful of milliseconds across Luxembourg, Belgium and Lorraine. A server in Frankfurt or Amsterdam is one or two milliseconds further for those users and a few milliseconds closer for users in Germany or the Netherlands. For a website or a normal application nobody notices either way. For voice or anything else latency-sensitive, pick the location nearest the users and check the provider's peering rather than the country.
Prices and market depth
Germany and the Netherlands have two of the largest hosting markets in Europe, with the economies of scale and the entry prices that come with it. For raw capacity, bulk storage, or a fleet of cheap servers, they are hard to beat. France is similar for volume. Luxembourg is a small market with fewer providers and no race to the bottom, and the prices reflect a datacenter certified to the highest tier and a company that owns what it runs. You pay for that whether or not you need it.
Power and the building
Our servers are in LuxConnect DC1.1, a Tier IV certified datacenter run by LuxConnect, on hydro-sourced electricity with guarantees of origin. That says something about one building and its operator, not about Luxembourg as a whole. LuxConnect is owned by the Luxembourg State, which matters if you plan in years rather than months: a government-owned datacenter is much less likely to be sold, merged, restructured or closed than one owned by a fund or a listed group, and there is no foreign jurisdiction the landlord answers to. Frankfurt and Amsterdam host some of the largest datacenter campuses in Europe at every tier and price point. If your compliance work asks for a specific certification or energy source, check the actual site rather than the country.
Sector rules
Some sectors have their own reasons to care about the country. Luxembourg's financial regulator has its own rules on IT outsourcing, and entities under its supervision usually already know they want a Luxembourg-based provider. If such a rule applies to you, it settles the question before anything on this page does.
Country by country
Luxembourg or Germany. Germany has more providers and lower entry prices. Luxembourg gives you a server under Luxembourg law and jurisdiction, a few milliseconds less to users in Luxembourg, Belgium and Lorraine, and a lower consumer VAT rate. If none of that matters for your workload, a German server is the sensible choice.
Luxembourg or Belgium. We have no datacenter in Belgium. The server is in Bettembourg, twenty minutes from the Belgian border. Our network peers directly at BNIX in Brussels, so traffic to Belgian ISPs present there takes the direct route. Belgian companies with a VAT number are invoiced without VAT, and Belgian consumers pay 17 % Luxembourg VAT instead of 21 %. If the data must physically be in Belgium, Luxembourg is the wrong answer however close it is.
Luxembourg or France. France has large providers and low prices for bulk capacity. Our network peers at France-IX in Paris, so traffic to French ISPs present there is exchanged directly, and Lorraine is closer to Bettembourg than to Paris. What Luxembourg adds is a server under Luxembourg law on hardware the provider owns, with reverse-charge invoices for French companies.
Luxembourg or the Netherlands. The Netherlands has one of the largest hosting markets in Europe and prices to match. For a server that only needs to be somewhere in the EU, that is the benchmark. Luxembourg makes sense when jurisdiction matters, when your users are in Luxembourg, Belgium or the Greater Region, or when you want a provider whose hardware and network are its own.
When to pick which
- Price per gigabyte or per core is the deciding factor: Germany or the Netherlands.
- Your users are in Luxembourg, eastern Belgium or Lorraine, and the application is latency-sensitive: Luxembourg.
- You are a Luxembourg company, or your auditor wants contract, provider and supervisory authority in one jurisdiction: Luxembourg.
- Your users are mostly in one neighbouring country and nothing else distinguishes the options: host there.
- The data must physically stay in a specific country by law or contract: that country.
- You want to know exactly who owns the hardware and who could be ordered to hand over data: ask any provider in any of the five that question, and choose based on the answer.
What we can say about our own servers, in contractual form, is on Hosting under Luxembourg law: NovaNode-owned hardware in LuxConnect DC1.1, no sub-processors for customer data, backups inside the EU, Luxembourg law and the CNPD. The plans themselves are on VPS in Luxembourg, and the plain-language version, including who tends to host here and why, is Why Luxembourg.
NovaNode · 21.10.2026