> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.deepgram.com/docs/scaling-and-deployment-strategies/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.deepgram.com/_mcp/server.

# Scaling and Deployment Strategies

---

What's Next

* [System Maintenance](/docs/maintaining)
* [Blue-Green Deployment](/docs/blue-green-deployment)
* [Auto-scaling](/docs/autoscaling-best-practices)
* [Metrics Guide](/docs/metrics-guide)
* [Ingress Authentication](/docs/self-hosted-ingress-auth)
* [Using Private Container Registries](/docs/using-private-container-registries)

> Once you have a basic running environment, there are a number of considerations to iterate towards a true production environment. Unlike our hosted offerings, concerns around scaling, maintenance, and security are fully managed by your team. However, we are happy to advise, including the information included in the following guides.

## Docs

- [System Maintenance](https://developers.deepgram.com/docs/maintaining.md): Periodically, you will update configuration files and models, install product updates for your self-hosted deployment, and rotate licensing credentials. A regularly updated system will be both more secure and more performant than a lagging one.
- [Blue-Green Deployment](https://developers.deepgram.com/docs/blue-green-deployment.md): Blue-green deployments are an effective strategy for managing self-hosted updates, especially in cases when backwards compatibility is not maintained and multiple container dependencies exist.
- [Auto-Scaling](https://developers.deepgram.com/docs/autoscaling-best-practices.md): Auto-scaling is a complex endeavor. It is highly dependent on the application deployed, the use case of that application, and business needs and constraints. As such, this guide does not attempt to address all scenarios. A basic understanding of containerized infrastructure is assumed, and specific implementation details are out of scope save for some selected example configurations. References to other materials may also be provided where appropriate.
- [Networking](https://developers.deepgram.com/docs/networking.md): Configure ingress and load balancing for self-hosted Deepgram streaming workloads.
- [Metrics Guide](https://developers.deepgram.com/docs/metrics-guide.md): Monitoring system metrics is an important part of maintaining a healthy Deepgram self-hosted deployment. Metrics can also aid in decision making around scaling and performance concerns. To this end, Deepgram services publish a variety of metrics on exposed endpoints that you can query to determine system health.
- [Ingress Authentication](https://developers.deepgram.com/docs/self-hosted-ingress-auth.md): When deploying Deepgram's self-hosted API container with our  and  guides, your environment will only be accessible from within your private network. This should be sufficient for the majority of enterprise use cases. You can send requests from other services within your private network, or setup a proxy to allow requests from the public internet to pass through your existing application before being passed into your Deepgram self-hosted environment.
- [Redact Usage](https://developers.deepgram.com/docs/self-hosted-redact-usage.md): Configure usage data redaction in your self-hosted Deepgram deployment to enhance privacy and comply with security requirements.
- [Log Formats](https://developers.deepgram.com/docs/log-formats.md): Configure structured log output for self-hosted containers.
- [Using Private Container Registries](https://developers.deepgram.com/docs/using-private-container-registries.md): Mirror Deepgram container images to a private registry (AWS ECR, GCP Artifact Registry) for faster autoscaling and tighter network security.