EU-Hosted AI Models and EU-Hosted Websites: Two Layers

Search for "EU hosted AI models" and you land in a debate about inference: which large language models run on European servers, under European law, without a detour through a US cloud region. It is a good question. It is also only half of the stack. If you use one of those models to build a website, a second, quieter question follows immediately: where is that website served once it exists? The two questions have different answers, different risks and different fixes, and this guide keeps them apart.

What people mean by EU-hosted AI models

When someone asks for an EU-hosted AI model, they usually mean one of four setups.

First, a European model company that processes requests in Europe. Second, the European regions that large model providers and cloud platforms offer for their models, under contractual data-residency terms. Third, open-weight models self-hosted on servers you or a European provider control, which puts inference wherever you put the hardware. Fourth, European inference platforms that serve open models from EU data centres as an API.

Each option aims at the same concern: the prompts you send and the text or code that comes back are processed inside EU jurisdiction. For teams with strict clients, works councils or public-sector rules, that alone can decide which model they may use at work. The details matter, though, because "available in Europe" and "processed only in Europe" are different promises.

Do Claude, ChatGPT and Mistral run on EU servers?

Here is what each vendor says on its own pages, checked on 13 October 2026. The short version: none of the three keeps everything in the EU by default for every product, and all three offer some EU option.

ChatGPT and the OpenAI API. OpenAI offers data residency, meaning storage at rest, in regions that include "Europe (EEA + Switzerland)". Its eligibility line reads: "Eligible API customers and new ChatGPT Enterprise/Edu customers can choose to have in-scope customer content stored at rest in supported countries." In ChatGPT, inference residency, which keeps the model's GPU work in the region, is available to eligible Enterprise and Edu customers in Europe and other regions, on top of data residency. For the API, eligible projects can also run inference in Europe through eu.api.openai.com, which requires approval for modified abuse monitoring or zero data retention. OpenAI is explicit about the limits: account data, billing details and logs without content are out of scope, "Non-GPU processing may still occur globally", and ChatGPT Sites is not covered at launch. Individual ChatGPT plans are not on the eligibility list.

Claude and the Anthropic API. On Anthropic's own API, the inference_geo setting has two values today: "global", where inference "may run in any available geography", and "us". Its documentation lists the current limits plainly: "Only "us" and "global" are available", and for stored data, "Only "us" is currently available." For Europe, Anthropic points to its models on cloud platforms: its regional compliance page lists Europe as included on AWS Bedrock and Google Cloud Vertex AI, and as coming soon on Microsoft Foundry, where "regional endpoints guarantee that both data storage and model processing remain within your specified geographic region."

Mistral. Mistral's help center says: "By default, your data is hosted in the European Union", unless you explicitly use its US API endpoint, and that, depending on the feature, data "can be temporarily transferred outside of the European Union" to the sub-processor locations in its Trust Center. Inference location is a separate choice. Mistral's documentation describes a regional EU endpoint, api.eu.mistral.ai, that processes inference in "multiple data centers in EU and EFTA countries" and is billed at 1.1 times the standard price; for the default global endpoint, "Mistral does not commit to a specific inference location". Even the EU endpoint "does not make the Mistral control plane regional". Mistral's chat app, formerly Le Chat, is now called Vibe.

What this means for you: if the model layer must stay in Europe, pick the specific product, plan and endpoint that carries the guarantee, and get it in writing. "The vendor is European" and "the vendor has an EU region" are both weaker statements than that.

The layer underneath: where the AI-built site is served

Now let the model do its job. You describe a site, the model writes it, and out comes a folder of HTML, CSS and JavaScript, sometimes with a small server or database attached. From this moment on, the model is out of the picture. The thing that matters next is the hosting layer: the servers that answer your visitors, around the clock, for years.

That layer has its own residency question, and it is the one your visitors actually touch. Every visit to the finished site sends the visitor's IP address, and often form submissions with names and email addresses, to whichever host serves the files. An impeccably European model followed by a US-edge deploy means your own data stayed in the EU while your visitors' data leaves it on every page view.

Why the two layers are independent

Generation is a moment; serving is a subscription. The generation step touches your prompt, your ideas and your code, at build time. The serving layer touches your visitors' data on every request, indefinitely. You can mix the layers freely, which is precisely why they get confused: a US model can feed an EU host, and an EU model can feed a US host. The first combination protects your visitors but not your prompts; the second protects your prompts but not your visitors. Only choosing deliberately at both layers closes the loop.

Our data residency guide walks through what sits where for an AI-built site in more detail, and the EU data sovereignty overview covers the legal side.

An EU model plus an EU host, end to end

A chain that keeps both your prompts and your site in Europe is short and practical. Use a model with a European inference commitment, for example Mistral through its EU endpoint, to build or refine your site. Then deploy the generated project on VibeDeploy, where it is served from servers in Belgium by a Belgian operator, Tnet Comm.V, with a DPA on every paid plan. The Mistral deploy guide covers the handoff step by step, and the localhost guide covers the generic case of getting any locally generated build online.

The result: prompts processed in the EU or EFTA, visitors served from the EU, and something concrete to answer when a client or DPO asks where the data goes. If you are still choosing the hosting half, the European alternatives to Vercel and Netlify compares ten hosts with sources.

What VibeDeploy hosts, and deliberately does not

To be precise about our own layer: static sites and single-page apps are served directly, and a site can also run containers next to it (your own server, Postgres, MySQL, Redis or workers; up to 6 services with 2 CPU and 2 GiB in total), deployed by your AI through the MCP tool deploy_app and isolated with gVisor. Container data is not yet included in snapshots. There are no GPUs, and we do not offer model inference. If you need an EU-hosted model, pick one from the options above; if you need the site it produced to be EU-hosted, that is what we do. Keeping the two layers separate is not a limitation, it is the design: each layer is run by the party best placed to run it.

A verification checklist

Before calling a setup "EU-hosted", check both layers explicitly:

1. Model layer: where does inference run, under whose jurisdiction, and on which endpoint? Is that in the provider's DPA or data-residency terms for your plan?
2. Model layer: are prompts retained or used for training, and can you disable that?
3. Hosting layer: which company serves your visitors, and where are its servers?
4. Hosting layer: is there a DPA covering visitor data, and does traffic route through non-EU edges?
5. Both: can you name the answer for each layer in one sentence? If not, one layer is still assumed rather than chosen.

Two layers, two decisions. Choose both on purpose, and the whole chain, from the prompt to your visitors, stays on European ground. The hosting half starts at our pricing page, with a 14-day trial and no card; prices include VAT where it applies.

Sources

Vendor pages checked on 13 October 2026:

• OpenAI Help Center: Data residency and inference residency for ChatGPT
• OpenAI API documentation: Data controls in the OpenAI platform, section "Data residency controls"
• Anthropic: Data residency (Claude API documentation) and Regional compliance
• Mistral Help Center: Where do you store my data or my Organization's data? and Le Chat is now Vibe
• Mistral documentation: Regional inference