IT Infrastructure Software Resources
Articles and Discussions to expand your knowledge on IT Infrastructure Software
Resource pages are designed to give you a cross-section of information we have on specific categories. You'll find articles from our experts and discussions from users like you.
IT Infrastructure Software Articles
Containers as a Service: Types, Benefits, and Best Software in 2023
AWS re:Invent 2021 Roundup: A G2 Perspective
Site Reliability Engineers and the Software That Supports Them
IT Infrastructure Software Discussions
The honest answer from the review base is: it depends heavily on your starting point. Citrix DaaS is genuinely excellent at enterprise-grade security and centralized management for large, distributed workforces. Whether it's "worth it" for ease of use is a different question, and the reviews are pretty clear on where that breaks down.
From reviews in the virtual desktop infrastructure (VDI) category on Citrix specifically, and the alternatives that come up when teams walk away:
- Citrix DaaS: What reviewers say works: enterprise-scale management, MCS-based VM deployment, multi-authentication support, HDX protocol optimization, and the ability to publish individual apps rather than full desktops. Reviewers at healthcare, financial services, and large IT organizations describe it as the standard for good reason. What reviewers say doesn't work: licensing is genuinely expensive, setup complexity is real, and the end-user experience can degrade with bandwidth issues. If you're an IT team managing a 5,000-person enterprise where security requirements are non-negotiable, the complexity is justified. Does your organization have dedicated VDI administration capacity to configure and maintain it on an ongoing basis, or would it sit partially configured?
- Nerdio Manager: The alternative that comes up most for organizations evaluating Citrix and landing on something different. The High Performer placement on the Enterprise Grid with a 93 satisfaction score versus Citrix's 66 tells a story. Reviewers describe it as delivering the Microsoft Azure security model, centralized policy enforcement, and role-based controls with less operational overhead than Citrix. The catch is that it's Azure-native, so it's not the right answer for organizations that aren't standardized on Microsoft infrastructure. If you're already in Azure, is the reason you're evaluating Citrix because of a feature it has, or because it's what was there before Azure became the default?
- Kasm Workspaces: The alternative that comes up for teams where security is the priority, but the budget or complexity of Citrix isn't justified. Zero-trust architecture, DLP controls, session isolation, and browser-based access without endpoint software. Reviewers describe it as replacing RDP infrastructure with something that's both more secure and easier for end users to access. The enterprise security is structural rather than configurable, which is either a feature or a limitation, depending on your compliance requirements.
- V2 Cloud: Comes up for teams where "enterprise-grade security" means data off personal devices and centralized access control, not configurable compliance frameworks. For those requirements, reviewers describe it as delivering with far less overhead. For teams where security means deep policy enforcement and audit logging, it's not the right fit.
What's the specific Citrix feature your team actually uses that would be difficult to replicate elsewhere? That question narrows the field faster than most vendor comparisons.
Whether it's worth it splits on scale, not on the feature list. At a large size with strict controls, the security and central management justify the learning curve and cost; smaller teams tend to pay for depth they never fully use. The snag is that ease of use and Citrix's strengths pull in opposite directions, so you rarely get both at full strength at once. If ease matters as much as security, it's reasonable to shortlist lighter platforms alongside it rather than treating Citrix as the default.
This is one of the more specific comparison questions worth unpacking carefully, because the cost structure difference between these two is real, and the security gap is smaller than it might appear.
The per-user licensing issue with Citrix is well documented in reviews. Mid-market teams consistently flag it as the reason they're evaluating alternatives. V2 Cloud's pricing model is simpler and more predictable. But "enterprise-grade security" covers a lot of ground, and the answer depends on what security requirements actually matter for your environment.
From reviews in the virtual desktop infrastructure (VDI) category across both platforms:
- Citrix DaaS (4.1 stars, 546 reviews): Best for mid-market teams with complex compliance requirements, multi-vendor infrastructure (Azure and VMware together), or the need to publish individual applications rather than full desktops. Enterprise Grid Leader. Reviewers describe it as handling large VM catalogs with multiple delivery groups, supporting SAML, Azure AD, and Okta authentication, and managing centralized policy across distributed users. The security capability is real and deep. The cost reality: reviewers at 50–500-employee organizations consistently describe licensing as a barrier, and the setup's complexity means IT involvement at a level many mid-market teams can't sustain internally.
- V2 Cloud (4.7 stars, 248 reviews): Best for mid-market teams that need reliable remote access, centralized data, and fast deployment without building internal VDI expertise. Fully managed platform, so the security infrastructure is handled by V2 Cloud's team rather than your IT department. Reviewers describe data being stored on personal devices, encrypted access, and centralized control over who can access what. The security model is less configurable than Citrix, but sufficient for most mid-market compliance contexts. One reviewer with a multi-continent business managed it without an internal IT department.
The core trade-off: Citrix gives you more control over security configuration, which matters if your compliance requirements are specific (e.g., HIPAA, SOC 2, regulated financial services). V2 Cloud handles security for you in a managed model, which matters if your team doesn't have the capacity to configure and maintain those controls internally. For mid-market teams sitting on Citrix and evaluating V2 Cloud as an alternative, what's the compliance requirement that's keeping you on Citrix? That usually defines whether a migration makes sense.
Citrix's cost buys controls you can configure and show an auditor, which is decisive under a specific regulation and overkill without one. V2 Cloud drops the licensing weight and most of the upkeep, but with a lower ceiling if requirements tighten later. Pin down whether you're buying for a named rule or a general standard, and the rest mostly settles itself.
The uptime and data loss question is where marketing claims and review reality tend to diverge the most. Every VDI vendor promises reliability. What reviewers actually describe is more nuanced and worth paying attention to.
From reviews in the virtual desktop infrastructure (VDI) category, where reliability and data protection are mentioned:
- V2 Cloud: The reliability pattern in reviews is notably consistent. Multiple reviewers describe it as a platform where "nothing breaks," and one described great uptime as the primary reason for staying after two-plus years. One reviewer at an accounting firm specifically described it as preventing client files from being stored on personal computers, which is both a data-loss prevention and a compliance tool. The support team's response time is what reviewers cite when something does go wrong: phone and chat responses are described as fast and effective at resolving issues.
- Nerdio Manager inherits the Azure infrastructure SLA. Reviewers describe using it to enforce consistent security and compliance standards across all desktops simultaneously, with monitoring and visibility into endpoint performance. One reviewer described the platform as keeping everything organized so that when something goes wrong, the source is visible rather than requiring a search through disconnected systems. The autoscaling behavior is the one area reviewers flag for careful setup: misconfigured scaling rules can have downstream cost and availability effects.
- Kasm Workspaces: Data loss prevention is built into the product architecture. Ephemeral sessions mean that by default, nothing persists after a session ends, which is the DLP model some security teams explicitly want. Reviewers describe using this intentionally: spin up a session, do the work, close it, and nothing survives. For organizations handling sensitive files or working in regulated environments, this is the most defensible data posture in the category.
- Citrix DaaS: Enterprise reviewers describe it as the solution that keeps large organizations running when local hardware fails. Centralized management means a machine issue doesn't become a loss of user productivity, because the desktop exists in the cloud. The performance-related criticisms (latency under bandwidth stress, Teams audio issues) don't affect uptime per se but do affect the reliability of the user experience.
When you're evaluating uptime promises, are you looking at infrastructure SLAs or at actual user-reported experience consistency? Those are different numbers, and they tell different stories.
Your distinction between SLA and lived consistency is useful and often challenging for vendors. Workspot, which reports 99.95% availability, supports this with positive reviews, showing improved work-from-home setups and fewer on-prem troubleshooting issues. However, its specs are limited to prebuilt VM sizes, so while consistency is high, the maximum is lower. The SLA sets the minimum, and reviews indicate how closely daily performance matches it.
I’d look at both, but actual user-reported consistency would matter more after confirming the SLA meets the contractual requirement. A 99.9% infrastructure SLA doesn’t necessarily mean users experience 99.9% productive availability. I’d want to know how often sessions disconnect, performance becomes unusable, or recovery requires support intervention alongside the formal uptime figure.
Kasm Workspaces building data loss prevention into the architecture itself through ephemeral sessions, so nothing persists once the session closes, seems like a more defensible posture for regulated or sensitive work than relying on policy alone.



