Access model
All platform interaction is through thelk CLI and the Telnyx Portal. There is no direct access to underlying infrastructure (no kubectl, no SSH).
What Telnyx manages
- LiveKit SFU (media server)
- SIP service (built-in telephony)
- Agent container runtime
- Autoscaling
- TLS/SSL termination
- Load balancing
- Health checks and rolling deploys
What you control
| Capability | How |
|---|---|
| Agent code and Dockerfile | lk agent deploy . |
| Secrets | lk agent deploy --secrets / lk agent update-secrets |
| Rollback | lk agent rollback |
| Logs | lk agent logs |
| Phone numbers | Telnyx Portal |
| SIP connections | Telnyx Portal |
| Model selection | Telnyx plugin or BYOK |
Key differences from LiveKit Cloud
- Telephony is native — No third-party SIP provider needed
- Models via plugin — Use
livekit-plugins-telnyxor BYOK, not LiveKit Inference - Portal — portal.telnyx.com, not cloud.livekit.io
- Billing — Single Telnyx invoice for compute, models, and telephony
- Regions — Telnyx data centers (see Regions)