Onscryn vs Microsoft
Remote Desktop Services.
Remote Desktop Services is the long-standing way to publish apps and desktops from Windows Server, and it has a web client. Onscryn gives you browser access to Windows apps as a ready-made service. The difference is mostly in how much you build and operate yourself.
| Onscryn | Microsoft RDS | |
|---|---|---|
| Browser access | A link in a browser tab | The Remote Desktop web client, published from RD Web Access |
| What you set up | Enroll a Windows host and publish an app | Per Microsoft's docs: RD Gateway, RD Connection Broker and RD Web Access, trusted public certificates, the web client installed from the PowerShell Gallery |
| Licensing | Windows and your own software still need licences | Per-user RDS CALs (the web client needs per-user, not per-device) |
| Sign-in | SSO over OIDC and SAML, roles, instant revocation | Windows and Microsoft identity. Check their documentation for SSO options |
| Data controls | Clipboard and file policy at the broker, watermark, recording | Group policy based. Check their documentation |
| Automation | UI-tree workflows and a Copilot (preview) built in | Not part of RDS |
| Branding | Your name, logo and domain | Web client and RD Web Access pages. Check their documentation |
Choose RDS if
- You already run Windows Server infrastructure and have the skills to operate it.
- You want to stay entirely inside the Microsoft stack.
- Your deployment is large and needs full control of every component.
Choose Onscryn if
- You would rather not build and maintain a gateway, a broker and web-access servers.
- You want browser access to just the apps people need, with controls included.
- You want your own branding and SSO without extra assembly.
What the RDS web client asks of you
Microsoft's documentation says the Remote Desktop web client needs a deployment with RD Gateway, RD Connection Broker and RD Web Access, publicly trusted certificates on the gateway and web access roles, and a deployment configured for per-user Client Access Licences, otherwise all licences are consumed. The web client itself is installed on the RD Web Access server from a PowerShell module, and has to be updated the same way.
None of that is unreasonable if you run Windows Server already. It is simply work, and it is work Onscryn exists to take off your plate.
Licensing
RDS uses Client Access Licences, and Microsoft's AVD documentation also lists RDS CALs with Software Assurance as an eligible licence where session hosts run Windows Server. Using Onscryn does not remove Windows licensing either, so settle that early whichever way you go.
Sources, reviewed October 2026
- Set up the Remote Desktop web client (Microsoft Learn)
- Licensing Azure Virtual Desktop, including RDS CALs (Microsoft Learn)
We make Onscryn. Vendors change products and terms, so check their documentation before you decide. Spot something out of date? Tell us at [email protected].
Questions.
Yes. Microsoft documents a Remote Desktop web client for RDS. See the linked page for its requirements.
More comparisons
Onscryn vs Azure Virtual Desktop
How Onscryn compares with Microsoft's Azure Virtual Desktop for publishing Windows apps: where each runs, how licensing works, what you manage, and which fits.
Onscryn vs Citrix
How Onscryn compares with Citrix Virtual Apps and Desktops (Citrix DaaS) for delivering Windows apps: browser access, setup, what you manage, and when each fits.
Onscryn vs Cameyo
How Onscryn compares with Cameyo by Google for turning Windows apps into browser apps: how users access them, where they run, and which fits.
Onscryn vs Amazon WorkSpaces Applications
How Onscryn compares with Amazon WorkSpaces Applications, formerly AppStream 2.0: where apps run, how they are billed, how users connect, and which fits.