Deepgram's Australia Endpoint Is Now Generally Available

Today, the Deepgram Australia endpoint is generally available to every customer. Any organization with Australian data-residency requirements, whether based in Australia or serving Australian users from abroad, can now run speech-to-text, text-to-speech, and Voice Agent workloads on Deepgram, with audio processed and stored inside Australia, using the same API, models, and SDKs available on our US and EU endpoints.

Australia has been among the most-requested regions from our customers, with demand concentrated in healthcare, financial services, legal technology, and government. This launch is a direct response to that demand.

For regulated industries, this removes a long-standing constraint. Under the Australian Privacy Principles (APP 8), an organization that discloses personal information overseas remains accountable for how that information is handled downstream. Health data carries a stricter obligation, as the My Health Records Act requires that it be processed within Australia. Government and critical-infrastructure work adds further onshore requirements under the Hosting Certification Framework and the Security of Critical Infrastructure Act. For these buyers, where voice data is processed and stored is a procurement requirement.

Until now, teams building on Deepgram in Australia could route audio to our Global or EU endpoints, which introduced cross-border exposure, or deploy Deepgram self-hosted within their own Australian infrastructure, which requires the engineering capacity to operate it in production. The Australia endpoint provides a third path. It is a fully managed, fully onshore option that uses the same Deepgram Voice AI API as our Global or EU endpoints.

The Australia endpoint is production-ready and available to all customers, with no waitlist and no enterprise-only restriction. It runs in AWS’s ap-southeast-2 region (Sydney), and pricing matches our Global and EU rates at launch.

Adoption requires a single change. Point your integration at api.au.deepgram.com, and your existing API keys and SDK integrations continue to work. There is no separate account, no migration project, and no change to how you call the API.

Your audio, transcripts, and speech output are processed and stored in Australia, with both storage and inference in-country.

The residency commitment is specific. For speech-to-text and text-to-speech on Deepgram models, both storage and inference happen on Australian infrastructure (AWS ap-southeast-2, Sydney), not storage alone. Two boundaries are explicit, so compliance teams can review the full picture:

• Voice Agent LLM. If a Voice Agent uses a managed third-party LLM (the reasoning step), that provider processes the request outside Australia. Confirm the provider's residency and processing guarantees independently; Deepgram runs listen and speak in-country.
  
• Operational metadata and billing are processed in the US.
  

For the strictest frameworks (such as the My Health Records Act, where all processing activities, including access, must occur in Australia), opt out of model improvement (mip_opt_out=true). That keeps customer content out of any training workflow, so no content is accessed or processed across Australian borders for any purpose.

The Australia endpoint provides the same API surface as our Global and EU regions. Speech-to-text is available at /v1/listen and /v2/listen, text-to-speech at /v1/speak, Voice Agent at /v1/agent/converse, and text intelligence at /v1/read.

Deepgram model availability is at parity with our EU endpoint, so the speech-to-text and text-to-speech models teams already run on Deepgram are available in Australia without changes.

Voice Agent is the workload where residency matters most. A real-time, two-way voice agent streams customer audio continuously, which places the question of where that audio is processed at the center of any security review. Running the agent on the Australia endpoint keeps Deepgram's speech-to-text and text-to-speech onshore. The agent's LLM step runs on the model provider you select or provide, and that provider determines where the reasoning is processed. Confirm the provider's residency and processing guarantees independently.

Set the base URL to the Australia endpoint in your existing client. The rest of your code stays the same.

from deepgram import DeepgramClient, ClientOptionsFromEnv

# Point your existing integration at the Australia endpoint
deepgram = DeepgramClient(
    "YOUR_API_KEY",
    ClientOptionsFromEnv(url="https://api.au.deepgram.com"),
)

Voice Agent connections use agent.au.deepgram.com. Both endpoints route all customer payloads through Australian infrastructure.

No other major voice AI provider offers a fully sovereign, managed endpoint in Australia. Some providers store data in-region but run inference elsewhere, so processing can still cross borders. Others offer an in-country option only through infrastructure the customer has to deploy and operate. Deepgram performs both processing and storage in-country, fully managed, with no infrastructure for the customer to run.

That distinction matters most in healthcare, financial services, legal technology, and government-adjacent sectors, where an onshore guarantee separates a deployment that passes review from one that stalls. Deepgram holds SOC 2 Type I and Type II certifications, and the Australia endpoint extends that compliance posture with in-country processing and storage.

The Australia endpoint is live now and available to every Deepgram customer.

• Read how regional endpoints work →
  
• Australia endpoint quickstart →
  
• See the EU endpoint, our first regional launch →
  

To move a workload to Australia, update your base URL to api.au.deepgram.com, or contact your account team to plan the transition.

The Australia endpoint is part of a broader expansion. Over the past year, Deepgram has extended where voice AI runs, from Dedicated deployments to our EU endpoint and now Australia, while continuing to expand the languages our models support. The goal is consistent: Deepgram should run where your business runs, in the language your customers speak. Australia is the next step, and more regions will follow.