How it works
Quasar runs games on your GPU server and brings them to your browser. A first install puts everything on one host; you can add another computer as your library grows.
QUASAR / CONNECTIONSOne host. Two paths.
Your browser↕ HTTPS · web app & API
YOUR SERVER / ALL-IN-ONEControl plane↓ Session managementGPU host
Browser ↔ GPU host
Direct WebRTC · video, audio & input
Over your LAN or VPN
Follow the request, then the direct stream.
Press Play
Section titled “Press Play”- Your browser asks the control plane to start an app.
- The control plane selects an available GPU host and compatible stream settings.
- The host’s node agent starts the game.
- Your browser connects directly to that host for video, audio and input over WebRTC.
The web app uses the control plane’s API for accounts, the library and session management. The direct host connection carries the stream, so every GPU host must be reachable from your browser over your LAN or VPN.
What runs on your server
Section titled “What runs on your server”- Control plane: serves the web app and manages accounts, the library and sessions. Its data lives in Postgres.
- Node agent: runs apps and streams them from a GPU host. Each additional GPU server has its own agent.
- Installation and recovery: you declare one seed container. It keeps a recovery service running to install, update and recover that machine’s Quasar services. Persistent machine state and user homes must be kept.
See the glossary for app, host, session and quality profile terminology, or go straight to the quick start.