> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/administration/regional-hosting.md).

# Regional hosting

Choose US, EU, UK, Canadian, or Australian hosting for your Felt workspace. Learn which data stays in your chosen region.

{% hint style="success" %}
Available on the Enterprise plan. [Talk to sales](https://felt.com/sales)
{% endhint %}

Regional hosting lets you choose where Felt stores your workspace's data. Choosing a region helps you meet data residency rules and can speed up loading for people near it.

{% embed url="<https://www.youtube.com/watch?v=-0Krvkk7Srs>" %}

## Available regions

Felt stores regional data in Amazon Web Services (AWS).

| Region         | AWS region               |
| -------------- | ------------------------ |
| United States  | us-west-2 (Oregon)       |
| European Union | eu-central-1 (Frankfurt) |
| Australia      | ap-southeast-2 (Sydney)  |
| United Kingdom | eu-west-2 (London)       |
| Canada         | ca-central-1 (Montréal)  |

New workspaces use the United States region.

## Set the hosting region

1. Click your workspace name in the sidebar, then click **Workspace settings**.
2. Click the **Workspace** tab.
3. In the **Hosting region** section, select a region under **Set hosting region**.
4. Click **Change region** to confirm. Data created after the change is stored in the new region.

{% hint style="warning" %}
Data already in Felt stays in its original region when you change the hosting region. To move it to the new region, email <support@felt.com>.
{% endhint %}

## What's stored in the region

Felt stores this data in the hosting region you choose:

* Uploaded data files
* Features
* Tiles
* Derived statistics
* Data created by analysis
* Search indexes

Wherever your workspace is hosted, Felt stores and handles some data in the United States:

* Account and user details
* Subscription and billing records
* Item metadata and sharing settings
* Annotations
* Felt AI conversations

Geocoding, routing, Global Library layers, and Felt AI requests are also processed in the United States. Felt AI runs through Amazon Bedrock in US regions. To keep everything in your own AWS account, see [Self-hosted deployment](/administration/self-hosted-deployment.md).

## Security in every region

Felt applies the same security controls in every region, including its SOC 2 Type 2 controls. Each AWS region has several physically separate Availability Zones, each with independent power, cooling, and networking to protect against failures. For Felt's security practices and how to request the SOC 2 report, see [Security and privacy](/administration/security-and-privacy.md) and [Felt's security page](https://felt.com/security).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.felt.com/administration/regional-hosting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.