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 mid-market VDI question looks different from both the SMB and enterprise versions. You've got enough users that individual management doesn't scale, but you probably don't have a dedicated VDI team. Managers at this size are looking for something that can be administered by a generalist IT person without weeks of training, with predictable costs, and that doesn't require an emergency whenever someone leaves or joins.
Looking at the Mid-Market Grid for virtual desktop infrastructure (VDI) and filtering reviews by mid-market company segments, three platforms stand out: Nerdio Manager, VirtualBox, and Citrix DaaS.
- Nerdio Manager: The only Leader on the Mid-Market Grid, and the review evidence explains why. Managers at growing companies describe it as solving the problem of managing cloud workstations for a distributed workforce without manually setting up each machine. One review described the platform bringing structure to virtual desktop management that didn't require constant babysitting of individual configurations. For Microsoft-based environments, the Azure cost savings from autoscaling are particularly relevant at mid-market scale, where cloud spend is meaningful but not yet managed by a dedicated FinOps team.
- VirtualBox: A Contender on the Mid-Market Grid, with 95 mid-market reviews, the second-highest segment count in this category. Mid-market reviewers describe it as the go-to tool for running multiple OS environments on existing hardware, particularly for development, testing, and cross-platform work. The base product is free and open source, which is a meaningful cost consideration at this scale. The reviewers' most-often-cited limitation is that it's a workstation hypervisor, not a fleet management platform, so it works well for individual use cases but doesn't scale to centralized desktop management without additional tooling.
- Citrix DaaS: 141 mid-market reviews, the highest segment count. Mid-market managers describe it as what they use when they need consistent remote access for a large group of users across locations. The recurring concern at this scale is cost: licensing is designed for enterprise-scale deployments, and mid-market teams cite per-user licensing as a main reason they evaluate alternatives.
- Amazon WorkSpaces: Listed as a Mid-Market Contender (G2 score 63). Worth evaluating for AWS-centric environments. The integration with existing AWS infrastructure is the primary mid-market draw; the satisfaction score (39 in this segment) reflects trade-offs in usability that reviewers consistently flag.
For mid-market IT managers who've evaluated more than one of these, what was the deciding factor? Was it pricing structure, ease of management, or something about how the platform handles scale?
It is also worth mentioning V2 Cloud, which offers straightforward flat pricing and a low management burden, as well as Dizzion, suited for teams that require multi-cloud capabilities and compliance controls without maintaining their own infrastructure.
Which virtual desktop infrastructure (VDI) tools support integration with existing workflows without extensive customization? This question tends to reveal where the real hidden costs of a VDI deployment live. The licensing cost and hardware cost are obvious. The "six weeks of professional services to get it connected to our identity provider" cost is not until you're already in it.
Looking at the virtual desktop infrastructure (VDI) category for integration without customization overhead, here's what the review evidence shows:
- What teams are usually trying to integrate:
- Identity providers (Azure AD, Okta, SAML-based SSO)
- Existing file storage and collaboration tools
- Security and MDM platforms
- Line-of-business applications
From reviews in this category:
- Nerdio Manager: The Microsoft-native integration story is the strongest in this category. Reviewers describe it as fitting into existing Azure environments, integrating with Microsoft 365, Intune, and on-premises identity platforms without additional connectors. One reviewer described "simple integration into existing environments or setup into new environments" as the first thing they'd call out. For teams already in the Microsoft stack, the integration work is minimal because the product is built around that stack.
- Kasm Workspaces: Microsoft Identity integration is specifically mentioned in recent reviews as easy to set up. One reviewer described going live with Microsoft Identity integration with minimal issues, and another described Kasm replacing their Microsoft Remote Desktop servers without a complex migration. Integration with other software is described positively, though customizing specific security configurations (such as network isolation per session) requires navigating advanced settings.
- V2 Cloud: The integration story here is about simplicity over depth. One reviewer described using it to virtualize desktop software that doesn't have a web app, replicating an existing network environment with terminal services, with support helping work through the edge cases. It's not an enterprise integration platform, but for small teams moving existing software to a cloud-accessible environment, the connection between the cloud and existing tooling tends to be straightforward.
- Citrix DaaS: Multiple authentication methods (Azure AD, Okta, SAML), integration with VMware and Azure cloud VMs, and the ability to run apps rather than full desktops for specific use cases. The integration capability is deep, but reviewers flag that integration with third-party vendors could be tighter, and the configuration overhead is real. This is a platform for teams with dedicated IT resources managing the integrations, not one that connects out of the box with minimal effort.
For your workflow, which integration is non-negotiable? The answer usually determines whether a lighter or heavier platform makes more sense.
Cameyo is worth considering for the other camp: reviewers mention its provisioning via Google Groups and streaming Windows apps to Chromebooks as PWAs. If Azure and M365 are non-negotiable, the Nerdio-style solution you mentioned remains relevant; if Google Workspace or ChromeOS are essential, the choice shifts accordingly. Usually, the platform is selected based on the critical integration, not just price.
The integration that quietly costs the most time is usually peripherals: printers, scanners, signature pads and whatever specialist hardware a department depends on. Identity gets scoped carefully because it's obvious, while a label printer in the warehouse gets discovered in week three. Worth inventorying attached devices alongside the application list.
Identity integration would be the non-negotiable one for me because it touches every user from day one. If Azure AD, Okta, or SAML needs custom work just to get basic access right, the VDI project starts accumulating overhead before the desktop experience even matters.
The combination of mobile access and real-time performance is where VDI platforms separate fairly clearly. Some tools are designed primarily for desktop or laptop access and offer mobile as an afterthought. Others are built around the assumption that users might be connecting from a phone or tablet, and the performance experience on those devices reflects that design choice.
From reviews in the virtual desktop infrastructure (VDI) category filtered for mobile access and performance feedback:
- V2 Cloud: Mobile access is explicitly cited in multiple reviews, with users describing connecting from phones and tablets as part of normal workflow rather than a backup scenario. One reviewer cited the ability to access the platform from any computer or phone, anywhere in the world, as the primary reason their team uses it. The performance caveat that keeps showing up: the entry-level plans can feel slow, and getting genuinely fast performance sometimes means upgrading to a higher-tier plan, which increases cost.
- Nerdio Manager: Reviewers describe accessing the management interface and desktops from nearly any device without installing extra certificates or software. One reviewer specifically described the browser-based access as working on a phone or tablet. The performance side is strong for standard workloads, though reviewers note that apps that need strong network connectivity (like Teams video calls) can have degraded experiences inside the VDI.
- Kasm Workspaces: The browser-based architecture means the mobile story is technically solid, since any modern browser on a mobile device can access the workspace. Reviewers describe connecting from a tablet and having a Linux desktop ready in seconds. The performance ceiling is a consideration for resource-intensive tasks: the container-based model is lighter than full VMs, which improves mobile performance, but it's not designed for GPU-intensive workloads.
- Citrix DaaS: HDX optimization is the Citrix-specific feature reviewers describe for performance tuning. It adapts the session quality to available bandwidth, which matters for mobile connections that can vary. The reviewer complained that shows up most in this context: performance degrades when network quality drops, and Teams audio/video inside the VDI is a known friction point.
For teams where mobile is the primary use case rather than a backup, what's the minimum performance threshold that makes a VDI actually usable on a phone?
The point that mobile is often an afterthought aligns with the reviews. Amazon WorkSpaces reviewers describe using phones and tablets for real work, with graphics-heavy tasks limited on lower-tier bundles. For everyday apps, a stable connection and properly sized instance matter most.
On a phone, my minimum threshold would be less about raw benchmark performance and more about interaction latency. Opening apps, typing, scrolling, and switching windows need to feel immediate enough that users don’t start avoiding the VDI. For mobile-first use, I’d also test performance on an ordinary cellular connection rather than office Wi-Fi, since that’s where the experience really proves itself.
For a mobile-first use case, I'd test on an ordinary cellular connection rather than office Wi-Fi, since that's usually where the real performance story shows up rather than in a benchmark done under ideal conditions.



