Where to Host Your API Docs in the EU
· The Routebase Team

Here's a thirty-second test for your API docs. Open your portal in a browser, open the developer tools and switch to the network tab. Then pick any endpoint, press Try it and send a request.
Now look at where that request went.
If the host is your own API, the request travelled from the reader's browser straight to your servers, and nobody in between saw the token. If the host belongs to your docs vendor, the request took a detour through their infrastructure. In that case every reader who ever tried your API from the docs has sent a real token and a real payload through that vendor, wherever its servers happen to stand.
Most teams never run this test, because the console looks exactly the same either way. Most teams also never ask where their docs are hosted, because the pages are public anyway. That holds until a customer's security questionnaire asks, and by then the honest answer depends on parts of the portal that nobody on the team thinks of as documentation.
The pages are the harmless part
Your public pages are meant to travel. They end up in every reader's browser, and a content delivery network keeps copies close to your readers because that is what makes a portal fast. Where the HTML sits is rarely the problem.
The records behind them are not
A portal also watches how it is used. It counts page views so that you know which guides people read, and it logs search terms so that you can see what they were looking for and didn't find. It collects ratings and comments on individual pages, and a portal behind a login keeps a list of everyone who may sign in.
None of that is your API reference. It is data about your readers, many of whom work for your customers, and it sits wherever your docs vendor decided to put it. When a questionnaire asks about EU residency for your documentation, this is what it is really asking about.
Six questions to ask a docs host
A vendor's data residency page usually tells you where the database is. These six questions get you the rest, and a good vendor can answer each of them in a sentence or two:
- Where are the spec, the pages and the uploaded images stored?
- Where do page views, search terms and feedback end up, and how long are they kept?
- Does the Try it console call my API directly, or through your servers?
- Which services run outside the region, such as sign-in, email or the edge network?
- Is the EU region available on every plan, or only with an enterprise contract?
- Can a workspace move to another region later, and how does that work?
Two of them deserve a second look. Almost every hosted product runs a few shared services in front of its regional data, so the fourth question is really a request for a published list with a location next to each service. A blanket promise that everything stays in Europe is not an answer to it.
The fifth question decides how early you can close the topic. When residency is tied to an enterprise contract, a small team either pays for a tier it doesn't need or waits until its first large customer forces the decision.
The leak you added yourself
Not every gap belongs to the vendor. There's a good chance someone on your team pasted an analytics snippet, a chat widget or a feedback tool into the portal header at some point. Each of those reports your readers' visits to wherever its own provider stores data, so a portal hosted in Frankfurt can still send every page view to another continent.
So list every script your portal loads before the questionnaire arrives. The list is usually short, and writing it down now is far easier than reconstructing it under a deadline.
In Routebase
Run the thirty-second test on a Routebase portal and the Try it request goes to your API's host. The console sends every request from the reader's browser directly to your API, so a reader's token never passes through Routebase. Your API needs a cross-origin rule for the portal's domain for that, which is the same rule any browser client of your API already needs.
Everything else stays in the region you choose when you create the workspace. The EU region runs in Frankfurt and is available on every plan, from Free to Enterprise. Each region is its own deployment with its own database, file storage and background jobs, and published portals are served from it on their own hostname or on a custom domain.
Page views and search terms are counted per page and per day in that region. Raw IP addresses are never stored, and the analytics records are deleted after 180 days. Ratings and feedback live in the same regional database.
The shared services in front of both regions are listed with their locations on our data residency page. The guide on publishing and hosting API documentation covers the practical side, from subdomains and custom domains to versions you can take back.
Run the test today
Open your docs, open the network tab and press Try it. If the request goes to your own API, you can already answer the hardest line of that questionnaire. If it goes somewhere else, you now know which question to ask your vendor first.