OpenAI customers that have an Enterprise agreement can enable Data Residency after executing an amendment with OpenAI. Please note that for data residency in Europe, customers must also be eligible for Zero Data Retention.

Your requests and data for eligible endpoints and models will always be processed by OpenAI services running in the relevant region. If your request is to an Endpoint that requires data persistence to function, such as /v1/batches, then that data is always persisted in data centers within the region, to the extent supported.

Some non-sensitive data, such as billing or usage analytics, will be processed and stored outside Europe.

The following models and API services are eligible for Data Residency today for the regions specified below.

* EU Region support is contingent on Customer being approved for Zero Data Retention for the applicable endpoints

** Zero Data Retention for image inputs is not included in standard Zero Data Retention and requires approval for enhanced Zero Data Retention.

*** For more details about Zero Data Retention in both our Completions API and Responses API please refer to the table in Default usage policies by endpoint.

To get started, please reach out to your account representative at OpenAI, or get in touch with us here.

Create a new project and select your desired region as the geography. Resources, such as inference engines or file storage under that Project, reside in that region. You cannot migrate an existing Project between regions.

For Europe, use https://eu.api.openai.com as your base URL instead of the default endpoint. All prompts and completions flow only through EU-based GPU infrastructure, and file storage (for features like Batch API) is in Azure Blob Storage geographically located within Europe. Metadata (e.g., billing, organization details) is still stored in the US.

If you send requests from an EU-located Project’s credentials to the US endpoint, you'll see an error. Ensure you use the correct endpoint (api.openai.com for US or eu.api.openai.com for Europe).

Yes. Your Organization can contain Projects in the US and Projects in Europe at the same time. Traffic for each Project must route to the corresponding endpoint.

We strive for parity between our US and European regions. However, some capabilities—such as alpha and beta releases—may become available in the US first. Over time, we plan to align features as closely as possible.

You will have separate API keys for each region's Projects. The keys for a US-region Project won’t work on the Europe endpoint, and vice versa.

We're currently exploring the possibility of expanding to additional regions. If you have feedback or a strong need for expansion in a specific region, we’d love to hear from you - feel free to contact our team!

No. Your usage will be priced similarly across the US and Europe.

Yes. Scale Tier is fully supported. Rate limits in the Europe region match those in the US.

Inference is restricted to the countries in the EEA (European Economic Area) plus Switzerland.

We're currently exploring the possibility of providing European Data Residency without requiring ZDR. If you have feedback or a strong need for this capability, we’d love to hear from you—feel free to contact our team.

Yes, Europe-based users should experience a noticeable reduction in request latency compared to using US-based endpoints. This improvement is designed to bring response times more in line with those of US-based customers through a reduction in geographical latency.