Skip to content

What Quasar is

Quasar runs games on computers you own and streams them to your browser. Games run in containers on your GPU machines, and you play them in a browser tab.

You log in, pick a game and press play. Quasar starts it on a GPU host with room, encodes it on the GPU, and streams video, audio and input to your browser over WebRTC. Close the tab and the session ends.

  • Multiple computers, one library. Add a GPU machine and it joins the pool. Sessions go wherever there is room.
  • Many users. Each user has their own home directory, saves and app access. Registration can be closed, invite-only or open.
  • Hardware encoding on verified AMD and NVIDIA GPUs; Intel VA-API remains untested.
  • Adaptive bitrate, on by default and tuned for smoothness.
  • Nothing to install on the client. Chrome or Chromium on desktop. Keyboard, mouse, touch and gamepads work.
  • An admin area at /admin for apps, images, stream profiles, hosts, GPUs, sessions and users.
  • Not Moonlight or GameStream. Moonlight clients can’t connect, and never will.
  • Not a game store. Quasar launches container images; you bring the games. Steam is supported as a library provider, so installed Steam titles show up as tiles.
  • Not built to face the internet. Play over a LAN or VPN. Quasar has not been security reviewed. See Reaching Quasar remotely.
  • No native client yet. The browser is the only client.

It suits homelab owners with an idle GPU who want to play from a laptop, tablet or TV, and households sharing one GPU.

It suits you less if you want to play over the open internet without a VPN, want a one-click appliance, or aren’t comfortable with Docker and Linux.

Quasar reuses the Wayland compositor (gst-wayland-display) and virtual input (inputtino) from the Wolf project (MIT). Wolf speaks Moonlight and grew from a single-host core; Quasar is multi-host, multi-user and streams to browsers. If you want Moonlight, use Wolf.