Xirsys Reviews & Product Details

What I value most about Xirsys is that it solves a problem I didn't even know HR operations had until we started running remote onboarding sessions for clients in Alberta and BC.

Our firm handles end-to-end HR outsourcing, and a big chunk of that is conducting remote onboarding and exit interviews for mid-market manufacturing and retail clients scattered across provinces. We kept running into connection failures—candidates on mobile networks, employees behind restrictive corporate firewalls, or people joining from rural areas with spotty internet. The video would freeze, audio would drop, and my team would spend twenty minutes troubleshooting instead of actually talking to the person. That's a terrible first impression for a new hire.

Xirsys provides the underlying STUN/TURN infrastructure that makes those WebRTC connections actually hold up across messy real-world networks . What I appreciate is the API-first approach—my IT partners integrated the credential system into our existing scheduling workflow without ripping out anything. A concrete example: last quarter we ran exit interviews for a manufacturing client in rural Alberta, and several participants were joining from locked-down corporate devices. Before Xirsys, those sessions would have been a coin flip. Instead, the relay fallback kicked in automatically, and we completed every interview without a single dropped call. The audit trail from the channel usage reports also helped when the client's compliance team asked how we protected PIPEDA-sensitive conversation data during transit.

The pricing model makes sense for a 51-200 person firm like ours. Direct peer traffic stays free, and we only pay for bandwidth when the network genuinely forces a relay . That's not a sales pitch—it's just how it's structured, and it means our monthly spend doesn't spiral when a client has a bad network week.

It's not a flashy platform. Nobody outside IT ever notices it's running. But for an HR ops manager who just needs onboarding calls to work the first time, every time, that invisibility is exactly the point. Review collected by and hosted on G2.com.

My biggest gripe with Xirsys comes down to the administrative overhead when managing access across multiple client environments. We run highly segmented onboarding and exit interview workflows for distinct manufacturing and retail partners in Ontario and Alberta. Because our HR coordinators rotate frequently between these accounts, I need to provision and revoke credentials constantly to maintain PIPEDA compliance.

The platform’s dashboard lacks robust native support for bulk identity management. Last month, I had to manually update permissions for fourteen different temporary HR contractors who were transitioning off a specific retail client's project. Instead of a streamlined SCIM integration or a straightforward CSV upload tool, I had to click through each individual profile to adjust their specific channel and region access. It was tedious, error-prone, and frankly, a waste of my team’s time. We eventually had to loop in our internal IT partners just to build a custom script using the management API, which shouldn't be necessary for a routine offboarding task.

Furthermore, the documentation surrounding regional edge node selection feels remarkably sparse. When we were setting up a new remote onboarding pipeline for a client with staff spread between urban Toronto and rural parts of Alberta, I wanted to ensure we were routing traffic through the most optimal data centers to prevent latency. The technical guides gave me a very superficial overview but didn't provide the deep-dive metrics I needed to make an informed architectural choice. I ended up relying on trial and error during live test calls to figure out which regional configurations actually performed best for our specific geography.

Finally, the reporting interface, while functional for basic bandwidth tracking, is incredibly rigid. I often need to extract telemetry data to prove to a client's compliance officer that we maintained secure, localized routing for sensitive HR discussions. The standard export options don't allow for custom date ranges or specific data filtering. I usually have to pull the raw data and spend time reformatting it in Excel before I can even present it.

None of these are dealbreakers—the underlying relay infrastructure is rock solid, which is why we stay. But the administrative friction and shallow technical documentation definitely create unnecessary speed bumps for an HR operations team that just wants to keep things moving. Review collected by and hosted on G2.com.

Hands down, the best part of Xirsys is its real-time WebRTC media routing plus automatic bandwidth fallback. It’s been a game-changer for running our live virtual training smoothly for our remote recruiter teams at Apex Talent Partners Inc. As the Corporate L&D Program Coordinator, most days I’m delivering onboarding and skill-building workshops for new healthcare staffing recruiters. Many of these team members join from home, and a handful live out in rural spots with unreliable internet. Before we brought Xirsys into our custom training portal, we dealt with constant disruptions: video dropping mid-lesson, whiteboard annotations freezing up, folks getting booted out of breakout rooms right in the middle of HIPAA training. It was such a hassle. Xirsys finds the lowest-latency path for media streams on its own, and gently scales down video quality instead of cutting the connection entirely.

Last month, I led a mandatory HIPAA compliance workshop for 28 new recruiters split across four breakout rooms. Three attendees had really weak home broadband, but their audio and shared whiteboard content stayed active for the full two hours. This reliability saves me roughly three hours every week — hours I used to sink into troubleshooting disconnects, scheduling makeup sessions, and re-recording training footage that got interrupted halfway through.

