Skip to main content

Deepgram Self-Hosted October 2026 Release (261001)

By Steven Van ·

Flux TTS audio is now watermarked, and self-hosted Engine will not start with Flux TTS enabled until the watermarker file and UUID are configured.

Self-hosted Deepgram deployments running Flux TTS need to act before upgrading to release 261001. Flux TTS audio is now watermarked. Deployments must add the watermarker model file (watermarker.<uuid>.dgv2, provisioned alongside the Flux TTS models) and set watermarker_uuid under [flux_tts] in the Engine configuration. Engine will not start with Flux TTS enabled if the watermarker is missing.

  • Images: the release tag is release-261001 for the API, Engine, license proxy and billing services. These match API 1.192.51, Engine 3.135.0, license proxy 1.11.1-1 and billing 1.14.0-3.
  • NVIDIA drivers: the Engine image requires driver version 580 or higher, open kernel module flavor.
  • FIPS 140-3: images for all four services are published under the -fips tag suffix. They run OpenSSL's FIPS 140-3 validated cryptographic provider. FIPS is enabled by setting [fips] mode = "enabled" in each service's configuration, and only on the -fips images, because the standard images do not include the FIPS provider.

The release note links to Deepgram's Numerals documentation. That page covers the feature that converts spoken numbers to digits, and says it works on both Flux STT models, with a different set of supported languages for Flux Multilingual.

Deepgram
Deepgram
Power enterprise voice solutions with Deepgram’s Speech-to-Text, Text-to-Speech, and Voice Agent APIs. Real-time, accurate, and built for scale.
View Deepgram →

Read the original announcement →

Read Deepgram Self-Hosted October 2026 Release (261001) on Creators Toolbox