Data Residency

Overview

Murf offers data residency through isolated regional environments for the streaming & websocket TTS API. Enterprise customers can choose where text and audio are processed, helping meet regulatory, contractual, or internal governance requirements—while still delivering ~130 ms latency.

Important choice:

• Use a regional endpoint when you need strict data residency.
• Use the global router when you want best-effort low latency for a worldwide audience (traffic is routed to a nearby region and may cross borders).

Regional vs Global: which should you use?

Regional endpoints (strict control - recommended for residency)

• By default, all customer account data (including user profiles, usage, and billing information) is hosted in the United States. However, with data residency enabled, text input, audio synthesis, and processing will be confined to the selected regional environment.
• Ideal for regulated workloads and contractual residency requirements.

Global router (latency-first - not for strict residency)

• https://global.api.murf.ai/v1/speech/stream automatically routes requests to an available, geographically close Falcon region for performance and availability.

• Because routing can select any available region, do not use the global URL if you require strict residency.

Available Regions

Murf offers data residency for Falcon TTS in 11 regional environments:

Access and Concurrency Rules

Note : Even with data residency enabled, your Murf account metadata (e.g., profile, usage stats) will continue to be stored in the United States. However, your input text, generated audio, and intermediate processing data will remain within your chosen regional environment.

Developer Integration

When using data residency, simply call the regional endpoint that corresponds to your desired jurisdiction.

Example:

1
import requests
2
3
# Global URL
4
response = requests.post(
5
    "https://global.api.murf.ai/v1/speech/stream",
6
    headers={"api-key": "<YOUR_API_KEY>"},
7
    json={
8
        "text": "Hi, How are you doing today?",
9
        "model": "FALCON",
10
        "voiceId": "Matthew",
11
        "multiNativeLocale": "en-US"
12
    },
13
    stream=True
14
)
15
with open("global_audio.mp3", "wb") as f:
16
    for chunk in response.iter_content(chunk_size=1024):
17
        f.write(chunk)
18
19
#  Regional URL
20
response_india = requests.post(
21
     "https://in.api.murf.ai/v1/speech/stream",
22
     headers={"api-key": "<YOUR_API_KEY>"},
23
     json={
24
         "text": "Hi, How are you doing today?",
25
         "model": "FALCON",
26
         "voiceId": "Matthew",
27
         "multiNativeLocale": "en-US"
28
     },
29
     stream=True
30
 )
31
with open("india_audio.mp3", "wb") as f:
32
     for chunk in response_india.iter_content(chunk_size=1024):
33
         f.write(chunk)

For Enterprise customers, region-specific API keys will be provisioned by your Murf account manager.

Data Residency Architecture

With Murf’s isolated Falcon TTS environments:

• Text and audio data remain confined to the selected region for processing.
• Customer account and billing data are centralized in the United States.
• Network routing ensures requests to regional URLs stay within that jurisdiction.
• Encryption in transit is maintained globally via HTTPS.

This architecture balances regulatory compliance, latency optimization, and operational transparency.

Compliance & Security

Data residency environments extend Murf’s core security and compliance framework, including:

• GDPR Readiness : Murf’s processing framework aligns with GDPR’s regional data processing requirements.
• SOC 2 Compliance : Murf follows strict standards for data confidentiality, availability, and integrity.
• Encryption at Rest & In Transit : All content is encrypted using industry-standard AES-256 and TLS 1.2+.
• Region-Specific Isolation : Enterprise accounts can restrict Falcon TTS processing to a specific jurisdiction.

FAQ