I also lean heavily on the token access control feature. I can generate short-lived links for each training event, with separate permissions for instructors, participating recruiters, and observers from our audit team. Since we handle sensitive healthcare staffing protocols, it’s non-negotiable to restrict who can join live sessions and access recorded training materials.

One nice surprise I didn’t expect is its detailed session telemetry logs. The tool keeps track of each attendee’s connection health, join time, and stream status. When our internal compliance team needed confirmation that every recruiter stayed for the full HIPAA training, I pulled this telemetry report from Xirsys to cross-check against our LMS attendance records. Having this second source of proof checked all the audit boxes, and I didn’t have to chase people down for screenshots or manual sign-in sheets after the session wrapped up.

That said, Xirsys is built for WebRTC media infrastructure, so it can’t take over our core learning workflows. We still keep our curriculum, quizzes, and completion certificates in our dedicated L&D platform. Even with that boundary, it fixes our biggest pain point: unstable live video that derails required compliance training and piles on extra work. It keeps breakout discussions, whiteboard collaboration and live instruction running reliably for our distributed recruiter group. That frees me up to focus on what I’m actually here to do: build new training content for healthcare staffing, lay out quarterly upskilling plans, and keep our virtual workshop calendar on track. Review collected by and hosted on G2.com.

For all the reliability Xirsys brings to our live training streams, it has some frustrating gaps that regularly add extra work to my plate at Apex Talent Partners Inc. As the L&D Program Coordinator, I run a lot of HIPAA compliance and recruiter skill workshops, and the biggest pain point is that it doesn’t hook up cleanly with our existing L&D platform. It only handles the WebRTC media layer, so there’s no native way to push session attendance, connection logs or recording metadata straight into our training management system. Last month, I hosted a three-hour compliance training for 31 new recruiters. Once the session wrapped, I had to manually export Xirsys telemetry data, clean it up, and cross-reference every attendee against our LMS roster one by one. That manual matching ate up nearly two hours of my afternoon, time I’d set aside to draft our next onboarding module.

I also struggle with its very basic alerting for bandwidth overages. We don’t get custom, early warnings tied to individual training events. If a big workshop with dozens of recruiters burns through our allocated relay bandwidth, we only get a generic email after we’ve already gone over the limit. That’s stressful for us because we schedule back-to-back training days, and unexpected overages can disrupt the afternoon sessions before I even realize what’s happening.

Another downside is that its admin dashboard is built for devs, not L&D folks. A lot of the metrics and token settings are buried in technical menus. If I need to pull a quick audit report for our healthcare compliance team, I have to dig through raw connection logs instead of picking a pre-built compliance template. I can’t quickly filter records just to show who joined, stayed for the required duration and never lost their connection.

One annoying, unplanned hassle I’ve run into is how it handles breakout room media tracking. It captures stream activity for the main room, but once learners split off into separate breakout groups, the logs don’t clearly label which attendees were in which group. When our audit team asked to verify small-group discussion participation for a recent HIPAA workshop, I had no straightforward way to prove who was present in each breakout session. I ended up asking each breakout facilitator to send me separate handwritten sign-off notes.

Xirsys is solid at keeping video and audio streams stable, but it never was built to plug into a full learning delivery workflow. I still maintain a separate spreadsheet to tie Xirsys session IDs to our training rosters, completion requirements and audit checklists. These limitations pull me away from my core L&D work: building recruiter training content, mapping out our quarterly upskilling schedule, and making sure all our mandatory healthcare staffing compliance training stays on track. Review collected by and hosted on G2.com.

As Retail Operations & Vendor Partnership Manager at HomeNest Retail Group, the real-time edge routing and failover controls within Xirsys stand out as our most valuable feature, especially for our live product demo streams and in-store omnichannel feeds we run for home goods promotions. We host regular live selling sessions that link our online shopfront to physical store displays, and any disruption to the media stream can cut into seasonal promotion windows and disappoint wholesale vendors tuning in to view our featured product lines. Xirsys’ intelligent relay selection automatically redirects traffic to alternate nodes if one route degrades. During our spring kitchenware launch stream, more than 12 wholesale partners joined the broadcast simultaneously, and the system rerouted connections seamlessly when our primary uplink had brief packet loss. This automated failover setup eliminates roughly three hours weekly of manual testing and emergency route reconfiguration that our team previously handled before and during each live retail event.

I also value how its granular access token system lets us compartmentalize stream access for different vendor groups. We often run private preview feeds ahead of major sales drops, where only selected suppliers can view unreleased home goods inventory. I can generate short-lived, role-specific tokens for each vendor cohort, revoking access instantly once the preview window closes without touching our core broadcast setup. This level of control keeps unreleased product imagery from leaking before the scheduled merchandising date, a constant risk when sharing broadcast links broadly over email.

