Everything teams ask before putting Xirsys under production WebRTC.
Xirsys is the SDK-agnostic WebRTC connectivity API for apps, media servers, calling SDKs, and AI voice or video agents. These answers cover regions, TURN usage, pricing, credentials, media-server support, and production operations.
How is Xirsys different from a calling SDK or AI-agent platform?
Xirsys does not replace your app layer, calling experience, model provider, or media server. It provides the neutral WebRTC connectivity layer underneath: standard ICE configuration, global STUN/TURN routing, API-issued credentials, static credentials, analytics, and support.
What do you mean by Single Geographic Region for Developer accounts?
Developer accounts are limited to one region for testing. Production accounts include all global regions and automatically route users to the nearest available cluster for lower latency and a 99.95% uptime SLA.
How do I calculate my WebRTC usage requirements?
Only TURN-relayed bandwidth is billed. Direct peer-to-peer STUN sessions do not consume paid relay bandwidth. As a planning baseline, average TURN usage is often around 15%, mobile-heavy applications can land closer to 30% to 40%, and residential ISP audiences may be closer to 5% to 15%.
How does Xirsys pricing work?
STUN connections are unlimited and free. Production plans are based on included TURN bandwidth, with overage rates for traffic above the selected plan. That makes pricing align with real fallback usage instead of every WebRTC session.
What is the default bitrate for video and audio calculations?
The usage calculator uses planning defaults for audio, SD audio/video, and HD audio/video. Actual usage depends on codec, resolution, duration, network conditions, and application behavior, so production teams should monitor real dashboard usage after launch.
What are non-expiring static TURN credentials?
Some media servers and communication infrastructure need long-lived credentials instead of credentials that expire after a short window. Xirsys production accounts include static, non-expiring TURN credentials for registered channels, managed from the dashboard.
Can I use Xirsys with my existing SDK, media server, or AI agent?
Yes. Xirsys returns standard ICE server configuration, so it can work with browser WebRTC, native clients, third-party frameworks, calling SDKs, Kurento, Jitsi, Janus, mediasoup, Wowza, Cisco, and AI voice or video agent workflows that use WebRTC.
What media servers are supported?
Xirsys is standards-based. Any WebRTC-compliant client or media server that accepts ICE server configuration can use Xirsys STUN/TURN credentials, including Kurento, Jitsi, Janus, mediasoup, Wowza, Cisco, browser WebRTC, and native WebRTC stacks.
How do I upgrade, downgrade, or cancel?
There are no long-term contracts for self-serve plans. You can change plans or cancel from the Xirsys dashboard under the Plans page.
Can I pay by check or bank transfer?
Yes. For annual, enterprise, or invoiced plans, contact experts@xirsys.com and the team can help with the right billing path.
Can I have a global access trial?
Contact Xirsys to discuss a production-style trial when you need to test multiple regions, static credentials, or a real deployment architecture before launch.
Is enterprise support available?
Yes. Enterprise customers can discuss custom contracts, volume bandwidth planning, migration support, and production support requirements with the Xirsys team.
Is there an API?
Yes. Xirsys provides a REST API for creating and managing channels, issuing credentials, and integrating STUN/TURN provisioning into automated application flows.
Does Xirsys support HIPAA or GDPR requirements?
Xirsys can discuss compliance requirements, data processing needs, and enterprise agreements with your team. Contact experts@xirsys.com for a compliance-specific review.
Use the calculator or talk to an expert before choosing a plan.
Bandwidth needs depend on audience, stream type, session duration, and network mix. Xirsys can help size usage and design the right credential strategy.