Engineering guides / Realtime communication and P2P engineering

By Arte Soft engineering · 24 October 2026

TURN server cost audit: measure relayed traffic before changing topology

Reducing relay cost starts with understanding which sessions use it and how much data they move. Turning TURN off can make a dashboard cheaper while simply preventing the hardest-to-connect customers from completing a call.

Reconcile application sessions with relay traffic

Join call identifiers, selected candidate types, session duration and relay accounting where available. Separate audio, video and attachment use rather than treating every connection as one cost unit. Check whether bytes are counted on ingress, egress or both in your infrastructure bill. A useful baseline explains the measurement boundary before presenting a per-call number that may combine incompatible counters.

Find out why relay was selected

A relayed path can be necessary for connectivity, deliberately preferred for privacy or accidentally forced by configuration. Inspect policies and representative traces before changing candidate priorities. If direct candidates arrive too late because signaling is broken, fixing that defect may change relay use. If the audience is predominantly behind restrictive networks, a lower relay percentage may be the wrong success criterion.

Distinguish inefficient media from necessary fallback

A long high-bitrate video call costs more than a brief audio call even with the same connection type. Review resolution, frame rate, codec negotiation and whether unused tracks remain active. Do not reduce quality blindly: participants may need screen text to remain readable. Measure the outcome on the task and the network instead of optimizing bandwidth in isolation from the product’s purpose.

Compare operational options honestly

Self-hosted relay and managed infrastructure have different staffing, capacity and incident-response implications. Evaluate geography, reachability, authentication and monitoring alongside data transfer prices. A theoretical saving disappears quickly if a relay outage prevents paid sessions. Cost estimates should use observed traffic with a stated period and separate one-time engineering effort from recurring infrastructure exposure.

Check abuse and credential handling

Long-lived or publicly exposed relay credentials can allow traffic unrelated to your application. Review expiry, allocation limits and how credentials reach authenticated clients. Test what happens when credentials expire during setup and when the service is unavailable. Rate controls should stop abuse without rejecting legitimate reconnects or group-call participants. Keep operational secrets out of client logs and shared audit exports.

Relay audit input pack

  • Bring a stated billing period, relay traffic counters and application session references that can be joined without sharing personal call content.
  • Check whether your cost model counts both directions of traffic and whether it includes infrastructure outside the relay itself.
  • Agree that a proposed saving is acceptable only if the defined connectivity and media-quality checks still pass after the change.

Define a measurable delivery

A cost audit should leave a reconciled baseline, a short list of changes and an acceptance comparison that includes connection success. Arte Soft can discuss realtime engineering through GPT Realtime Assistant and separately labelled Wonek R&D, without claiming a guaranteed relay reduction for your population. Bring billing exports and sanitized session statistics; the result should show which costs are avoidable, which protect reachability and which remain uncertain until more traffic is observed.

Relevant Arte Soft work

Wonek — communication engineering R&D, not a shipped or audited messaging product is our own product or engineering project. It provides context for the work we discuss here; it is not a claim of identical results for every client deployment.

Sources and further reading

Need help with TURN traffic and cost audit?

Send the current app, system or brief, the behaviour you need and your constraints. We can agree a discovery, implementation or repair scope with concrete acceptance criteria.

Discuss this with Arte Soft

Continue reading