Deepgram self-hosting clears FIPS 140-3 for regulated deployments
- Source
- x.com
- Date
For regulated buyers, the speech AI eval often ends on one question: "Is the cryptography FIPS validated?" If the answer is no, the on-prem deployment is dead. No matter how good the models are. We just changed the answer. 🧵
Deepgram self-hosted now runs in a FIPS 140-3-compliant configuration. Full online path: API, Engine, and License Proxy, plus FIPS-encrypted models. Built on Chainguard's FIPS-validated crypto module.
Turning it on is a config change Same API, same deploy, same Nova models. No difference in performance vs non-FIPS.
The old tradeoff was compliance OR accuracy. Pick a weaker vendor that clears FIPS, or give up on-prem. Now you deploy the models you actually want and still clear the federal gate. No separate SKU.
Context
Deepgram offers a self-hosted configuration for environments requiring FIPS 140-3 cryptography. Its deployment documentation makes the setup requirements concrete: use the designated FIPS container images, enable FIPS mode for each service and load compatible encrypted model files. Installing the special images alone does not enable the mode.
This also changes connection requirements. The FIPS API image accepts TLS 1.3 and rejects TLS 1.2, so older clients or intervening proxies can fail to connect. The deployment option therefore requires checking the complete connection path, alongside the service configuration.
Checking sign-in…
Loading comments…