Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Block quote

Ordered list

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text

Emphasis

Superscript

Subscript

A Spectrum of VDI Options

Here's a breakdown of the key VDI deployment models:

  1. On-premises VDI: This approach involves deploying and managing all VDI infrastructure (servers, storage, software licenses) in your own data center. While offering full control, it requires significant upfront investment and ongoing IT expertise.
    1. Examples of On-Prem VDI: Citrix, Omnissa (formerly VMware) 
  2. Cloud-based VDI (often referred to as DaaS - Desktop as a Service): This option involves shifting your VDI infrastructure to a public cloud provider like Amazon Web Services (AWS) or Microsoft Azure. You manage the virtual desktops themselves, but the underlying infrastructure is handled by the cloud provider. While offering some improved scalability compared to on-prem, you're still responsible for ongoing management tasks.
    1. Examples of Cloud-based VDI: Azure Virtual Desktops, AWS Workspaces.  
  3. Hybrid VDI: A hybrid approach allows you to implement both cloud and on-prem deployment models and determine where your applications and data are hosted based on specific requirements. This approach can be useful when organizations need to cater to different use-cases within the organization. For example some applications may need to run close to an on-prem data center, or there may be security concerns about moving data to a public cloud. Another variation on the hybrid model is where a VDI solution operates their control plane in the cloud, but the compute or data plane is on-prem. This is common with many cloud-native solutions, while there are some cloud-native, SaaS solutions like Sonet.io that have both the control and compute plane in the cloud. 

Cloud-native vs SaaS VDI solutions

Many VDI vendors also refer to themselves as cloud-native or SaaS and it’s important to understand the distinction between the two terms. SaaS describes how you access the software (subscription online), while cloud-native describes how it's built (designed for the cloud). Think of it as a delivery method vs. architecture. Cloud-native applications break down the functionalities into smaller components called microservices, and compared to traditional monolithic applications that develop functionalities in a big block, cloud-native applications have higher scalability and resilience thanks to their distributed functionalities. Modern VDI solutions can be both cloud-native and SaaS (like Sonet.io), while others may only be cloud-native (eg. it’s built for the cloud, but you still need to manage the infrastructure, it’s not delivered as a service) or only SaaS (eg. a solution has been ‘lifted-and-shifted’ to the cloud to enable it to be delivered as a service, but it lacks the benefits of being cloud-native). Many of the legacy VDI solutions are neither cloud-native or SaaS. 

  1. Cloud-native VDI: A cloud-native VDI solution means that the VDI solution was developed specifically for the cloud, versus a legacy vendor solution that has been ‘lifted-and-shifted’ to the cloud. Being ‘born in the cloud’ means they have likely reduced some of the complexity around deployment and operations. Cloud-native solutions may also increase efficiency, reduce costs and ensure high availability. While cloud-native solutions may offer a better experience due to their architecture, they often still require infrastructure setup and maintenance. Another important note about cloud-native solutions is that some aspects of the solution may not run in the cloud, even if it is cloud-native. Often the control plane (the plane that decides how data is managed and processed) is in the cloud, but the compute or data plane is not cloud-based. The compute plane is where your data is actually processed, and this may still be done on-premise. 
    1. Examples of Cloud-native VDI: Dizzion, Workspot 
  2. SaaS VDI: A SaaS VDI solution manages everything for you - infrastructure, software, updates, security - allowing you to focus on your core business. You pay a predictable monthly fee per user, and the solution provider handles the rest. SaaS solutions can be cloud-native or ‘lift-and-shift’. Many MSPs provide a SaaS solution so that organizations can realize the benefits of this delivery model, but the VDI solution itself was not necessarily built for the cloud. 
    1. Examples of SaaS VDI that are also cloud-native: Windows 365, Sonet.io 

Why choose a Cloud-native, SaaS solution? 

