Self-hosted TURN
You manage server provisioning, ports, TLS, credentials, DNS, monitoring, failover, global regions, capacity, and bandwidth surprises.
Self-hosting Coturn can work for prototypes. Production WebRTC needs global coverage, user-aware routing, DNS resilience, monitoring, credential management, usage reporting, bandwidth planning, and support. Xirsys packages that into a managed STUN/TURN hosting service.
A production relay layer needs to work when users are on mobile networks, corporate firewalls, VPNs, symmetric NATs, and locked-down Wi-Fi. Xirsys handles the operational layer so product teams can focus on the application.
You manage server provisioning, ports, TLS, credentials, DNS, monitoring, failover, global regions, capacity, and bandwidth surprises.
The 30-day trial provides all 12 regions, user-geo routing, API and static credentials, and up to 2 channels with individual usage reports. Paid plans keep those features active with higher channel capacity, dashboard analytics, and production support.
A single VM can be enough for controlled tests, local demos, and narrow internal use cases.
Start with the full relay network and production features for 30 days. Paid plans keep access active with plan-based channel and WebSocket capacity, high-availability routing, unlimited STUN, and operational tooling for real customer traffic.
Often, yes. TURN helps when client networks cannot establish direct peer paths. A public cloud server does not remove restrictive client-side NATs, proxies, firewalls, or UDP-blocking networks.
No. TURN relays connectivity fallback traffic. It does not replace your media server, SFU, SDK, app backend, or AI agent runtime.
Start with expected sessions, stream type, duration, and estimated relay percentage. Use the Xirsys calculator to size production plans around TURN-relayed traffic rather than every WebRTC session.