An unexpected benefit we found through ongoing use is its consistent performance across our mixed network environment. Our warehouse and retail floor run on separate Wi-Fi subnets with inconsistent bandwidth. Many competing WebRTC platforms struggle to maintain stable connections between these zones, but Xirsys negotiates peer connections reliably across our fragmented local network. This reliability meant we could run impromptu walkthrough streams straight from the warehouse floor for suppliers, showing stock condition and packaging quality without relocating gear to a dedicated high-speed office space.

Our lean retail group does not employ dedicated IT staff, and the REST API hooks let our developer contractor tie stream logs into our inventory dashboard. We pull connection metrics alongside stock levels to see which live demos drove vendor interest and pre-order commitments. It is not built to replace our inventory or merchandising scheduling platforms, so we still feed stream performance data manually into our product launch trackers. Even with that limitation, Xirsys fills a critical gap for our omnichannel live selling pipeline. It keeps our vendor-facing live media feeds stable, simplifies secure access management for confidential previews, and removes the stress of last-minute connection troubleshooting during our busiest seasonal retail promotion cycles. Review collected by and hosted on G2.com.

While Xirsys delivers dependable relay services for our vendor live streams at HomeNest Retail Group, its native dashboard analytics lack the tailored segmentation we need to tie streaming activity to our retail merchandising goals. As Retail Operations & Vendor Partnership Manager, I need to isolate viewer data by wholesale supplier, product category, and preview event, so I can gauge which home goods lines spark the strongest pre-order interest. The built-in reports only show aggregate connection counts, session durations, and node usage. During our fall bedding preview event, 18 vendors joined across three separate private streams. I could not filter metrics to see which supplier logged in, how long they viewed our linen assortment, or whether they stayed through the order terms segment. I had to cross-reference exported connection IDs against my vendor sign-up log in a spreadsheet, matching each session manually. This sorting work ate up more than three hours of my week that I would otherwise allocate to finalizing launch schedules and confirming stock allocations.

I also find its access management workflow cumbersome when we run overlapping preview sessions for multiple product lines. Each stream’s token settings live in isolated panels, with no bulk editing tool to adjust expiry windows or permission rules across several active broadcasts at once. When we shifted our holiday decor preview schedule earlier this year, I needed to shorten the validity window for seven separate vendor streams. I had to open each entry one by one to regenerate tokens and send updated links out, which created delays and raised the chance that a supplier might receive an expired access link by mistake.

Another recurring pain point is the limited alerting framework. We only receive generic notifications for total outages, with no tiered warnings for subtle quality drops such as rising latency or jitter. These gradual degradations often hurt viewing experience long before a full disconnect triggers an alert. During one cookware preview, several vendors reported choppy video halfway through the stream, but our team received no signal until the relay node failed completely. By then, many suppliers had already left the session, hurting our chances of securing early bulk commitments.

One small positive takeaway from these gaps is that we created a standardized event log template for every vendor preview. We log invite lists, token expiry times, and product categories in advance, which helps our team quickly troubleshoot access issues and organize exported connection data later. Since our retail group operates without dedicated IT staff, we cannot build custom webhooks to feed granular alerts and segmented logs into our inventory dashboard. If Xirsys added tag-based viewer segmentation, bulk token controls, and latency threshold alerts, it would align far better with our seasonal merchandising workflows. As it stands, these shortcomings force us to layer manual tracking on top of every stream, adding administrative overhead right when our product launch calendars are most tightly packed. Review collected by and hosted on G2.com.

What I appreciate most is this consolidated account panel that bundles identity, billing and plan controls into one simple tab set. Having user credentials, company metadata and subscription limits in a single view saves me roughly three hours each week, because I don’t jump between disjointed screens when refreshing access credentials for our product engineering team, and it keeps our usage logs aligned with our CCPA and TCPA contact-data audit requirements.

I’m Noah Ohob, RevOps Manager at Vertstack Technologies in Austin. After migrating off Salesforce to Attio, we track PLG product usage, partner relationships and inbound lead signals, and Xirsys handles the WebRTC STUN/TURN connectivity layer for our in-app real-time collaboration widgets that our customers use for demo sessions and support calls. Before Xirsys, our prior real-time infrastructure tool split account identity, credential rotation and plan quota tracking across separate dashboards. Every time our engineering team rolled out a new PLG feature with live video chat, I had to cross-check billing thresholds and reset secrets in multiple places, which slowed our QA cycles. This account dashboard streamlines that whole workflow. When we rolled out a partner-exclusive collaboration module last quarter, I pulled up this page, confirmed our free tier channel limits, updated our business contact details for billing alerts, and cycled the main account password without leaving the account view. The toggle between Account, Billing and Plan makes it easy to validate capacity before we push new real-time features live to our customer base.