Here's how a true Cloud-native, SaaS VDI solution like Sonet.io stands out:

  • Easy Adoption: No need for lengthy implementation projects. For organizations that have never used VDI, a cloud-native SaaS solution is a great way to get started and move away from shipping devices, using VPNs and managing software on devices. For organizations looking for an alternative to their existing VDI, this also makes the transition very straightforward. You can get started with a set of apps quickly as there’s no infrastructure to set up, and you can ensure you have positive feedback from your initial user group before rolling out to the wider organization. The ability to leverage elastic scaling makes it very simple to start small and scale when ready. 
  • Reduced IT Burden: Eliminate the need for dedicated VDI administration staff. As the infrastructure is completely managed by the SaaS provider, there’s no need to have a team of people dedicated to managing VDI infrastructure. Ongoing updates and patches to published apps and virtual desktops can be done once on a ‘golden VM’, so there’s no need to update hundreds or thousands of machines. If an update causes and issue (eg. like what organizations saw with Crowdstrike) you can rectify if by updating once, instead of requiring manual updates on every device. Admins can manage apps and policies from a single, browser-based interface, and there’s no need to deploy anything on user devices. 
  • Modern User Experience: Allow users to access work through any browser on any device. As the workforce evolves, many workers now expect a modern user experience that matches their experience with consumer apps. Using a cloud-native SaaS solution allows users to access the apps and desktops they need through any commercial browser, and easily switch between devices. Even legacy desktop apps can be accessed through a browser, making it a much more familiar experience for workers. 
  • Always Up-to-Date: Instances are always kept up-to-date and don’t run on stale versions. This means you can always leverage the latest features and aren’t stuck on outdated versions of your VDI solution and can more easily update apps and desktops. 
  • Scalability on Demand: Easily add or remove users as your business needs evolve. New users can be added in seconds, leveraging edge PoPs of the public cloud network backbone closest to their location for high-performance. 
  • Predictable Costs: Replace upfront capital expenditure with a flat monthly subscription fee. With per-user pricing there is no risk of surprise costs that are often seen with traditional DaaS or cloud-native solutions due to their usage-based pricing. 
  • Built-in Security and Visibility: Benefit from comprehensive Zero Trust security and data loss prevention policies. Leveraging a cloud-native SaaS solution that doesn’t require anything to be deployed on the device, creates an air-gap between user devices and corporate apps and data. Security policies can be easily applied across groups of users and admins can get in-depth visibility into user actions for troubleshooting, training and forensic purposes. 

Common Questions when moving to a cloud-native SaaS solution for VDI

Can you access on-prem applications with cloud-native or SaaS VDI solutions? 

Yes. VDI solutions that are hosted in the cloud are still able to connect with on-prem apps, often through a connector. This allows you to take advantage of cloud-native SaaS solutions, while still satisfying your on-prem use cases. 

Can you use a SaaS VDI solution with windows virtual desktop or windows apps? 

Yes, you can use a SaaS solution to deliver windows desktop apps as well as SaaS apps, web apps, virtual desktops and on-prem apps. 

Are there any latency issues when using a SaaS VDI solution? 

No. Users get an excellent experience with low latency as powerful cloud compute resources are used, nearest to their physical location. Leveraging world-wide cloud infrastructure means that organizations can easily add users in any location and enable users traveling to any location to have fast, seamless and secure access to apps and virtual desktops. 

Exactly how long does it take to get started with a SaaS solution? 

You can deliver apps to your remote users within an hour. 

What are the benefits of having both the control plane and the compute plane in the cloud? 

Having both the control plane and the compute plane in the cloud ensures you have predictive costs, end-to-end security and elastic scalability. If the compute and control are not all in the cloud, you often then need to manage across multiple vendors for setup, maintenance, security and whenever an issue arises. Having both in the cloud also helps to ensure you have predictive costs and elasticity is more easily managed. 

Conclusion

For businesses seeking a simplified, scalable, and cost-effective VDI solution, true SaaS, that is also cloud-native is the clear winner. With Sonet.io you can empower your workforce with secure, high-performance apps and desktops while freeing your IT team to focus on strategic initiatives.

Ready to explore the benefits of true SaaS, cloud-native VDI? Book a demo with us today!