Everything teams ask before putting Xirsys under production WebRTC.

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.

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.99% uptime SLA.

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%.

You can estimate TURN relay traffic with this equation: number of participants^2 * stream bitrate * total seconds of transmission. For example, a 1-minute one-to-one medium-quality video call using TURN is 2^2 * 512 kbits/s * 60 seconds = 122,880 kbits, or 15.3 MB. You can also use the Xirsys usage calculator.

STUN connections are unlimited and free. Production plans are based on included relay bandwidth, including TURN and relayed data traffic, with overage rates for traffic above the selected plan. That makes pricing align with real fallback usage instead of every WebRTC session.

Xirsys offers a free developer account so teams can try the service, and paid production plans include a 99.99% uptime guarantee and 24-hour ticket support.

Your monthly bandwidth allowance resets on the first day of each calendar month, and unused bandwidth does not roll over. If a paid account exceeds its included bandwidth, overage is calculated by calendar month and charged according to the subscribed plan.

Xirsys sends usage emails after you exceed your plan amount. Overage may be waived if you upgrade before the end of the month to cover the additional usage; otherwise, the card on file is charged at the end of the month. Free developer bandwidth is hard-capped, so relay service stops once the monthly allowance is used until the account is upgraded or the allowance resets.

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.

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.

Yes. You can use any third-party WebRTC client-side framework with Xirsys. 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.

You can call the Xirsys API before each connection to receive valid ICE credentials, or use static TURN credentials from the dashboard when your infrastructure needs non-expiring credentials.

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.

There are no long-term contracts for self-serve plans. You can upgrade, downgrade, or cancel at any time from the Xirsys dashboard under the Plans page.

When you upgrade, your card is charged a prorated amount based on your billing cycle. When you downgrade, unused bandwidth is forfeited and there is no refund available, so Xirsys recommends downgrading at the end of your billing cycle.

Self-serve plans accept credit card payments, including Visa, MasterCard, and American Express. PayPal, Google Wallet, and similar wallet payments are not accepted for self-serve billing.

For annual, enterprise, or invoiced plans, email experts@xirsys.com and the team can help with the right billing path, including check or bank transfer when available for the agreement.

You can update the credit card on file from the Xirsys dashboard. Open the Account section, enter the new card details in Manage Account Billing, and use the Update Card action.

Use the Forgot Password link on the login page to reset your password. You may also reset your password from inside the dashboard.

You can update the name or email address on your account from the Account section of the dashboard. Your ident cannot be changed.

Email experts@xirsys.com to discuss a production-style trial when you need to test multiple regions, static credentials, or a real deployment architecture before launch.

Yes. Enterprise customers can email experts@xirsys.com to discuss custom contracts, volume bandwidth planning, migration support, and production support requirements with the Xirsys team.

Email experts@xirsys.com with questions, concerns, bug reports, or product feedback. The support team will help review the issue and next steps.

Check status.xirsys.com for current service health. You can subscribe from the status page to receive alerts when service incidents or updates are posted.

Check whether the account has used its monthly bandwidth allowance. Free developer bandwidth is hard-capped, so relay service stops after the allowance is used and resets on the first day of the next month.

If you still have bandwidth available, email experts@xirsys.com with your ident, any developer-console errors, and a Wireshark capture if you can provide one.

Xirsys is not taking on application development work, but the team can refer you to trusted development partners if you share your scope of work and budget.

Yes. See the Xirsys IP whitelist documentation for the latest list of Xirsys IPs to allowlist.

Yes. Xirsys provides a REST API for creating and managing channels, issuing credentials, and integrating STUN/TURN provisioning into automated application flows. You can call the /_turn endpoint before each connection to receive an ICE string with valid credentials.

Xirsys is a transmission-only service for live data and does not store any personally identifiable information. In addition, all audio and video data transmitted over the Xirsys service is by default transmitted with end-to-end encryption. For these reasons the Xirsys service is covered by the HIPAA Conduit Exception Rule.

Xirsys offers a 99.99% uptime guarantee, and you can read the SLA policy in the terms of service.