I rely heavily on how this account page links directly to the Connect and Analytics modules on the sidebar. Once our company and user identity are saved here, all the connection channels and usage reporting inherit this account context automatically. That means every WebRTC session log ties back to our verified Vertstack account, which simplifies audit reviews when we process CCPA deletion requests for customer interaction data. The pencil edit icons next to email and password make quick credential rotations painless; I don’t have to work through a long setup wizard when handing a channel over to a backend developer.

An unexpected benefit I’ve discovered is how simple it is to catch quota risks early. A few weeks back, our engineering team was ready to launch a broad rollout that would have spiked relay traffic and hit our channel cap. I hopped to the Plan tab, reviewed our limits, coordinated with product to throttle the rollout in phases, and avoided a sudden outage that would have broken live support sessions for our enterprise accounts. Previously, quota warnings only landed in delayed emails, which created risk during busy sales quarters. This straightforward layout also makes it easier to onboard junior ops teammates; they can quickly locate where to review plan terms and update account details without constant hand-holding from me.

Suggestions: I’d love built-in edit history for all account changes right on this screen. Role-based sub-accounts would be extremely valuable so I can create restricted logins for engineers without sharing the primary company credentials. I also want usage-threshold webhooks that feed our Attio workflow, plus native retention labels for connection logs to auto-expire customer session data per our CCPA policy. Review collected by and hosted on G2.com.

My biggest frustrations with Xirsys boil down to the lack of granular change logging on the account panel, no role-separated sub-accounts, and reactive quota alerts that leave our RevOps compliance workflows exposed. The account tab only shows static contact and plan details; there is no built-in history showing when someone updated the email, rotated the main password, or modified company metadata. Last month our backend engineer updated our account contact email for billing notifications, and I had no native way to pull a timestamped record of that edit. Since we have to maintain audit trails for CCPA and TCPA compliance, I was forced to manually log the change in our Attio workflow, eating up nearly three hours I had reserved for processing customer deletion requests. If we receive a formal data inquiry, gaps in this modification trail create unnecessary compliance risk for our customer session and contact data.

I’m Noah Ohob, RevOps Manager at Vertstack Technologies in Austin. We moved away from Salesforce and run Attio to track PLG usage and partner relationships, and Xirsys powers the STUN/TURN relay for our in-app demo and support video widgets. The permission model is a major bottleneck. There is no limited reviewer or engineer-only sub-account option. When our dev team needs to check channel usage or grab fresh TURN credentials, the only option is to hand over our primary master account login. That means anyone with access can alter account contact details, billing settings, or reset the main password. I avoid sharing it as much as possible, which creates bottlenecks: developers message me repeatedly during sprint cycles to fetch secrets, slowing our product release cadence. We cannot scope access so engineers only see their assigned channels without touching core account identity settings.

I’m also disappointed by how the quota notification system works. Alerts only send delayed emails once we have already exceeded bandwidth limits, and there are no configurable pre-threshold webhooks we can pipe into Attio. During a partner launch a few weeks back, our relay traffic climbed fast and hit the hard cap before we got the notification. Our live demo sessions went offline mid-meeting with a strategic BD prospect, and sales had to pivot to Zoom, hurting that deal momentum. The analytics also roll up hourly, so we cannot get near-real-time session metrics to forecast consumption ahead of time. That makes it tough for me to forecast usage and budget alongside our sales pipeline.

There is also no per-channel retention tagging for relay metrics. All usage logs follow one global retention rule, and I cannot mark session data tied to certain customer accounts to expire sooner per our CCPA schedule. Every time we process a deletion request, I have to open a support ticket to request targeted cleanup, which adds days to our response timeline. There is also no native integration to push account events or usage events into our CRM stack. I cannot trigger Attio automations when a partner channel spikes in traffic, so we miss chances to flag high-engagement accounts to our customer success team.

Suggestions: First, add an immutable edit log right on the account page for every change to email, password, and company fields. Second, introduce scoped sub-accounts with granular permissions, so engineers can manage channels without access to billing and primary identity settings. Third, add customizable percentage-based threshold alerts with webhooks that feed into Attio. Fourth, add channel-level data retention rules so we can align session metric expiration with our CCPA obligations. Finally, expose an event API for usage spikes and credential rotations, to trigger our internal RevOps workflows automatically. Review collected by and hosted on G2.com.