Cloud gaming on Windows with the rendering moved to a remote GPU

Noland runs as a desktop client on Windows and uses the Vast.ai account and API key you provide to show currently available marketplace hardware. After you choose a suitable listing, Noland provisions that remote machine as a Linux gaming environment and configures the NVIDIA stack, Sunshine streaming host, and WireGuard connection. Average provisioning takes about 10–15 minutes, with game downloads and title-specific setup potentially adding more time before play.

The operating systems on the two ends have different jobs. Windows runs locally on your PC, where it displays the stream and sends keyboard, mouse, or controller input. Linux runs remotely on the selected GPU host, where the game is installed, rendered, and encoded. A Windows client does not turn that host into Windows, does not create a Windows VM, and does not remove the remote environment's Linux compatibility constraints.

• Use the Windows desktop client to manage the cloud gaming workflow
• Choose from GPU listings currently available through your Vast.ai account
• Allow an average of 10–15 minutes for the base environment to provision
• Connect to a Linux host prepared with NVIDIA software, Sunshine, and WireGuard

A lower-spec Windows PC may be able to stream a supported game that it could not render well locally because the marketplace GPU handles the demanding graphics workload. The local machine receives compressed video and audio while returning player input. That can reduce the need for a powerful local gaming GPU, but it does not make local hardware irrelevant or guarantee that every old or entry-level Windows computer will provide a good experience.

The Windows PC still has to run the client smoothly, decode the selected video format and settings, display the stream, process audio and input, and maintain a stable network connection. Older processors, weak or unsupported video decoding, driver issues, high display targets, or unreliable Wi-Fi can become the limiting factor. Start with conservative resolution, frame-rate, and bitrate settings, then adjust them according to what the actual device and network can sustain rather than assuming a fixed FPS target.

• Check that the PC can decode the intended stream settings smoothly
• Use a stable wired or high-quality wireless connection where practical
• Test controllers, keyboard, mouse, audio, and display behavior early
• Increase stream quality only after confirming a stable baseline

Game compatibility is determined primarily by the remote Linux environment, not by the operating system displaying the stream. A game may depend on an anti-cheat system that does not support Linux, a launcher with incomplete Linux behavior, DRM that blocks the environment, or Windows-only services and features. Some titles can work while others cannot, and even a powerful marketplace GPU cannot solve a software-level incompatibility.

Check the specific games, launchers, anti-cheat requirements, account flows, peripheral needs, and online features that matter to you before committing to a long session. Do not treat a successful stream connection as proof that a title will launch or remain supported. Noland configures the gaming and streaming foundation, but it cannot promise universal game support, and compatibility can change when a game or its supporting software is updated.

• The remote host is Linux rather than Windows
• Anti-cheat, launchers, DRM, and Windows-only features can block a title
• Streaming compatibility and game compatibility are separate questions
• Verify important games individually instead of assuming a complete catalog

Noland prepares Sunshine on the remote host and WireGuard for the connection, enabling a direct streaming path between the provisioned environment and your Windows PC. In measurements, Noland adds about 8 ms of overhead above the natural network-route latency. That figure is not total latency and should not be read as an 8 ms input-to-display promise for every location, ISP, PC, or host.

Actual responsiveness includes distance and internet routing, local network conditions, congestion, game processing, host encoding, client decoding, input devices, and display behavior. The chosen GPU influences rendering capability, but a more expensive GPU cannot repair a poor route or unstable local connection. Compare host location and configuration alongside price, then tune game and stream settings for the session you actually observe; no particular FPS or latency is guaranteed.

Noland has a $0 monthly subscription. Compute is billed through Vast.ai while the selected marketplace instance runs, including time spent provisioning, downloading games, configuring software, or sitting idle. Typical overall marketplace compute is around $0.10–$0.40 per hour for many practical configurations, but live supply, GPU model, host, and configuration determine the actual rate. Neither a particular price nor a particular Windows cloud gaming setup is guaranteed to be available.

Treat each marketplace instance as replaceable infrastructure. Use game-supported cloud saves or another appropriate backup approach where available instead of assuming files will survive beyond the instance lifecycle. When a session ends, close the game cleanly, allow supported save synchronization to finish, stop the instance, and verify its status in the service responsible for billing. Closing the Windows client or disconnecting the stream should not be treated as confirmation that compute has stopped.