Sunshine and Moonlight cloud gaming on a provisioned GPU host

The Vast.ai GPU host runs the Linux gaming environment and Sunshine, which captures rendered frames and encodes them for streaming. The client side receives and decodes that video, plays audio, and returns keyboard, mouse, or controller input to the remote session.

Noland configures the NVIDIA stack, Sunshine, and WireGuard as part of provisioning, which averages 10–15 minutes. Games and their launchers can require additional installation and configuration after the base environment is ready.

WireGuard provides the network connection used to reach the Sunshine host, allowing the stream to travel directly between the client and provisioned environment rather than through a Noland video relay. Direct does not mean distance-free: packets still follow the available internet route.

Noland's measured overhead is about 8 ms above natural route latency. This is not total input-to-display latency, which also includes routing, game processing, encoding, local and remote network conditions, decoding, display, and input devices.

• Select a host with a sensible route to your location
• Prefer a stable local connection
• Tune bitrate, resolution, and frame rate for the actual network and client

The selected GPU affects game rendering and encoding headroom, but stream quality also depends on the host configuration, game settings, client decoding capability, bandwidth stability, congestion, and display. A higher-priced GPU cannot correct a poor network route.

There is no responsible guarantee for FPS, resolution, or latency across every setup. Start with settings the client and connection can sustain, observe the session, and adjust before increasing quality targets.

A working Sunshine stream does not guarantee that a game itself will run. Noland's remote environment is Linux, and compatibility varies with the title, launcher, anti-cheat, DRM, Windows-only features, and input requirements.

Not every game works, and marketplace hardware and pricing are not guaranteed. Treat the host as disposable, use supported save synchronization or another appropriate backup approach where available, and stop the instance when the session ends to avoid continued compute billing.