Changelog

Deepgram Self-Hosted May 2026 Release (260514)

Container Images (release 260514)

• quay.io/deepgram/self-hosted-api:release-260514

  • Equivalent image to:
    • quay.io/deepgram/self-hosted-api:1.187.0

• quay.io/deepgram/self-hosted-engine:release-260514

  • Equivalent image to:

    • quay.io/deepgram/self-hosted-engine:3.117.0

  • Minimum required NVIDIA driver version: >=570.172.08

• quay.io/deepgram/self-hosted-license-proxy:release-260514

  • Equivalent image to:
    • quay.io/deepgram/self-hosted-license-proxy:1.10.1

• quay.io/deepgram/self-hosted-billing:release-260514

  • Equivalent image to:
    • quay.io/deepgram/self-hosted-billing:1.13.0

Batch Diarization v2 model delivery for new self-hosted deployments

Release 260514 ships Deepgram’s new batch diarization model (v2) to self-hosted. New deployments provisioned through your Deepgram representative will receive only the v2 batch diarizer model on disk by default. To produce diarized output on a fresh deployment, batch requests must specify diarize_model=v2 or diarize_model=latest. diarize=true on its own is pinned to v1; on a 260514 deployment that does not have the v1 model on disk, /v1/listen?diarize=true returns a successful response with no speaker labels — consistent with Deepgram’s longstanding behavior when a requested diarizer model is not present.

Existing deployments retain their v1 batch diarizer and continue to work without changes. To add v2 to an existing deployment, contact your Deepgram representative.

This Release Contains The Following Changes

• Batch Diarization v2 — A new batch diarization model with significantly improved speaker labeling, preferred 3.3× over v1 in side-by-side human evaluation. Strongest gains on contact-center audio (~80% reduction in median Confusion Error Rate vs. v1, ~60% at p95). Compatible with Nova-1, Nova-2, Nova-3, plus enhanced and base batch models; monolingual and multilingual. Not compatible with Whisper. The API response format is unchanged from v1. Batch-only; streaming diarization is unchanged. See Speaker Diarization for details.
• New diarize_model Parameter — Opt into v2 by passing diarize_model=v2 (pin to v2) or diarize_model=latest (recommended; auto-upgrades to future diarizer iterations) on pre-recorded /v1/listen requests. Unrecognized values return 400 Bad Request. Streaming requests reject diarize_model and return 400; use diarize=true for streaming diarization. diarize=true on batch continues to route to v1 to preserve behavior for existing integrations.
• General Improvements — Keeps our software up-to-date.