# Global Deployments

Rev AI has deployments available outside the United States (US) to help businesses get access to the same Rev AI services, while catering to their data processing and storage requirements. At the moment we support the following regions:

- [The European Union (EU)](#european-union-deployment)


If you are interested in using Rev AI's global deployments, please contact the support team at [support@rev.ai](mailto:support@rev.ai) or reach out to your Customer Success Manager.

## European Union deployment

Rev AI offers data processing and data storage in the European Union (EU). Businesses can now have their Rev AI customer data processed and stored within our EU data center. This data center is physically located in Frankfurt, Germany.

Similar to our US offering, our EU expansion enables our customers and prospects to confidently operate in compliance with GDPR policies. Use the following resources to learn more:

* Rev AI's [GDPR-compliant Data Processing Addendum](https://www.rev.com/legal/data-processing-agreement)
* [Data residency and delineation maintenance between US and EU accounts](https://www.rev.ai/blog/rev-ai-expands-its-presence-in-the-european-union/)


### API endpoint

The base URL for this version of the API is `https://ec1.api.rev.ai/`.

### API availability

The following APIs are available:

- [Asynchronous Speech-to-Text API](/api/asynchronous) at base URL `https://ec1.api.rev.ai/speechtotext/v1/`.
- [Language Identification API](/api/language-identification) at base URL `https://ec1.api.rev.ai/languageid/v1/`.
- [Streaming Speech-to-Text API](/api/streaming) at base URL `wss://ec1.api.rev.ai/speechtotext/v1/stream/`.


### Limitations

The [Asynchronous Speech-to-Text API](/api/asynchronous) has the following additional constraints:

- [Human transcription](/api/asynchronous) is not supported.
- [Custom vocabularies](/api/features#custom-vocabularies) can be supplied only at job submission time via the [`custom_vocabularies`](/api/asynchronous) option. Using pre-existing user-defined custom vocabularies via the [`custom_vocabulary_id`](/api/asynchronous) option is not supported.
- [Language](/api/asynchronous) support may be limited.