Desktop as a Service
Definition
Desktop as a Service
Desktop as a service delivers a full user desktop from a provider hosted platform rather than from the local device. The provider runs the images, the sessions, and the underlying infrastructure, and the buyer keeps the data and the policies.
The user experience is deliberately ordinary — somebody logs in, sees a familiar desktop, and never thinks about where the processing actually happens.
The appeal is control. Data stays in the hosted environment rather than scattering across laptops, and a lost device becomes an inconvenience instead of an incident.
It is not a universal answer — network dependency is absolute, and a user on a poor connection has a worse day than they would with a local machine.
Key takeaways
- Desktop as a service hosts complete user desktops on a provider platform.
- Data stays central, which reduces the damage a lost device can do.
- Network quality determines the experience more than any specification does.
- Licensing and peak concurrency drive most of the real cost.
How it works
The provider hosts desktop images on shared infrastructure and streams sessions to whatever device the user has. Provisioning is centralised, so a new starter gets a working desktop in minutes and a leaver loses access the moment the account is disabled.
Pricing usually follows concurrency rather than headcount. Ten thousand named users with two thousand concurrent sessions cost far less than ten thousand simultaneous ones, which makes usage profiling worth doing early.
The model sits inside the wider cloud services market. The FedRAMP Marketplace lists authorised cloud offerings, and hosted desktop providers appear there once they serve buyers with federal security requirements.
| Factor | Strength | Limitation |
|---|---|---|
| Security | Data never leaves the platform | Depends on identity controls |
| Provisioning | Minutes rather than days | Image management overhead |
| Cost | Predictable per session | Peak concurrency drives price |
| Performance | Fine for most workloads | Poor for graphics heavy tasks |
Remote access guidance still applies. NIST SP 800-46 Revision 2, published in July 2016, covers enterprise telework and remote access security, including the risks that follow any device connecting from outside the office.
Peripheral support is the practical friction — printers, scanners, headsets, and signature pads behave differently over a remote session, and testing them is unglamorous but necessary.
Image management becomes a standing job. Every application update has to reach the hosted image, and a neglected image quietly turns into the thing users complain about most.
Examples
Desktop as a service suits regulated work, contractor access, and rapid scaling, and the case is usually about control rather than cost. Four examples show the pattern.
A financial services firm. Contractors worked entirely inside hosted desktops, so no client data ever reached a machine the firm did not manage.
A healthcare group. Clinical staff moved between sites and resumed the same session on a different terminal, which suited shift working far better than assigned laptops.
An outsourcing provider. Agent desktops were hosted centrally in 2024, letting a Manila site and a home based team run identical, locked down environments.
A design studio. It tried hosted desktops for rendering work and moved back, because graphics performance over the session was not acceptable.
Related terms
Desktop as a service sits alongside the cloud delivery models it belongs to and the infrastructure roles that keep hosted environments running for users every working day.
- Cloud Based: the delivery mode this service depends on.
- Software as a Service SaaS: the application layer equivalent of the same idea.
- Remote Work: the working pattern driving most adoption.
- IT Support Technician: the role supporting users of hosted desktops.
- Network Engineer: the role whose work determines session quality.
- Cloud Engineer: the role operating the underlying platform.
- Data Center: the facility the sessions ultimately run in.
FAQ
What is the difference between desktop as a service and virtual desktop infrastructure?
Both stream hosted desktops. Desktop as a service is delivered and operated by a provider, while virtual desktop infrastructure is usually built and run in house.
How is it priced?
Typically per concurrent session per month, sometimes per named user. Concurrency pricing rewards accurate usage profiling before purchase.
Does it improve security?
It centralises data, which reduces device loss risk. It does not fix weak identity controls, and it introduces the platform itself as a dependency.
What workloads are a poor fit?
Graphics intensive work such as rendering, video editing, and computer aided design, unless the provider offers specialist accelerated instances.
What happens when the network fails?
Work stops. Offline capability is limited by design, so connectivity resilience matters more than it does for local machines.
Which peripherals cause problems?
Printers, scanners, signature pads, and specialist headsets. Test each one before rollout rather than after.
Explore hosted delivery models across the Outsource Accelerator site.
Independent
