Test your voice agents with non-production deployments

LiveKit’s non-production deployments allow voice-agent teams to run the same container image, project, and shared secrets as production under separate named environments, reducing the need to maintain duplicate agents while enabling testing of models, prompts, and integrations on real infrastructure. These deployments can be created and managed through the CLI using a `--deployment` flag, sleep when idle to avoid compute costs, and can be targeted for calls through tokens or dispatch APIs, although they require recent Python or Node SDK versions. Unlike production, non-production deployments cold-start on demand, immediately terminate active sessions during redeployment, and do not support rollback, making them appropriate for iterative testing rather than interrupt-sensitive traffic. Deployment-specific behavior or credentials can be selected at runtime through the `LIVEKIT_AGENT_DEPLOYMENT` environment variable, while CI workflows can route branches to staging or production and optionally require approval before production releases. The feature is available on Ship and higher plans, with limits of two non-production deployments per agent on Ship and five on Scale; logs can be used for inspection, while deployment-specific observability metrics are planned for the future.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.