Skip to main content

​
Regions

Deploy to the region closest to your users. See Regions for all available endpoints.

​
Environment variables vs livekit.toml

We prefer environment variables for configuration where possible. Set LIVEKIT_URL, LIVEKIT_API_KEY, and LIVEKIT_API_SECRET in your environment — no livekit.toml required for those. Unlike LiveKit Cloud, there is no one-to-one project restriction. You can define multiple agents under a single project. However, each agent requires its own livekit.toml file because the lk agent deploy command reads the agent ID from it. This is a limitation in the underlying LiveKit CLI — if a future CLI release supports setting the agent ID via flag or environment variable, we’ll adopt it. For multi-agent projects, use the --config flag to point at different TOML files: 
lk agent deploy . --config agent-a.toml
lk agent deploy . --config agent-b.toml

​
Multiple environments

Use separate API keys for dev, staging, and production environments. Each key operates independently.

​
Log access

Stream logs from your running agent: 
lk agent logs <agent-id>
Log forwarding to third-party services (Datadog, Sentry, CloudWatch) is coming soon.

​
Custom networking

VPC peering and private endpoints are not available yet. All agent traffic routes over Telnyx’s network.