ISV Integration: Introduction
If you build a Windows product — WinForms, WPF, or similar — WebStream lets you deliver it as browser-based SaaS without rewriting it. WebStream sits beneath your application to stream it through the browser, remove RDP and VPN dependencies, and add enterprise-grade controls.
What WebStream provides for ISVs
- Browser delivery of your existing application, with no rewrite.
- White-label branding so customers see your identity, not WebStream's. See Branding.
- Governance — file, print, and clipboard policy, identity integration, and audit — that helps you pass customer security reviews.
- Multi-tenant isolation via organizations, so each customer has its own users, applications, and workspaces.
Two integration depths
| Approach | When |
|---|---|
| Publish as-is | Deliver your existing executable through workspaces and policies, with no code changes. See Publishing Your App. |
| Deep integration (ActiveX) | For ISVs with source-code access who want richer in-app capabilities. See ActiveX SDK. |
The business case
Shipping browser-delivered SaaS lets you onboard customers faster, remove the support burden of customer-managed RDP/VPN, and meet demand for cloud delivery — often in a quarter rather than the multi-year timeline a full rewrite would take.
To turn your product into governed single-app SaaS reliably, follow the Best Practices: SaaSification method — prove it runs on a fulltrust Virtual Desktop, tighten the policy toward lowtrust, then project the single app via an App Collection.