Put the Windows application in the browser — with file, print, clipboard, and audit control — without a helper client on every endpoint, and without a locked concurrent-seat year.
WebStream ACP is a single control plane for governed application delivery. You host it on your own servers (WebStream LDC), in a private cloud, or on AWS. Users open a standard HTML5 browser. There is no AppController to install, and no plug-in to keep in version lockstep.
If that describes yours, you already have a publishing product. The question is whether the browser path is the product, or a subset that still needs a native client for files, direct print, sound, ports, or smart cards.
GraphOn GO Global publishes Windows applications with a proprietary protocol, RapidX. An HTML5 Web App exists. AppController remains the default when users need the fuller device path. WebStream is built the other way around: the browser is the product, and governance sits in the control plane. If you are packaging a commercial application for customers, the same path is covered on ISV SaaSification.
GO Global is a capable Windows application publisher. The friction shows up when the browser has to carry the whole job, when the contract is a concurrent-seat year, and when file, print, and clipboard need to be policy — not a client setting.
The official Web App does not replace AppController for client file access, direct local print, client sound, serial and parallel ports, or smart cards. Clipboard in the Web App is limited. If users need those behaviours, the native client is still the default.
AppController is the path for the fuller product. That is another package to install, version, and support — the same class of helpdesk load you hoped to leave behind by “going HTML5.”
GO Global licences concurrent users on a one-year, non-cancellable commitment. You cannot drop seats mid-term. That is a clean model for a steady concurrent peak. It is a rigid one when usage is shift-based, seasonal, or still being proven.
Single sign-on is sold separately from the core seat. Identity should sit with the identity provider you already run, not as a per-seat extra.
GO Global publishes application publishing, clients, and printing. It does not publish a control plane at the depth of trust levels, disposable sessions, child-process default deny, profile cleanup, audited file/print/clipboard, and session recording.
Official notes still cover UPD failures, Type 4 gaps, and in-session Chrome/Edge print issues. The Web App print path is a PDF preview. If print is a governed download, design for that. Do not inherit a Universal Printer Driver estate.
A side-by-side look at governed browser delivery versus GraphOn application publishing.
| Area | GO Global (GraphOn) | WebStream ACP |
|---|---|---|
| What users receive | Published Windows apps; full device path via AppController | The specific application in the browser, governed per policy |
| Browser path | HTML5 Web App exists; AppController is the default for files, direct print, sound, ports, smart cards | Browser is the product. No helper client |
| Remoting | Proprietary RapidX. Does not use Microsoft RDS as the remoting stack | Session factory is an RDP pool on the host. RDP is not exposed to the internet. Pixels leave over WSS |
| Licensing | Concurrent users, one-year non-cancellable commitment | SessionHours — pay for active streaming time. Editions, BYOL |
| Identity | SSO is a paid add-on | OIDC, LDAP, Microsoft Entra ID, Okta in the identity plane |
| File, print, clipboard | Client and Web App behaviour; print still has UPD / Type 4 notes | Policy for file, print/PDF, and clipboard, with session audit |
| Session hygiene | Multi-session host (GGSE) | Disposable sessions, profile cleanup, child-process default deny, optional session recording |
| Where it runs | Windows host; your datacentre or a hoster | Your servers (LDC), private cloud / customer VPC, or AWS Marketplace |
| TLS | Your edge | Designed path: load balancer plus ACM certificates |
| Admin experience | GraphOn consoles and client packages | One admin console. AI-assisted ops via MCP Server |
Want the wider picture? See how WebStream compares with Citrix, Amazon WorkSpaces, Thinfinity, and Kasm on the platform comparison page, or model costs on pricing.
The same publishing jobs, handled with the browser as the whole path and governance in the control plane.
Publish a commercial Windows product as a browser experience under your own brand. SessionHours follows usage. Identity stays with the IdP you already sell against.
Keep the Win32 application. Stop asking every endpoint for a native client when the job is one form, one database, one print-to-PDF.
Give an external user exactly one application, governed and audited. Not a desktop. Not a VPN foothold. Not a client package on a laptop you do not own.
Concurrent-seat years assume a stable peak. SessionHours fits contact centres, shared workstations, and rotating crews.
WebStream LDC runs on locally hosted Windows servers. Private cloud and customer VPC are first-class. AWS Marketplace is there when that is the buying path — it is not a requirement.
Publish today from the room you already have. Move the same application later. You are not buying a second VDI programme to get out of a publishing tool.
WebStream is not a like-for-like replacement for every GO Global deployment — and we would rather tell you up front.
WebStream is not a Horizon or Citrix persistent-desktop replacement. It virtualises application access, not the desktop around it.
The end-to-end demo: browser login, launching a real Windows application, file workflows, and starting WebStream Core on infrastructure you control.
Watch the full WebStream demo — Windows applications published through the browser without a helper client.
Tell us which Windows applications GO Global publishes today and we will map the WebStream path — including where WebStream fits and where it does not. Prefer to give us full detail? Use the full assessment form.
For publishing specific Windows applications to users who can work in a browser — yes, that is the job. WebStream does not replace a persistent desktop estate, and it does not match AppController on USB, multi-monitor, or smart-card redirection. If those are mandatory, say so early.
GO Global does not use Microsoft RDS as the remoting stack. It uses RapidX. That is a protocol fact, not a licensing conclusion. Microsoft has separately discussed RDS CALs for third-party GUI remoting. WebStream uses an RDP pool on the host and does not expose RDP to the internet. Do not read this page as a claim about avoiding licences. Confirm licensing with your Microsoft advisor.
No. Users sign in and launch the application in a modern HTML5 browser over TLS. There is no AppController package and no browser plug-in to install.
GO Global sells concurrent users on a one-year commitment. WebStream paid tiers bill SessionHours — active streaming time — plus editions. You are not buying a year of seats you cannot reduce. Always-on ISV peaks should still be modelled; hours are a different forecast from concurrent users.
On your own servers with WebStream LDC, in a private cloud or customer VPC, or from AWS Marketplace. This is not an AWS-only product. TLS is designed around a load balancer and public certificates, not a self-signed host certificate in the browser.
WebStream treats print as a governed PDF download by design, and clipboard as policy — on or off, direction, size, audit — over HTTPS. That is a deliberate product choice, not a Universal Printer Driver estate. If users must have direct local print or device-class redirection, WebStream is the wrong product.
Yes. Prove one application in WebStream Core, on your servers or in a short cloud trial, before you touch the concurrent-seat estate.
Identity sits in the WebStream identity plane with OIDC, LDAP, Microsoft Entra ID, and Okta. It belongs to the identity provider you already run rather than a per-seat extra.
Start free with WebStream Core. Deploy on-premises (MSI / LDC) or on AWS, and prove the browser experience with your own application before you change the GO Global contract.