Your organization still depends on a custom Windows inventory system built in 2008. Your finance team refuses to leave their legacy desktop application even though it’s a security nightmare. Meanwhile, your CTO is pushing AI integration and your CFO is hemorrhaging budget on complex virtual desktop infrastructure. Sound familiar? According to recent IDC research on application delivery platforms, this exact scenario plays out across enterprises worldwide—and it’s becoming a bottleneck for digital transformation.
The fundamental tension is real: legacy applications are often too expensive to rewrite, too mission-critical to retire, yet increasingly incompatible with modern security frameworks and AI-driven workflows. Organizations can find themselves trapped between maintaining aging systems and investing millions to rebuild them from scratch. That binary choice has forced many IT leaders to postpone modernization efforts or accept substantial security and operational costs to keep legacy software running.
A new IDC Market Note examining Cameyo by Google suggests there’s a third path forward. By delivering Windows and legacy applications directly within the Chrome browser using virtual application delivery, organizations can connect their existing software to modern cloud infrastructure and AI capabilities without requiring complete application rewrites. The analysis provides useful context for teams considering how to bridge the gap between their current environment and next-generation endpoints.
The Real Cost of Keeping Legacy Systems Alive
Replatforming legacy applications is genuinely expensive. IDC’s research emphasizes that the financial and technical barriers to rebuilding business-critical software from scratch make that approach unfeasible for most organizations. When you factor in development time, testing cycles, potential downtime, and training, a custom application rewrite can easily consume millions in budget and calendar months of effort.
Traditional virtual desktop infrastructure addresses this by allowing legacy applications to run remotely, but it brings its own cost structure. Complex VDI solutions require significant operational overhead, public server infrastructure, and ongoing management of persistent desktops. The IDC analysis highlights that organizations pursuing virtual application delivery as a bridge strategy see notably different economics. When shifting from legacy VDI environments to application-centric delivery models, companies report potential total cost of ownership reductions reaching 54 percent—a substantial improvement that extends hardware lifecycles and reduces capital expenditures.
That cost advantage matters especially when you consider how to fund other modernization efforts. Cloud infrastructure budgets are already stretched; research shows European organizations estimate they’re wasting roughly 89 percent of their public cloud spending. Reducing the burden of legacy system delivery frees up resources for other initiatives, whether that’s AI tooling, security upgrades, or DevOps infrastructure improvements.
Security and AI Capabilities Without Rewrites
Moving legacy applications into a browser-based delivery model sounds technically straightforward, but it creates meaningful security and capability advantages. When a 20-year-old Windows application suddenly runs inside Chrome, it inherits modern threat protections and data loss prevention policies that the original application was never designed to support. Through Chrome Enterprise, legacy workflows can connect to advanced security controls—threat detection, DLP policies, and managed access—without requiring any changes to the underlying application code.
The security model matters as much as the capabilities. Traditional VDI environments often rely on open VPNs and exposed public server ports that expand the attack surface and create vectors for lateral movement. The IDC research notes that application delivery approaches using zero trust architecture isolate sessions and resources from the broader corporate network, reducing overall exposure. Non-persistent infrastructure further limits the value of compromised sessions since nothing persists beyond a single connection.
For organizations eyeing AI integration, browser-based application delivery offers a path to introduce managed AI tools like Gemini without forcing every user toward uncontrolled shadow AI solutions. Legacy workflows running inside Chrome can access enterprise-managed AI capabilities alongside their existing applications, providing employees with sanctioned tools rather than pushing adoption of personal or external AI services that bypass organizational controls.
What This Means for IT Teams
Who is affected: Mid-sized organizations running Windows domains with legacy desktop applications, particularly those with limited budget for large-scale replatforming and hybrid environments combining on-premises infrastructure with cloud services. This applies whether your users are remote, in-office, or split between both.
Severity: Medium. If your organization is still running significant legacy applications while trying to modernize your endpoint strategy and adopt AI tools, you’re managing inefficiency and accepting security limitations, but this isn’t an emergency unless you’re facing active compliance pressure or the cost burden is directly impacting planned modernization spending.
Do this week:
- Audit your environment to identify which Windows desktop applications are truly business-critical and would be expensive to rewrite or migrate. Document which of these are actively blocking your team from adopting newer security controls or cloud-based workflows.
- Review your current remote desktop and VDI infrastructure costs—both licensing and operational overhead—and compare that to your total endpoint management budget. Understanding where money is flowing helps prioritize which applications might benefit from alternative delivery approaches.
- Evaluate whether your current Chrome Enterprise deployment (if you have one) includes advanced threat protection and DLP policies enabled. If not, determine whether your security team has bandwidth to enable these controls, since that capability becomes more valuable if you’re considering application delivery platforms.
Safe to ignore if: You operate in a pure cloud-native environment where legacy Windows applications represent less than 10 percent of your deployed workloads, or if your organization has already committed to and budgeted a multi-year replatforming roadmap with clear timelines and ownership.
Our take: Legacy applications aren’t going away, and pretending they will is a planning failure. The practical question isn’t whether to eliminate them but how to manage them cost-effectively while your organization pursues modern infrastructure and AI integration. Browser-based application delivery represents a genuine evolution from earlier virtualization models because it treats legacy software delivery as a tactical problem rather than a forced choice between rewrites and accepting perpetual technical debt.
Key takeaway: Organizations increasingly view legacy application environments as a temporary operational reality requiring a bridge strategy, not a permanent architectural constraint. By connecting existing software to modern Chrome infrastructure and cloud-based security controls, teams can modernize incrementally without the financial shock of wholesale application replacement.
The real question for your organization: Are you currently allocating resources to manage legacy applications in ways that could be redeployed toward modern cloud infrastructure and AI capabilities if you had a less expensive delivery mechanism? If the answer is yes, that’s the conversation worth having with your leadership team and security stakeholders.
Source: Google Cloud Blog article on Cameyo and IDC Market Note
Get Tech Savvy Digest in your inbox
IT news, cybersecurity, and crypto — the signal, not the noise. No spam, unsubscribe anytime.

