Same protocol. Different bill.
Pricing models differ: some bill per GB, some sell monthly bundles. Each provider's public list price is shown in the terms they publish, so you can compare against your own traffic.
Provider comparison
| zTurnMonthly TB plan | ExpressTURNFlat monthly plan | CloudflarePer GB, pay as you go | TurnixMonthly bundle + overage | TwilioPer GB, priced by region | |
|---|---|---|---|---|---|
| Price per TB | $5 → $10 | ~$1.80* | $50 | $225 → $750 | from $400 |
| Free allowance | Yes. First month | Yes. 1,000 GB / mo | Yes. 1,000 GB, shared | Yes. 10 GB | No. STUN only |
| Volume discount | Yes. Automatic | No. Flat rate | No. One rate | Yes. By plan size | Not published. Not published |
| Support | Yes. Email, from the team running the relays | Yes. Email support | Yes. By account plan | Not published. Not published | Yes. By account plan |
| Bandwidth cap | Yes. No cap, billed at your rate | Not published. 5 TB included | Yes. No cap | Yes. Bundle, then overage | Yes. No cap |
Dollars per TB of relayed traffic, normalised from each provider's own published list price on 2026-09-16. Billing models differ — each is named under the provider. Where a provider publishes nothing on a row, the table says so rather than guessing. Follow the source links for current figures.
ExpressTURN: The $9 Premium plan includes 5,000 GB. ExpressTURN publishes no overage rate and no pricing above that plan, so the cost of exceeding 5 TB in a month is not knowable from their site.
Checked against:Our pricingExpressTURN (opens in a new tab)Cloudflare (opens in a new tab)Turnix (opens in a new tab)Twilio (opens in a new tab)
How to compare for your app
A per-GB rate only means something once you know how much of your traffic is relayed.
Estimate relayed sessions
Commonly 10–20% of sessions need a relay, and more on corporate and cellular networks. Your own mix is the only number that matters.
Multiply by data per session
Voice uses roughly 25–30 MB per hour in each direction; 720p video about 1 GB. These are estimates from codec bitrates, not measurements.
Check the fine print
Which direction is billed, whether TLS on 443 is included, and whether the regions you need are actually offered.