Architecture
Where the workspace runs, what connects it, and where each responsibility belongs.
The two sides
Vyray Now connects the device in front of you to a separate computer. Applications and processes run on that remote machine. Your local device displays the remote desktop and supplies your input.
Deployment choices
The remote machine can be a cloud instance or a physical workstation. Choose the operating system and computing resources for your workload. A cloud machine may have a GPU or use CPU resources, depending on the applications you need.
Cloud infrastructure is provided separately. Vyray Now is the connection to that workspace.
Scroll sideways to read the full table.
| Component | Responsibility |
|---|---|
| Local device | Displaying the session and supplying input. |
| Remote computer | Running applications, processes and the workspace. |
| Hosting environment | Keeping the remote machine available and configured. |
Data boundaries
Files saved on the remote computer stay on that computer. Local copies, transfers and backups depend on how you configure and use the environment.
The remote machine still needs maintenance and backups. Separating it from a traveling device does not remove those responsibilities.
Continuity
A disconnected client does not itself stop the remote host. Ongoing work depends on the host, the application process and the operating-system session remaining active.
Transport, service topology and deployment requirements are being verified for the release. This overview describes the workspace model.