September 15, 2026

India Endpoint Now Generally Available

The Deepgram India endpoint (api.in.deepgram.com) is now generally available for customers requiring data processing within India.

Supported APIs

The India endpoint supports the following Deepgram APIs:

Speech-to-Text: /v1/listen and /v2/listen
Text-to-Speech: /v1/speak and /v2/speak
Voice Agent: /v1/agent/converse
Text Intelligence: /v1/read

Configuration

To use the India endpoint, replace api.deepgram.com with api.in.deepgram.com in your SDK or API requests. Your existing API keys and tokens work with the India endpoint.

For WebSocket connections, use the corresponding India URLs:

Speech-to-Text: wss://api.in.deepgram.com/v1/listen
Speech-to-Text (Flux): wss://api.in.deepgram.com/v2/listen
Text-to-Speech: wss://api.in.deepgram.com/v1/speak
Text-to-Speech (Flux): wss://api.in.deepgram.com/v2/speak
Voice Agent: wss://api.in.deepgram.com/v1/agent/converse

For detailed configuration instructions and SDK examples, see our Regional Endpoints documentation. For what Deepgram guarantees about where your data is processed and stored, see Your Data at Deepgram.

September 15, 2026

Deepgram Self-Hosted September 2026 Release (260915)

Container Images (release 260915)

quay.io/deepgram/self-hosted-api:release-260915
- Equivalent image to:
  - quay.io/deepgram/self-hosted-api:1.192.37
quay.io/deepgram/self-hosted-engine:release-260915
- Equivalent image to:
  - quay.io/deepgram/self-hosted-engine:3.131.2
- Minimum required NVIDIA driver version: >=580, open kernel module flavor
  - The minimum driver version has increased this release, up from >=570.172.08. The Engine image is built against CUDA 13, and NVIDIA’s official CUDA 13 support begins with the 580 driver branch. NVIDIA’s documentation states the CUDA 13 minimum as >=580 rather than a specific version.
  - The driver must be the open kernel module flavor, for example nvidia-driver-580-open. The proprietary build of the same version is not supported.
    - On Blackwell hardware the consequence is total: NVIDIA never added Blackwell support to the proprietary 580 branch, so on that build a Blackwell GPU disappears from the system, nvidia-smi reports no devices, and Engine will not start. See Drivers and Containerization Platforms for installation and verification steps.
quay.io/deepgram/self-hosted-license-proxy:release-260915
- Equivalent image to:
  - quay.io/deepgram/self-hosted-license-proxy:1.11.1
quay.io/deepgram/self-hosted-billing:release-260915
- Equivalent image to:
  - quay.io/deepgram/self-hosted-billing:1.14.0-2

FIPS 140-3 Images

FIPS 140-3 images are available for all four self-hosted services, published under the -fips tag suffix:

quay.io/deepgram/self-hosted-api:release-260915-fips
- Equivalent image to:
  - quay.io/deepgram/self-hosted-api:1.192.37-fips
quay.io/deepgram/self-hosted-engine:release-260915-fips
- Equivalent image to:
  - quay.io/deepgram/self-hosted-engine:3.131.2-fips
quay.io/deepgram/self-hosted-license-proxy:release-260915-fips
- Equivalent image to:
  - quay.io/deepgram/self-hosted-license-proxy:1.11.1-fips
quay.io/deepgram/self-hosted-billing:release-260915-fips
- Equivalent image to:
  - quay.io/deepgram/self-hosted-billing:1.14.0-2-fips

These images run OpenSSL’s FIPS 140-3 validated cryptographic provider. Enable FIPS by setting [fips] mode = "enabled" in each service’s configuration. FIPS mode should be enabled only on the -fips images; the standard images do not include the FIPS provider. See FIPS-Compliant Deployment for setup and configuration details.

This Release Contains The Following Changes

NVIDIA Blackwell GPU Support (GA) — Blackwell-generation GPUs are now generally available for self-hosted deployments. See Drivers and Containerization Platforms for driver requirements and Model and GPU Compatibility for which models run on which GPUs.
Flux Forced End-of-Turn — your client can now end a Flux turn on demand rather than waiting for the model to detect the end of speech. Enable it by setting listen_v2 = true and listen_v2_force_end_turn = true under [features] in your API configuration, then send a ForceEndTurn message on an active /v2/listen stream. The resulting EndOfTurn event reports trigger: "manual", and its transcript covers only the audio received before the message. See Force End Turn for details.
Mid-Stream Numeral Configuration for Flux — change numeral formatting during an active /v2/listen stream by sending numerals in a Configure control message, instead of fixing it at connection time. Previously numerals could only be set as a query parameter when the stream opened.
Formatting Improvements — improved reading of German numbers, currency, times, and addresses.
General Improvements — dependency and security updates, and refreshed base images.