Games on Whales

Games on Whales is an Unraid plugin that provides a low-latency, Moonlight-compatible game and desktop streaming host for gamers and homelab users who want to…

  • Game Servers
  • Media Applications
  • Network Services
  • Other
  • Plugins
  • Tools & Utilities
Games on Whales is an Unraid plugin that provides a low-latency, Moonlight-compatible game and desktop streaming host for gamers and homelab users who want to stream applications to Steam Deck, Apple TV, mobile, or desktop.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

66/100 Good

Maintained
86last commit 78 days ago
Popular
2620 GitHub stars
Easy to install
453 install platforms, install notes
Light to run
No data
Security check
95no serious findings, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 4 days ago

GitHub stars
20
Open issues
8
Last commit
2026-09-04
Latest release
2026.09.04
License
MIT
Activity
stale

Checked 5 days ago - source: GitHub (games-on-whales/unraid-plugin)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Start the temporary NVIDIA driver container If your setup uses NVIDIA, run the temporary-container command from the quickstart (for example, `sudo podman start musing_pascal`) so it fills the `nvidia-driver-vol` volume. That volume holds the NVIDIA driver files the game container needs; without it, the container may start but not use the GPU. source
  • Turn on NVIDIA persistence mode If your docs say you’re on CoreOS, run `sudo systemctl enable --now nvidia-persistenced.service`. This keeps NVIDIA’s device files ready at startup; otherwise the host may miss files the container needs and GPU acceleration can fail. source
  • Pick the right GPU on multi-GPU hosts Run `ls -l /sys/class/drm/renderD*/device/driver` to see which `renderD...` device points to your gaming GPU. Use that render node (Linux’s GPU device path) in Wolf; picking the wrong one can make it use the display card, causing crashes or no GPU acceleration. source
  • Deployment behavior The plugin deploys Wolf and Wolf Den with Docker Compose, persists udev rules, and adds an auto-start hook. source
  • Plugin settings Use the Settings page under Settings > Games on Whales to pick the GPU, appdata path, and start or stop the stack. source

Fetched 43 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why would the Games on Whales Unraid installer refuse to proceed?

The GoW installer requires the Compose Manager plugin to be present. Install Compose Manager from Community Applications before running the GoW installer.

What NVIDIA driver setting prevents a black screen or crash when streaming starts?

NVIDIA users must load nvidia_drm with modeset=1. Without that setting, Wolf can black-screen or crash on stream start.

How can I change the Wolf Den web UI port or configure Moonlight networking?

Wolf Den defaults to host port 8080, and the port can be changed in the plugin settings if another container uses it. Wolf defaults to host networking; you can switch to bridge networking or attach it to a custom Docker network with a static IPv4 address for Moonlight pairing.

Where are Wolf and Wolf Den state files stored, and do they survive reboots?

Their state persists in the configured appdata path, which defaults to /mnt/user/appdata/gow. The plugin also writes persistent udev rules and an auto-start hook to /boot/config/go so the stack restarts after a reboot.

How are controller device rules handled when a controller product name changes?

The bundled udev rules match Wolf devices by the Wolf virtual name glob, so they keep working if the controller's exact product name changes. If you maintain your own rules, prefer the glob over hard-coded names.

Can one server host multiple users with separate input devices?

Wolf can share a single server, possibly headless, by creating virtual hardware accelerated desktops. Remote mouse, keyboard, and controllers remain separated for those users.

Answers sourced from games-on-whales.github.io, github.com, www.reddit.com

Community

Collected 48 days ago - public community threads