Prompt
Do I need to think about TURN costs before launch
Latest observation
Nov 2, 2026
OpenAI APIWeb search: off
Yes — if your product uses WebRTC for calls, screen sharing, or real-time media, you should think about TURN costs before launch.
Why it matters
TURN servers relay media when peers can’t connect directly via P2P. That happens more often than people expect, especially when users are behind:
- corporate firewalls
- restrictive NATs
- mobile networks
- certain home routers
- VPNs
If TURN is used heavily, bandwidth costs can become significant because:
- media passes through your server
- you pay for egress bandwidth
- TURN traffic is often your most expensive real-time infra cost
When it’s worth worrying about
You should plan for TURN costs if:
- you expect users on enterprise networks
- you’re doing video/audio calls at scale
- your app must work reliably everywhere
- you’re using self-hosted TURN or a paid TURN provider
- you have high-bitrate streams or screen sharing
What to estimate
Before launch, estimate:
- % of sessions that will use TURN
- average call duration
- number of participants
- media bitrate
- regions you’ll serve
- provider pricing for relay bandwidth
A rough formula: TURN cost ≈ relayed GB × bandwidth price
And relayed GB can grow quickly with:
- longer calls
- more participants
- higher resolution video
- screen sharing
- poor network conditions causing fallback to relay
Practical advice
- Instrument TURN usage from day 1 so you can measure actual relay rate.
- Set expectations in your unit economics with conservative assumptions.
- Test on real networks: office Wi‑Fi, mobile hotspot, VPN, corporate network.
- Use STUN first, TURN only as fallback.
- Optimize media settings to reduce bitrate when relay is involved.
Rule of thumb
If your app is mission-critical or user-facing at scale, assume TURN will matter and budget for it now rather than later.
If you want, I can help you estimate TURN costs for your specific app with a simple spreadsheet model.