Knowledge Base • NetReach
NetReach Desktop vs NetReach Cloud
A side-by-side comparison of deployment models, accessibility, security considerations, and operational ownership for NetReach.
At a glance
-
NetReach Desktop runs as a local application on a Windows or macOS workstation.
-
NetReach Cloud runs as a containerized, web-accessible application hosted on Azure, AWS, or a private VM.
- Core management capabilities are comparable—your primary decision is where NetReach runs and how users access it.
Why this comparison matters
Both NetReach Desktop and NetReach Cloud centralize management of WTI out-of-band devices, but they differ in architecture, access method, scalability, security integration options, and who owns the infrastructure and maintenance. Use the comparisons below to align your NetReach deployment with your operational model.
Side-by-side comparison
Deployment, access, and operations
Compare how each model is installed, accessed, scaled, and maintained.
| Category |
NetReach Desktop |
NetReach Cloud (Azure / AWS / VM) |
| Deployment model |
Installed locally on a workstation |
Hosted as a containerized web app in Azure, AWS, or a private VM |
| Platform support |
Windows and macOS |
Azure, AWS, or customer-controlled virtualization |
| Access method |
Local desktop UI on the host machine |
Browser-based UI over HTTPS |
| Remote accessibility |
Typically via VPN or remote desktop to the host workstation |
Accessible from anywhere network policy allows (HTTPS) |
| Scalability |
Bound by workstation resources |
Scales with cloud/VM resources (CPU/RAM, services) |
| High availability |
Dependent on host PC uptime |
Higher availability with cloud/VM redundancy options |
| Maintenance & updates |
Installed and updated on the workstation |
Managed centrally (image/app updates + platform operations) |
| Infrastructure required |
No cloud infrastructure required |
Requires Azure/AWS services or customer VM infrastructure |
| Ideal for |
Single-admin, lab, NOC workstation, isolated networks |
Distributed teams, enterprise fleets, MSP operations, remote browser access |
| Cell data usage controls |
Not available in Desktop (cellular data usage cannot be managed/limited from NetReach Desktop). |
Users can control cellular data usage on the NetReach Cloud version. |
Authentication
How Desktop and Cloud authenticate to devices and users
NetReach Desktop
-
Authenticates through the WTI units (device-based authentication model).
NetReach Cloud (Azure / AWS / VM)
-
Token-based authentication is used to access and manage all units.
-
SSO support: Supports Single Sign-On (SSO) using OAuth 2.0 with Azure or AWS.
Connectivity note (ports & firewalls)
NetReach Cloud is accessed via HTTPS (TCP 443) and may require additional ports depending on features in use (for example, web terminal access in some deployments). Ensure your firewall policies allow the required traffic between the NetReach instance and managed WTI devices.
Functional capabilities (what stays the same)
In most environments, Desktop and Cloud deliver comparable day-to-day management capabilities. The primary differences are deployment, access method, and operational ownership.
For more information
For licensing and deployment guidance, please contact our sales team at sales@wti.com.
