Table of contents Toc Icon
Table of contents Toc Icon
A practical look at the three ways engineering teams give designers remote access to SOLIDWORKS, and how each one performs under real CAD workloads.
Remote and hybrid work has become a standard part of how engineering teams operate. For most software, giving people access from home is straightforward. SOLIDWORKS is more demanding, because the experience depends heavily on the hardware doing the work, and a remote setup that ignores this tends to perform poorly.
SOLIDWORKS relies on a certified professional graphics card and OpenGL, a substantial amount of memory, and fast storage. When any of these is missing or underpowered, models become slow to rotate, rebuilds take longer, and large assemblies become difficult to work with.
When teams move SOLIDWORKS off the office desk, they generally choose one of three approaches: a VPN back to the office network, a remote desktop connection into an office workstation, or a cloud hosted desktop. These options appear similar, but they behave very differently in practice. The sections below explain how each one works, where each one is limited, and why a cloud hosted VDI setup is generally the strongest fit for professional CAD work.
The Three Common Ways Teams Run SOLIDWORKS Remotely
The table below summarizes the three approaches before we examine each one in detail.
| Setup | How it works | Where it breaks down |
| VPN to the office | SOLIDWORKS runs on the local laptop. Files and licenses are accessed across a secure tunnel to the office network. | Opening and saving large assemblies across the tunnel is slow, and file conflicts are common without proper data management. |
| Remote desktop to an office workstation | SOLIDWORKS runs on a workstation at the office. The user views the screen remotely and only displays data and input travel across the connection. | A physical workstation is still required for each user, and it must remain powered on and maintained. |
| Cloud hosted VDI | SOLIDWORKS runs on a GPU-backed machine in the data center. Users connect from any device through a browser or application. | A stable internet connection is required, which is the main consideration for this approach. |
Running SOLIDWORKS Over a VPN
A VPN is often the first approach teams try, mainly because it is simple to configure. SOLIDWORKS continues to run on the local laptop, and it connects back to the office network to reach the license server and the design files.
The limitation is the file transfer. SOLIDWORKS assemblies are large, and every open and save operation moves that data across the tunnel. As the distance between the office and the remote user increases, the time required for each transfer also increases. Files open slowly, saves are delayed, and without a proper data management system, two users can overwrite each other’s work.
A VPN can be workable for light editing of individual parts. It becomes difficult to use once large assemblies are involved.
Running SOLIDWORKS Through Remote Desktop
Remote desktop addresses the file transfer problem. SOLIDWORKS runs on a workstation located in the office, close to both the design files and the license server. The remote user connects to that workstation, and only the display image, mouse input, and keyboard input travel across the connection. The CAD data itself remains on the office network.
This is a meaningful improvement, but it carries a requirement worth noting. Every remote user needs a physical workstation in the office, and each of those machines must remain powered on and maintained. If the workstation has a weak graphics card, the remote session performs only as well as that card allows. And if the machine fails, the user cannot work until someone is on site to resolve the issue.
Remote desktop also restricts how much of that workstation’s hardware SOLIDWORKS can use. Rotating and panning 3D models can introduce noticeable latency, some graphics cards run into OpenGL limitations that cause visual artifacts or force degraded software rendering, and peripherals like 3D space mice often show input lag over the connection.
In effect, remote desktop solves the file problem by requiring a full workstation for each person. This becomes costly and increasingly difficult to manage as the team grows.
Running SOLIDWORKS on Cloud Hosted VDI
A cloud hosted desktop, also described as desktop as a service, retains the main advantage of remote desktop while removing its central weakness. Instead of running on a workstation in your office, SOLIDWORKS runs on a GPU-backed machine in a data center. Users connect to it from a laptop, a Mac, or a thin client, through a browser or a lightweight application.
As with remote desktop, only display data travels to the user’s screen. The difference is that the machine performing the work is a properly specified, CAD-grade workstation that is maintained, patched, and backed up by the provider. There is no office workstation to purchase, no machine to keep powered on, and no hardware to replace when it reaches end of life.
The role of the graphics hardware in this model is worth examining more closely.
How GPU Acceleration Supports SOLIDWORKS Performance
SOLIDWORKS renders models using the graphics card rather than the main processor. Rotating a large assembly and enabling RealView are handled by the GPU. For this reason, a cloud-hosted virtual desktops intended for CAD cannot rely on a standard office-grade cloud machine. It requires a dedicated GPU behind it.
Ace Cloud Hosting delivers these desktops through Managed Citrix DaaS solutions, and the component responsible for graphics delivery is Citrix HDX Graphics, formerly HDX 3D Pro. It renders the 3D model on the server’s graphics card and streams the resulting image to the user’s screen. SOLIDWORKS draws using both OpenGL and DirectX, and HDX Graphics accelerates both, so viewport interaction remains responsive.
Citrix developed this capability specifically for graphics-intensive applications. Its documentation notes that HDX provides a desktop-equivalent experience even over lower-bandwidth connections, which is why a cloud hosted desktop remains usable over a standard broadband connection rather than requiring an office-grade network.
Support for 3D Input Devices
A 3D input device such as a SpaceMouse is central to how many SOLIDWORKS users pan, zoom, and rotate their models throughout the day. Many basic remote access tools handle these devices poorly, which can significantly degrade the experience of a remote setup.
Citrix addresses this through USB redirection with prioritized handling for the 3D mouse channel, so a SpaceMouse operates within the hosted session much as it does on a local machine. It is a detail that has a direct effect on daily use.
Managed Cloud Hosting Compared with Self-Managed AWS or Azure
Once a team decides to move to the cloud, the next question is who operates the environment. One option is to rent raw servers from AWS or Azure and build the entire setup internally. The other is to use a managed desktop as a service provider that delivers a fully configured environment.
The self-managed route often appears less expensive until the associated work is accounted for. Someone on the team is responsible for sizing the GPU machines, keeping graphics drivers current, tuning the streaming configuration, patching Windows, managing the license server, and scaling seats up and down as project demands change. In practice, this becomes an ongoing responsibility that usually falls to an IT staff member who already has a full workload.
With a managed cloud-hosted desktop, this work is handled by the provider. Ace Cloud Hosting operates the environment through Managed Citrix DaaS solutions, keeps the GPU drivers and HDX configuration tuned for SOLIDWORKS, and adjusts the number of seats as needed. The team simply opens SOLIDWORKS and works, without anyone internally maintaining the underlying infrastructure.
A managed desktop as a service provides a fully specified, GPU-backed Windows workstation in the cloud. The local device simply connects to it. SOLIDWORKS runs at workstation speed, design files remain in the data center, and there is no infrastructure for your team to build or maintain.
SOLIDWORKS Licensing in a Cloud Environment
Licensing is an area where remote setups frequently encounter problems, so it is worth addressing directly. Many multi-user engineering teams use SolidNetWork Licensing, in which a license server distributes floating seats to users as they open SOLIDWORKS.
When this license server is accessed over a VPN and the connection is slow or distant, users can experience delays when opening files and loading add-ins, and connection errors to the license server tend to appear at inconvenient times.
In a cloud hosted VDI environment, the license server is located within the same environment as the machines running SOLIDWORKS. They communicate over a local, low-latency connection rather than across the public internet, which removes most of the licensing issues that remote teams encounter. SolidNetWork, standalone, and 3DEXPERIENCE-connected licensing may be used in hosted environments, depending on the license agreement and deployment design. Teams should confirm compatibility with their SOLIDWORKS reseller before migration.
Data Management in a Hosted Environment
Storing SOLIDWORKS files in general-purpose services such as Dropbox or OneDrive can cause serious problems, because these tools do not recognize file references, revisions, or check-in and check-out behavior. This is a common cause of broken assemblies and overwritten work.
A dedicated CAD data management system such as SOLIDWORKS PDM resolves this, and it performs particularly well within a hosted virtual desktop. The PDM vault and the machine running SOLIDWORKS reside on the same fast backend, so check-in and check-out operations complete quickly. The team benefits from version control and file locking without the delay associated with reaching back to an office server.
Comparing the Cost of Each Approach
A capable SOLIDWORKS workstation represents a significant expense, and it has a limited useful life. A certified desktop or laptop configured for CAD costs several thousand dollars, and most teams replace these machines roughly every three years. Multiplied across every seat and combined with the IT time spent configuring and repairing them, the total cost is substantial.
Cloud hosted desktops for SOLIDWORKS shift this from a large periodic purchase to a predictable monthly cost per user. Published industry pricing for a GPU-backed cloud desktop generally falls within a range of a few hundred dollars per user per month, depending on the level of performance each engineer requires. Hardware purchases and refresh cycles are eliminated, and seats can be added or removed as workload changes.
One point worth noting during evaluation is the billing model. Some providers charge by the hour, which can produce unpredictable costs. A flat monthly rate per seat keeps the total stable and straightforward to plan around.
Choosing the Right Approach for Your Team
The following table offers a straightforward way to match each approach to a team’s situation.
| Situation | Reasonable choice | Reason |
| A single user, light part editing, strong home internet | VPN or standalone license on a capable laptop | Low overhead, and the workload is small enough to handle locally. |
| A few users, with strong workstations already in the office | Remote desktop into those office workstations | Reuses existing hardware, provided it is maintained. |
| A growing team, large assemblies, multiple sites, or Mac users | Managed cloud hosted VDI | Full CAD performance on any device, with no hardware to purchase or maintain and straightforward scaling. |
| An approaching hardware refresh with a constrained budget | Managed cloud hosted VDI | Avoids the large purchase in favor of a predictable monthly cost. |
Data Security Considerations
For many engineering and manufacturing organizations, design files are among their most valuable assets. In this respect, a cloud hosted desktop is often more secure than a local laptop.
In this model, CAD files are never stored on the local device. They remain in the data center, and only an encrypted image of the screen is transmitted to the user. If a laptop is lost or stolen, no design data is exposed. Access is centrally controlled, so IT determines who can access which resources, and all data is backed up in a single location rather than distributed across individual machines.
When endpoint downloads, client-drive mapping, clipboard transfer, and USB storage are restricted, CAD files can remain inside the hosted environment rather than being stored on users’ devices.
Choosing an Approach
A VPN is simple to set up but performs poorly with large assemblies. Remote desktop improves on this but requires a dedicated office workstation for each user. A managed cloud hosted VDI setup provides every engineer with a fast, fully specified SOLIDWORKS environment on the device they already use, without any hardware to purchase or maintain.
For teams that are distributed, working with heavy assemblies, or approaching a hardware refresh, Cloud Hosted SOLIDWORKS VDI is generally the approach best suited to how engineering work is carried out today. Ace Cloud Hosting delivers this through managed virtual desktop solution, giving engineering teams a fully managed, GPU-backed setup without the overhead of running the infrastructure themselves.
Provision a GPU-backed cloud desktop, load your largest assembly, and assess the performance directly. Our team will help size the environment correctly and connect your license and PDM, so the evaluation reflects how your engineers actually work.
